Features of LINC Generate - Public Support Login - Unisys

LINC 

Release 16.3/16R3 

Migration and Conversion 

Guide 

December 1998 

v

!()+ 


Release 16.3/16R3 

Migration and Conversion 

Guide 

Copyright ( 1998 Unisys Corporation. 

All rights reserved. 

Unisys is a registered trademark of Unisys Corporation. 

LINC is a registered trademark of Unisys Corporation. 

Level 16.3/16R3 December 1998 

v

The names, places, and/or events used in this publication are not intended to correspond to any 

individual, group, or association existing, living, or otherwise. Any similarity or likeness of the names, 

places, and/or events with the names of any individual living or otherwise is purely coincidental and 

unintentional. 

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product and related 

material disclosed herein are only furnished pursuant and subject to the terms and conditions of a duly 

executed Program Product License or Agreement to Purchase or Lease Equipment. The only warranties 

made by Unisys, if any, with respect to the products described in this document are set forth in such 

License or Agreement. Unisys cannot accept any financial or other responsibilities that may be the 

result of your use of this information or software material, including direct, indirect, special or 

consequential changes. 

You should be very careful to ensure that the use of this information and/or software material complies 

with the laws, rules, and regulations of the jurisdictions with respect to which it is used. 

The information contained herein is subject to change without notice. Revisions may be issued to advise 

of such changes and/or additions. 

RESTRICTED. Use, reproduction, or disclosure is subject to the restrictions set forth in DFARS 

252.227-7013 and FAR 52.227-14 for commercial computer software. 

TRADEMARKS. All other terms mentioned in this book that are known to be trademarks or service marks 

have been appropriately capitalized. Unisys Corporation cannot attest to the accuracy of this 

information. Use of a term in this book should not be regarded as affecting the validity of any trademark 

or service mark. 

Correspondence regarding this publication should be forwarded using the Business Reply Mail form at 

the back of this document to: Australian Centre for Unisys Software, 115 Wicks Road, North Ryde NSW 

2113, AUSTRALIA. Alternatively you can send an E-Mail message to: linc.pi@unisys.com 

Griffin is a trademark of Unisys Corporation. 

Micro Focus is a registered trademark of Micro Focus Ltd. 

ORACLE is a registered trademark of Oracle Corporation. 

PTX is a registered trademark of Sequent Computer Systems Inc. 

RS/6000 is a registered trademark of International Business Machines Inc. 

Sequent is a registered trademark of Sequent Computer Systems Inc. 

SQL*Plus is a registered trademark of Oracle Corporation. 

Sun is a registered trademark of Sun Microsystems, Inc. 

UNIX is a registered trademark of X/Open Company Ltd.

Contents 

About This Document :::::::::::::::::::::::::::::::::::::::::: ix 

Section 1. New Features of LINC Release 16.3/16R3 

New Features for All LINC Systems :::::::::::::::::::: 1-1 

CASE Load as LINC Generate Report ::::::::::::: 1-1 

Improved Handling of Date Conversions with New 

Century ::::::::::::::::::::::::::::::::: 1-2 

Extended Access for Inquiry-Only Users ::::::::::: 1-2 

Improved Generation Performance :::::::::::::: 1-3 

Enhanced Dictionary Enforcement :::::::::::::: 1-3 

Enhanced Structure Selection in LINC Generate :::: 1-4 

Enhanced Handling of Dates ::::::::::::::::::: 1-4 

Increased MAPPER File Header ::::::::::::::::: 1-4 

Implementation of Debug Date and Time ::::::::: 1-5 

Extended SENDLIST.STATIC; Command :::::::::: 1-5 

Consistent Initialization of Group Setup Data Items :: 1-5 

Enhanced Checking of LINC Specifications :::::::: 1-6 

Changes to support LCIF :::::::::::::::::::::: 1-6 

New Features for MCP Based LINC Systems :::::::::::: 1-7 

Extended RDB Capabilities :::::::::::::::::::: 1-7 

Restriction Lifted on Transfer and Configure ::::::: 1-7 

Rebuilding Profiles from Ispec Tables :::::::::::: 1-7 

Correct Calculation of Blocksize :::::::::::::::: 1-8 

Use of Connection Libraries for HUB ::::::::::::: 1-8 

Changes to Usercodes for Reports :::::::::::::: 1-9 

Restriction Lifted for BNA Generates :::::::::::: 1-9 

Specifying Sort Memory :::::::::::::::::::::: 1-10 

Avoiding Unplanned Reorganizations ::::::::::::: 1-10 

Improved Offline Reorganizations ::::::::::::::: 1-10 

Support for Features of DMS II XE ::::::::::::::: 1-11 

Control of Report Output Files :::::::::::::::::: 1-11 

Handling Five Digit Mix Numbers :::::::::::::::: 1-11 

Mixed Kanji Data in Ad Hoc Queries ::::::::::::: 1-11 

New Features for OS 2200 Based LINC Systems :::::::: 1-12 

v iii

Contents 

Installing with SOLAR ::::::::::::::::::::::::: 1-12 

Enhanced Debugging Facility :::::::::::::::::: 1-12 

Dynamically Changing Recovery Method :::::::::: 1-12 

Immediate Effect of LSM Changes :::::::::::::: 1-12 

Confirming Installation after Generation :::::::::: 1-12 

Increased Efficiency of Storage of Numeric Items :: 1-13 

Support for SDF Format Tapes ::::::::::::::::: 1-13 

Rebuilding Profiles from Ispec Tables :::::::::::: 1-13 

Implementation of GLB.TASK ::::::::::::::::::: 1-13 

Efficiency of SA$ Storage Area ::::::::::::::::: 1-13 

Remapping and Relinking All Reports ::::::::::::: 1-14 

Initializing with MCB When Using USERPRT :::::::: 1-14 

Operator Keyins :::::::::::::::::::::::::::: 1-14 

New Features for LINC Systems based on the UNIX 

operating system ::::::::::::::::::::::::::::::::: 1-15 

Terminating Your LINC System ::::::::::::::::: 1-15 

Improvements to Disk Space Use for ORACLE ::::: 1-15 

Transferring LINC Systems in Object Format ::::::: 1-15 

Upgrading Your Own LINC Executables with Object 

Packaging ::::::::::::::::::::::::::::::: 1-16 

Section 2. Migrating to LINC Release 16.3/16R3 

Overview ::::::::::::::::::::::::::::::::::::::::::: 2-1 

Terminology Changes in LINC Release 16.3/16R3 ::::::: 2-1 

Migrating from Releases Earlier than LINC II Release 

16.2/16R2 :::::::::::::::::::::::::::::::::::::: 2-2 

Finding Documentation :::::::::::::::::::::::: 2-2 

Using LCOPY ::::::::::::::::::::::::::::::: 2-2 

Migrating to LINC Release 16.3/16R3 ::::::::::::::::: 2-4 

Migration Procedure ::::::::::::::::::::::::: 2-4 

Using LCOPY to Migrate to LINC Release 16.3/16R3 2-5 

Installing Over LINC II Release 16.2/16R2 ::::::::: 2-5 

Addressing Migration Issues :::::::::::::::::::::::::: 2-7 

Environmental Settings :::::::::::::::::::::::: 2-7 

Date Handling :::::::::::::::::::::::::::::: 2-7 

Initialization of Group Setup Data Items ::::::::::: 2-9 

Numeric Data Items for OS 2200 Based LINC 

Systems :::::::::::::::::::::::::::::::: 2-11 

PowerClient Release 2R1 :::::::::::::::::::::: 2-11 

Generating Your LINC Systems after Migration ::::::::: 2-12 

iv v

Section 3. Migrating to LINC Development Release 2.3 

Contents 

Considerations :::::::::::::::::::::::::::::::::::::: 3-1 

Repository ::::::::::::::::::::::::::::::::::::::::: 3-2 

Section 4. Loading LINC Specifications from LDA into LINC 

Generate 

Overview ::::::::::::::::::::::::::::::::::::::::::: 4-1 

Preparing to Load an LCIF File :::::::::::::::::::::::: 4-2 

Restrictions on CASE Load ::::::::::::::::::::::::::: 4-3 

CASE Load Screen :::::::::::::::::::::::::::::::::: 4-4 

Overview ::::::::::::::::::::::::::::::::::: 4-4 

Accessing the CASE Load Screen ::::::::::::::: 4-4 

CASE Load Screen for MCP Based LINC Generate :: 4-4 

CASE Load Screen for OS 2200 Based LINC 

Generate :::::::::::::::::::::::::::::::: 4-7 

CASE Load Screen for LINC Based on the UNIX 

operating system Generate ::::::::::::::::: 4-10 

Generating Your LINC System after Loading :::::::::::: 4-14 

Recovering a Failed CASE Load ::::::::::::::::::::::: 4-14 

Running CASE Load in Batch :::::::::::::::::::::::::: 4-15 

Overview ::::::::::::::::::::::::::::::::::: 4-15 

Batch CASE Load for MCP Based LINC Systems :::: 4-15 

Batch CASE Load for OS 2200 Based LINC Systems 4-15 

Batch CASE Load for LINC Systems Based on the UNIX 

Operating System ::::::::::::::::::::::::: 4-16 

Creating the Batch Parameter File ::::::::::::::: 4-16 

Description of the Load Process ::::::::::::::::::::::: 4-19 

Overview ::::::::::::::::::::::::::::::::::: 4-19 

Process for a Full Load ::::::::::::::::::::::: 4-19 

Process for a Partial Load ::::::::::::::::::::: 4-19 

Effect of Granularity Flags in Partial Loads :::::::: 4-21 

How Conflicts are Resolved in Partial Loads ::::::: 4-22 

How Dictionary Items Are Loaded ::::::::::::::: 4-23 

Extract and Load Rules for LCIF Files ::::::::::::: 4-25 

Section 5. Unloading a LINC Specification from LINC 

Generate for LDA 

Using the CASE Data Extract Request Screen :::::::::: 5-1 

Accessing the Screen :::::::::::::::::::::::: 5-1 

v v

Contents 

Fields on the CASE Data Extract Request Screen ::: 5-2 

Completing a Partial Extract ::::::::::::::::::: 5-5 

Important Issues with the LCIF File :::::::::::::::::::: 5-7 

Overview ::::::::::::::::::::::::::::::::::: 5-7 

Compatibility of LDA and LINC Generate :::::::::: 5-7 

Relationships in the LCIF File ::::::::::::::::::: 5-7 

Checking the LCIF File :::::::::::::::::::::::: 5-7 

Reducing the Size of Extract Files from Host LINC :: 5-7 

Transferring the LCIF File to LDA :::::::::::::::: 5-9 

LINC Syntax Conversion :::::::::::::::::::::: 5-10 

Appendix A. Reserved Words 

Appendix B. LINC Limits 

Reserved Words Used by Software :::::::::::::::::::: A-2 

Reserved Words Created with Your LINC Specification ::: A-3 

Checking Reserved Words :::::::::::::::::::::::::::: A-4 

Overview ::::::::::::::::::::::::::::::::::::::::::: B-1 

Conventions :::::::::::::::::::::::::::::::::::::::: B-1 

Data Items ::::::::::::::::::::::::::::::::::::::::: B-3 

Dictionary Items :::::::::::::::::::::::::::::::::::: B-4 

Global Logics ::::::::::::::::::::::::::::::::::::::: B-4 

Summary :::::::::::::::::::::::::::::::::: B-4 

Number of Global Logics :::::::::::::::::::::: B-5 

Logic Lines in a Global Logic ::::::::::::::::::: B-5 

Global Logics in an Ispec :::::::::::::::::::::: B-5 

Nested Global Logics ::::::::::::::::::::::::: B-6 

Global Setup Data items :::::::::::::::::::::::::::::: B-7 

Summary :::::::::::::::::::::::::::::::::: B-7 

Number of Global Setup Data Items :::::::::::::: B-7 

Size of Global Setup Data Items ::::::::::::::::: B-7 

Number of Global Setup Data Items in an Ispec ::::: B-8 

Number of Global Setup Data Items in a Report :::: B-8 

Ispecs ::::::::::::::::::::::::::::::::::::::::::::: B-9 

Summary :::::::::::::::::::::::::::::::::: B-9 

Number of Ispecs :::::::::::::::::::::::::::: B-9 

Number of Data Items in Output Structure ::::::::: B-10 

Size of Ispec or Profile Record :::::::::::::::::: B-11 

Number of Logic Lines in an Ispec ::::::::::::::: B-12 

Database Commands ::::::::::::::::::::::::: B-12 

vi v

Contents 

Painted Items in an Ispec :::::::::::::::::::::: B-12 

Internal Database Storage Order :::::::::::::::: B-12 

Profiles :::::::::::::::::::::::::::::::::::::::::::: B-14 

Summary :::::::::::::::::::::::::::::::::: B-14 

Number of Profiles ::::::::::::::::::::::::::: B-14 

Number of Ordinates in a Profile :::::::::::::::: B-14 

Length of Profile Ordinates ::::::::::::::::::::: B-14 

Number of Lines in a Profile Definition :::::::::::: B-15 

Reports :::::::::::::::::::::::::::::::::::::::::::: B-16 

Summary :::::::::::::::::::::::::::::::::: B-16 

Number of Logic Lines for a Report :::::::::::::: B-17 

Setup Data items in a Report Frame ::::::::::::: B-17 

Database Commands ::::::::::::::::::::::::: B-17 

Global Setup Data Items in a Report ::::::::::::: B-17 

Setup Data Items in a Report Frame ::::::::::::: B-18 

Size of Generated Report Code ::::::::::::::::: B-18 

Files Used in a Report :::::::::::::::::::::::: B-18 

Physical Size of Extract Files Created Within a Report B-18 

Setup Data Items :::::::::::::::::::::::::::::::::::: B-20 

Summary :::::::::::::::::::::::::::::::::: B-20 

Number of Setup Data Items ::::::::::::::::::: B-20 

Size of Setup Data Items :::::::::::::::::::::: B-20 

Setup Data Items in an Ispec ::::::::::::::::::: B-20 

Setup Data Items in a Report ::::::::::::::::::: B-21 

Utilities :::::::::::::::::::::::::::::::::::::::::::: B-22 

Summary :::::::::::::::::::::::::::::::::: B-22 

Automatic Entries (HUB) ::::::::::::::::::::::: B-22 

Generation ::::::::::::::::::::::::::::::::: B-22 

GLI Programs ::::::::::::::::::::::::::::::: B-22 

LCOPY :::::::::::::::::::::::::::::::::::: B-22 

LINC System Transfer :::::::::::::::::::::::: B-23 

NOF Programs :::::::::::::::::::::::::::::: B-23 

Recovery :::::::::::::::::::::::::::::::::: B-23 

Reorganization :::::::::::::::::::::::::::::: B-23 

Translation ::::::::::::::::::::::::::::::::: B-23 

System Software :::::::::::::::::::::::::::::::::::: B-24 

Summary :::::::::::::::::::::::::::::::::: B-24 

Stations/Users :::::::::::::::::::::::::::::: B-24 

Size of LINC Generate Database :::::::::::::::: B-24 

Size of Generated Code ::::::::::::::::::::::: B-24 

Size of Generated Report Code :::::::::::::::: B-25 

Sorting Order ::::::::::::::::::::::::::::::: B-25 

v vii

Contents 

Appendix C. Features of OS 2200 Based LINC Systems 

Features of LINC Logic ::::::::::::::::::::::::::::::: C-1 

Features of LINC System Commands :::::::::::::::::: C-2 

Features of System Data Items :::::::::::::::::::::::: C-3 

Features of Utilities and Report Handling ::::::::::::::: C-3 

Features of LINC Generate ::::::::::::::::::::::::::: C-3 

Miscellaneous Differences :::::::::::::::::::::::::::: C-4 

Appendix D. Features of LINC Systems Based on the UNIX 

Operating System 

Overview :::::::::::::::::::::::::::::::::::::::::: D-1 

Structural Features ::::::::::::::::::::::::::::::::: D-1 

Overview ::::::::::::::::::::::::::::::::::: D-1 

Architecture :::::::::::::::::::::::::::::::: D-1 

Identification :::::::::::::::::::::::::::::::: D-2 

Profiles :::::::::::::::::::::::::::::::::::: D-2 

Reports :::::::::::::::::::::::::::::::::::: D-3 

Reserved Words ::::::::::::::::::::::::::::: D-3 

Terminals :::::::::::::::::::::::::::::::::: D-3 

Translation ::::::::::::::::::::::::::::::::: D-4 

ORACLE and Griffin Considerations ::::::::::::::::::: D-4 

Features of LINC Logic :::::::::::::::::::::::::::::: D-5 

Appendix E. Differences between Host LINC and LDA 

Glossary 

Index 

System-Wide and General Differences ::::::::::::::::: E-2 

Ispec and Report Differences ::::::::::::::::::::::::: E-5 

Data Item Differences :::::::::::::::::::::::::::::::: E-6 

Data Attribute Differences :::::::::::::::::::::::::::: E-8 

Profile Differences :::::::::::::::::::::::::::::::::: E-10 

Generation and Validation Differences ::::::::::::::::: E-11 

Logic Differences ::::::::::::::::::::::::::::::::::: E-12 

System Data Item Differences :::::::::::::::::::::::: E-16 

Global Logic Differences ::::::::::::::::::::::::::::: E-19 

Run Time Testing Differences ::::::::::::::::::::::::: E-20 

viii v

About This Document 

Purpose 

Scope 

Audience 

The purpose of this document is to provide information on migration of LINC Systems to 

LINC Release 16.3/16R3 (LINC Generate and LINC Deployment), and conversion across 

the various host types, and between LINC Generate and LDA. 

In this document, LDA is taken to mean LINC Development / LDA III. 

This document contains an outline of the new features of this release, and the instructions 

for migrating to this release from the previous release. 

For conversion between LINC Generate and LINC Deployment, it includes sections on 

extracting LINC Specifications from and loading LINC Specifications into LINC Generate. 

For conversion between host types, it includes details of reserved words and limits, and 

differences in the implementation of LINC on those host types. 

This document refers to other documents in the LINC Library for complete details of new 

features. Migration instructions for migration from releases prior to the previous release 

are included in the previous release. 

The primary audience for this document consists of those people responsible for installing 

LINC Software, and migrating LINC Systems. Secondary audiences consist of those people 

responsible for moving LINC Specifications between LINC Generate and LDA, and 

converting LINC Systems across host types. 

Prerequisites 

The audience is presumed to have been trained on the LINC product and should be familiar 

with administering LINC Systems. 

v ix


How To Use This Document 

Read Section 1 to obtain an outline of the new features of LINC Release 16.3/16R3, and 

then read Section 2 for the migration instructions. Read Section 4 and Section 5 for details 

of moving LINC Specifications between LINC Generate and LDA. See the appendixes for 

information on conversion of LINC Systems across host types. 

See "Organization" in this section, for details. 

Organization 

This document is organized into five sections and five appendixes. 

Section 1. New Features of LINC Release 16.3/16R3 

This section outlines the new features of LINC Generate and LINC Deployment for LINC 

Release 16.3/16R3. 

Section 2. Migrating to LINC Release 16.3/16R3 

This section describes the migration of LINC Deployment and LINC Generate from LINC II 

Release 16.2/16R2 to LINC Release 16.3/16R3. 

Section 3. Migrating to LINC Development / LDA III Release 2.3 

This section describes the migration from LDA Release 2.2 to LDA Release 2.3. 

Section 4. Loading LINC Specifications from LDA into LINC Generate 

This section describes the procedure for loading LINC Specifications into LINC Generate 

from an LCIF file created in LDA. 

Section 5. Unloading a LINC Specification from LINC Generate for LDA 

This section describes the procedure for extracting a LINC Specifications from LINC 

Generate into an LCIF file for loading into LDA. 

Appendix A. Reserved Words 

This appendix lists the various reserved words for this release. 

Appendix B. LINC Limits 

This appendix lists the known limits for LINC Systems. 

x v

Appendix C. Features of OS 2200 Based LINC Systems 


This appendix outlines the features of OS 2200 LINC Systems, and highlights differences 

between MCP based LINC Systems and OS 2200 LINC Systems. It is a useful source of 

information for conversion of LINC Systems to and from OS 2200 based hosts. 

Appendix D. Features of LINC Systems Based on the UNIX Operating System 

This appendix outlines important features of the implementation of LINC Systems based 

on the UNIX operating system, and highlights differences between MCP based LINC 

Systems and UNIX based LINC Systems. It is a useful source of information for conversion 

of LINC Systems to and from UNIX. 

Appendix E. Differences between Host LINC and LDA 

This appendix outlines important differences between LINC Generate and LDA. 

Related Product Information 

The following publications contain information relevant to the definition and operation of 

a LINC System. These publications are intended as reference sources for users who have 

completed LINC training courses. See your local Unisys representative for information on 

available LINC training courses. 

All of the documents below are published by Unisys Corporation and can be ordered 

through Plymouth Operations Software Manufacturing (POSM), or your local Unisys 

subsidiary. 

In addition to these documents, you may need documentation describing the operation of 

any related software; for example, COBOL. 

LINC Generate Operations Guide 

This document describes the use of LINC Generate to create and maintain user 

information systems. 

LINC Programming Reference Manual 

This document contains reference material for developers, such as LINC Logic commands 

and System Data items used in creating LINC Systems. 

LINC Programming Reference Handbook (7844 8057) 

This document contains the syntax of LINC Logic commands and System Data items and 

other commands used in LINC Generate. 

v xi


LINC Generate Reference Manual: Painter and Editor 

This document contains reference material for LINC Generate, including LINC Editor and 

LINC Painter commands, Data commands and Data Attributes, and screens and commands 

for defining Profiles. 

LINC Executive Overview - The Business Case (7833 2145) 

This document is an introduction to LINC for executive and general readers. 

LINC Technical Overview - The Business Case (7833 2152) 

This document is an overview of LINC features and facilities for more technically oriented 

readers. 

LINC on UnixWare Installation and Configuration Guide 

This document describes the procedures for installing and configuring released LINC 

Software on UnixWare hosts. 

LINC on Sequent DYNIX/ptx Installation and Configuration Guide 


Software on Sequent PTX hosts. 

LINC on Sun SPARC Solaris Installation and Configuration Guide 


Software on Sun hosts. 

LINC on IBM RS/6000 AIX Installation and Configuration Guide 


Software on RS/6000 hosts. 

LINC on HP-UX Installation and Configuration Guide 


Software on HP-UX hosts. 

LINC Deployment for Windows NT Getting Started 


Software on Windows NT hosts. 

LINC Ad Hoc Inquiry Operations Guide 

This document describes the operation of LINC Ad Hoc Inquiry, which enables users to 

make inquiries against a LINC System, either interactively, or by using structured (SQL) 

statements. 

xii v

LINC Developers Guide: LCOPY 


This document provides reference material for using the LINC LCOPY Utility, which is 

used to transfer LINC Specifications between versions of LINC Generate. 

LINC Development Installation and Administration Guide 

This document describes the installation of LDA in standalone or multiuser environments 

and the administration of the LDA working environment, including repository 

administration, backup procedures, security and other issues. 

v xiii

Section 1 

New Features of LINC Release 

16.3/16R3 

This section describes new features of LINC Release 16.3/16R3 in the following categories: 

$ ‘‘New Features for All LINC Systems’’ 

$ ‘‘New Features for MCP Based LINC Systems’’ 

$ ‘‘New Features for OS 2200 Based LINC Systems’’ 

$ ‘‘New Features for LINC Systems based on the UNIX operating system’’ 

New Features for All LINC Systems 

The following new features apply to LINC Systems on all host types. 

CASE Load as LINC Generate Report 

When the CASE Load program was first developed, the amount of data being transferred 

was small. The CASE Load program was developed as a COBOL program, using a NOF 

interface into the LINC Development System (LINC Generate). With the advent of LDA, the 

amount of data being transferred has increased dramatically, necessitating a fresh 

evaluation of both the approach and implementation of the CASE Load facility. 

The CASE Load facility has been re-engineered as a Report of LINC Generate. 

Reduced impact of loads 

The philosophy of the load is to mark as little as possible of your LINC Specification for 

regeneration. During a partial load, changes to a structure are made by merging the 

changes, rather than deleting the structure and then re-adding it. Deleting a structure 

causes all references to the structure to be marked as needing re-generation, which can be 

excessive for minor changes such as adding a Global Setup Data item, altering the 

presentation of a screen, or changing logic. 

For example, in previous releases all Global Setup Data items were deleted and then 

added. This marked all parts of your LINC Specification that used Global setup Data items 

for regeneration. For LINC Release 16.3/16R3, only changed Global Setup Data items are 

replaced. 

v 1-1


Handling Dictionary items 

When loading Dictionary items, CASE Load will perform the equivalent of Dictionary 

Maintenance (DMA) changes when the incoming Dictionary item conflicts with an existing 

item. This functionality will replace the previously required manual procedure to get the 

Dictionaries in step before the load. 

Batch initiation of CASE Load 

The CASE Load program can be initiated as a batch process, as for other LINC Generate 

Reports. 

Accessing CASE Load 

CASE Load screens are accessed from inside LINC Generate by using the CLD Activity 

code. For example, you can enter GO CLD in any Action field. 

Error messages 

During the CASE Load, an error report is produced, detailing any problems encountered. 

You can direct this report to your choice of printer. 

Improved Handling of Date Conversions with New Century 

For LINC Release 16.3/16R3, new functionality has been implemented for the existing date 

conversion and change of century date features as follows. 

$ A new FORMAT; command option has been added to the MOVE.DATE; LINC Logic 

command. This will enable you to specify the format of the date returned, allowing for 

the current century date as opposed to the initiate date. 

$ A new LINC Supervisor command, SCENTURYnnnn, enables you to set a secondary 

base year in GLB.CENTURY-START to determine which century a six-digit date 

belongs to, independent of the base year which is still used for relative day numbers. 

$ A date conversion of particular six-digit date items will now ignore GLB.CENTURY for 

date conversions of GLB.TODAY and its equivalents. 

The secondary base year set by the SCENTURYnnnn Supervisor command will not be 

displayed nor compared when using the LCOPY Compare facility. 

For details see your LINC Programming Reference Manual and LINC Generate 

Operations Guide. 

Extended Access for Inquiry-Only Users 

In releases prior to LINC Release 16.3/16R3, you could access the LINC Painter, the LINC 

Editor, and some LINC Reports (listing screens, such as LDL Listing) in LINC Generate as 

an inquiry-only user. 

1-2 v

NewFeaturesforAllLINCSystems 

In LINC Release 16.3/16R3, as an Inquiry only-user you can access most parts of your LINC 

Specification. This includes access to view trace settings, frame descriptions, pack 

mapping, accesscode and station access, inquiry screens, and inquiry reports. 

There is no access to parts of LINC Generate that only have an updating function. For 

example: generate screens, Supervisor Mode, patch utilities, patch consolidation and audit 

archiving, transfer screens, LCOPY, CASE Extract, resource locking, loading of language 

and output control codes files, and Module views. 

Improved Generation Performance 

In LINC Release 16.3/16R3, improvements to the performance of your LINC Generate 

reduce the number of logic lines marked for re-edit when you change Global Setup Data 

items or Setup Data items. 

In releases prior to LINC Release 16.3/16R3, when a Global Setup Data item or Setup Data 

item was edited, all lines of logic that referenced the item were automatically marked for 

re-edit. In LINC Release 16.3/16R3, the lines of logic that reference the item are marked for 

re-edit only if your change is significant (for example, you change the name, length, or edit 

type). 

Impact on Translation 

You should consider any impact on translated Global Setup Data item values when editing 

Global Setup Data items. When you change a translatable Global Setup Data item, existing 

language translations are only deleted if the name, length, or initial value changed. In 

previous releases, translations were deleted if you made any change. 

Enhanced Dictionary Enforcement 

In releases prior to LINC Release 16.3/16R3, you could control the creation of data items in 

your LINC Specification by using the Enforce dict (Y,N,D) field on the Specification 

Options screen of LINC Generate. 

In LINC Release 16.3/16R3, this field has been changed to the Enforce dict (Y,S,N) field, 

and the new Enforce db items only field has been added to provide you with greater 

control when adding data items. 

Enforce dict (Y,S,N) Field 

Use this field to set the type of Dictionary enforcement for your LINC Specification: 

$ Enter Y to allow users to add data items that have been defined in your Dictionary. 

$ Enter N to allow users to add data items without restriction. 

$ Enter S to allow users to add data items that have been defined in your Dictionary, or 

that are defined to be the same as (by using the SAME.AS; Data Command) Dictionary 

items. 

v 1-3


You can use the Enforce db items only field to limit this setting to new database data 

items. 

Enforce db items only Field 

Use this field to apply the setting of the Enforce dict (Y,S,N) field to new database data 

items: 

$ Enter Y to apply the setting to new database data items. 

$ Enter N to apply the setting to all new data items. 

Enhanced Structure Selection in LINC Generate 

On the LINC Audit Inquiry Listing (ADQ) and LDL Listing Utility (LDL) screens, you can 

choose to select individual structures to be included in your listing. In LINC Release 

16.3/16R3, you can use the Continue from field to choose a starting point for the list of 

structures. This enables you to access the structures you require, without having to display 

multiple screens containing all structures. 

See your LINC Generate Operations Guide for descriptions of the ADQ and LDL screens. 

Enhanced Handling of Dates 

In LINC II Release 16.1/16R1, the System Data item GLB.CENTURY was included to supply 

the century for use in complex DATE.CONVERT; commands. GLB.CENTURY was updated 

if a date prior to the base year was used in the date conversion. This new value of 

GLB.CENTURY was used in subsequent date conversion, and could have caused problems 

interpreting dates. 

For example, if the base year is 1957, LINC initially sets GLB.CENTURY to 19. A year of 70 

is interpreted as 1970. A year of 40 is interpreted as 2040 and GLB.CENTURY is set 

automatically to 20. A year of 70 is subsequently interpreted as 2070. 

In LINC Release 16.3/16R3, you can choose whether or not to update GLB.CENTURY, by 

setting the DC; sets GLB.CENTURY field on the Primary Specification Options screen. A 

new System Data item GLB.DC-CC is automatically updated to contain the century of the 

date during date conversion. 

A conversion report is provided to ease migration. See ‘‘Date Handling ’’, in Section 2 for 

details. See your LINC Programming Reference Manual for details of the 

DATE.CONVERT; command and the Systems Data items GLB.CENTURY, GLB.DC-CC, and 

ACTMTH. 

Increased MAPPER File Header 

In LINC Release 16.3/16R3, you can now include 256 characters in a Report Frame you are 

using as the header for a MAPPER Extract file. This limit was 132 in previous releases. 

1-4 v

NewFeaturesforAllLINCSystems 

See the MAP LINC Painter command in your LINC Generate Reference Manual: Painter 

and Editor. 

Implementation of Debug Date and Time 

This feature enables you to test your LINC System with any date and time (for example, for 

the next century) without the risks associated with resetting the system time. You set the 

debug date and time for individual LINC Systems by using the LINC System command 

:DDT. You cannot use this feature in LINC Generate. 

Only user dates and times will change; internal dates and times are not affected. All files 

created or modified during testing still have correct (system) time stamps, and database 

recovery will not be affected. 

See your LINC Administration and Operations Guide for details of the LINC System 

command :DDT. 

Extended SENDLIST.STATIC; Command 

In LINC Release 16.3/16R3, the SENDLIST.STATIC; command has been enhanced to 

include standalone Reports, removing the following restrictions: 

$ For MCP based LINC Systems, that the LINC System be running in order to update 

static list boxes 

$ For LINC Systems based on the UNIX operating system, that the Report is initiated 

from PowerClient (Designer Workbench) 

$ For OS 2200 based LINC Systems, that the request to update a listbox came from a PID 

currently in use 

Consistent Initialization of Group Setup Data Items 

The initialization of Group Setup Data items and Group Global Setup Data item was 

subject to different behavior on the different host types. For example, for MCP based LINC 

Systems, you can move spaces to a Group Setup Data item that contains numeric Setup 

Data items. These numeric data items are interpreted as containing zero. For UNIX and 

OS 2200 based LINC Systems, this is not the case. 

In LINC Release 16.3/16R3, you can use the INITIALIZE; LINC logic command to ensure 

that initialization is the same across all host types. In addition, the command offers a wide 

range of choices of initial value. A conversion report is provided to assist you when 

migrating your LINC System. 

See your LINC Programming Reference Manual for the INITIALIZE; command and 

‘‘Initialization of Group Setup Data Items’’ in Section 2 of this guide for migration issues. 

v 1-5


Enhanced Checking of LINC Specifications 

In LINC Logic, it is possible to code MOVE; commands that will result in inconsistent or 

unexpected results. These commands are known as overlapping moves. In LINC Release 

16.3/16R3, you can check for overlapping moves by using the LINC Checker Utility (CHK) 

in LINC Generate. 

In addition, options available in the batch for the LINC Checker Utility have been 

extended. See your LINC Generate Operations Guide for details. 

Changes to support LCIF 

For LINC 16.3 a number of changes have been made to ensure compatibility with LDA 2.2 

and above. Changes to the LINC CASE interchange file (LCIF) enable Patch Identification 

and Change Identification information to be exchanged between the host and LDA. 

Changes to LINC to support this include: 

$ A new Supervisor Mode command to set the default level for CASE Extract. 

$ Two new options for the Choice field on the CASE Data Extract Request Screen. For a 

GLOBAL Specification, the user may choose to extract all patch and change 

information for the LINC Generate if the system’s valid extract level is set to allow this. 

For a Specification, the user may choose to extract an LDA 2.2 or 2.3 format LCIF 

which will include patch and change information for that Specification. 

$ Two new fields on the CASE Load Screen. Load Change Information allows the user 

to load LDA patch and change information from the LINC CASE interchange file. 

Audit with CC info from file enables the user to create Audit records from the 

CASE Load run using the LDA patch and change information. 

$ Two new parameters for batch CASE load: CCLOAD and CCAUDIT. 

1-6 v

New Features for MCP Based LINC Systems 


The following new features apply to MCP based LINC Systems. 

Extended RDB Capabilities 

For LINC Release 16.3, fields added to the A Series Configure Remote DB Options screen 

enable you to take advantage of the performance enhancements in the DMS II RDB 

feature. 

These fields are: 

$ ACK rate 

$ Delay audit file removal 

$ File transfer option 

$ Synch restart int 

For details, see the MCP Based LINC Administration and Operations Guide. 

Restriction Lifted on Transfer and Configure 

In releases prior to LINC Release 16.3, the name of a LINC System created during transfer 

or configure had to be identical to the name of the original generated LINC System. In 

LINC Release 16.3, the names can be different. 

When configuring and transferring a new LINC System, you can change the names of the 

LINC System and LINC Database by using the Home screen of the LINC Configure Utility. 

For automatic configure, you can change the names in the Generate Set. 

When performing a configure of an existing LINC System (either by Hands-on configure or 

by using a Generate Set) the names used in previous configures must be retained, or must 

be reentered on the Home screen of the LINC Configure Utility. 

You can also use the System Management Utility (SMU) to change the system, database 

and window names. 

See your MCP Based LINC Administration and Operations Guide for details on 

transferring your LINC System and SMU. 

Rebuilding Profiles from Ispec Tables 

In LINC Release 16.3, you can use the LINC Database Management Utility (DMU) to rebuild 

LINC Profiles from the LINC Ispec tables associated with the Profile. This will enable you 

to take advantage of situations when it is quicker to rebuild a Profile file from the base 

table rather than recover the whole database. You may also find this feature useful if your 

Profile set has been corrupted. 

v 1-7


See your DMS II Utilities Options Guide for guidelines on deciding whether it is more 

efficient to rebuild the set or subset from the data set, or to rebuild from the set or subset 

itself. 

Correct Calculation of Blocksize 

In LINC II Releases 16.1 and 16.2, blocksizes were calculated incorrectly for some 

structures, and were different to the sizes shown on the DASDL Options (CDLA) screen in 

LINC Generate. 

In LINC Release 16.3, blocksizes are calculated correctly. Structures affected are those 

that are a half byte less than a multiple of 6 bytes (for example, 17.5 and 23.5 bytes) and 

that have defaults set on their DASDL Options screen. 

Note: This change may lead to unexpected reorganizations of your LINC Databases 

after migration. 

Avoiding reorganization 

To avoid reorganizations due to blocksize changes: 

1. Open the file system/SOURCE/DMS. 

2. Identify the structures that are affected by this change. 

Look at the trailer records which contain the record lengths. The trailer record begins 

with %%%%%TRAILER, and the record length is in a 6 digit field at position 39. This 

field includes one decimal, so that the value 000175 indicates a record of length of 

17.5 bytes (which would be affected). 

3. Access the DASDL Options screen in LINC Generate. 

4. For each structure you identified in Step 2, enter the blocksize value from LINC II 

Releases 16.1 or 16.2. 

You can now generate your LINC System. 

Use of Connection Libraries for HUB 

Prior to LINC Release 16.3, default timeout values were used to detect client or server 

program failure for HUB (external Automatic Entry) transactions. 

In LINC Release 16.3, the HUB facility uses the Connection Library system software 

feature, which enables the establishment of a two-way interface with calling LINC 

Systems. This can lead to improved response. In addition, an abort of any attached 

program is detected, enabling immediate transaction aborting or recovery procedures 

(depending on the transaction status of the particular program that aborted). 

1-8 v

Diagnostics 


HUB diagnostic routines have been modified so that the diagnostic print file is written by 

the LINC16/1/LIBRARY library, and the printer backup file produced is located under the 

mix number of that library (rather than the HUBRouter library). (As in previous releases, 

you to use the HUBRouter library to activate the diagnostics.) This change enables 

diagnostics to be collected in the LINCSUPPORT library before the library connection to 

HUBRouter is established, and after the library connection is terminated. 

Compatibility with LINC II Releases 16.1 and 16.2 

In LINC Release 16.3, the LINC libraries will continue to provide the existing interface for 

programs that are not regenerated, or for existing LINC Systems from LINC II Releases 

16.1 and 16.2. The functionality of these systems is unchanged. 

Compatibility with LINC II Release 15 

The functionality of LINC Systems from LINC II Release 15 is unchanged. 

Changes to Usercodes for Reports 

LINC Generate Reports 

LINC Generate uses LINC Reports to perform some functions. For example, LCOPY 

includes the Report CPY. 

In releases prior to LINC Release 16.3, Reports that performed LINC Security Module 

(LSM) security checks used the usercode of LINC Generate when the Report was initiated 

using the LINC Report Initiation Program (RIP). In LINC Release 16.3, the usercode that 

initiated RIP is used for LSM security. 

Automatic Entries in Reports 

In releases prior to LINC Release 16.3, when a Report was initiated, GLB.USERCODE was 

set to the usercode of the LINC System. 

In LINC Release 16.3, external Automatic Entries received through HUB for Reports 

initiated by RIP have GLB.USERCODE set to the usercode that initiated RIP. For Reports 

initiated by using the RUN; LINC logic command or :RUN LINC System command, the 

usercode is the usercode of the station initiating the Report. 

Restriction Lifted for BNA Generates 

In releases prior to LINC Release 16.3, MCP based LINC Systems generated using a BNA 

generate (BNA gen field of the Configure Options screen) could only be transferred to and 

configured on the environment defined in the BNA Generate Set (or to an RDB secondary 

standby environment). In LINC Release 16.3, this restriction has been lifted. 

These LINC Systems can now: 

v 1-9


$ Be transferred using other Generate Sets (using the Configure Generate set field on 

the Transfer Selection screen) 

$ Be defined as base systems for Model LINC Systems 

If the Generate Set used to configure your LINC System is a BNA Generate Set, it must be 

the same Generate Set used to generate the LINC System. This restriction ensures that all 

DMS files are compatible. 

Specifying Sort Memory 

In LINC Release 16.3, you can specify the amount of sort memory to be used when 

database reorganizations are required. This new feature will improve the times taken to 

perform reorganizations, especially of large databases. 

The Allowedcore field has been added to the A Series Generate Options screen to enable 

you to enter the amount of memory to use. The A Series Generate Options screen is 

described in your LINC Generate Operations Guide. Similar fields have been added to the 

Environment Options screen of the Configure Utility and the Home screen of the Database 

Management Utility (DMU). 

Before using this feature, you should check the hardware your site is using can provide the 

amount of memory you intend to use. 

The default value for the Allowedcore field is 0 (zero), which means that a default value of 

12,000 words per reorganization task (the same as in releases prior to LINC Release 16.3) is 

used. 

Avoiding Unplanned Reorganizations 

In LINC Release 16.3, you can take advantage of the DASDL options POPULATIONINCR 

and POPULATIONWARN to reduce unplanned reorganizations when database structures 

reach their logical capacity. These options enable you to automatically increase the 

population of a structure, or to request a warning when the population approaches the 

limit. 

For a generated LINC System, or a LINC System configured using a Configure Generate 

Set, the population options can be set for the entire database, or for individual Ispecs (the 

Event set is considered as a single Ispec). For a LINC System configured using the LINC 

Configure Utility, the options can be changed only for the entire database. You can use 

DMU to set the options for the database, individual Ispecs, or the Event set. 

See your MCP Based LINC Administration and Operations Guide for generation issues. 

Improved Offline Reorganizations 

1-10 v


In LINC Release 16.3, you can use features of DMS II that deliver improved performance 

and restartability of unaudited online reorganizations. Fields on the A Series Generate 

Options screen in LINC Generate enable you to choose the method of handling 

reorganizations. 

See your MCP Based LINC Administration and Operations Guide for complete details of 

this feature and your LINC Generate Operations Guide for details of the fields. 

Support for Features of DMS II XE 

In LINC Release 16.3, you can use DMS II Extended Edition (DMS II XE) features. This 

eases the strain on very large and busy LINC Systems by enabling you to specify multiple 

sections for any set or dataset. 

In previous releases, each dataset (Component or Event set) or set (Profile) consisted of 

one file, which could become unmanageably large or reach its size limit. DMS II XE 

enables you to specify a number of sections (each one a separate file) for any set or 

dataset. This will increase the available size of the set or dataset, and improve access for 

large and busy LINC Systems, as the files can be distributed across a number of packs. 

DMS II XE includes transtamp locking (enabling individual sections to be locked 

independently) and an RSN word (which efficiently resolves profile duplicates). 

You can enable use of DMS II XE enables either globally (on the Generate Set Global 

DASDL Defaults screen of LINC Generate) or for individual datasets (Component or Event 

DASDL Options screen). You can specify the number of sections for datasets (Component 

or Event DASDL Options screen), or for sets (Profile DASDL Options screen and a new 

Profile Section Definition screen). 

Control of Report Output Files 

In LINC Release 16.3, the ATTRIBUTE; LINC logic command enables you to control Report 

output files for non-ROC and ROC Direct Reports for MCP based LINC Systems. See your 

LINC Programming Reference Manual for details. 

Handling Five Digit Mix Numbers 

In LINC Release 16.3, mix numbers up to 5 digits are now supported, in line with MCP 

SSR45.1. 

In LINC Release 16.3, mix numbers are stored in Log files in four bytes as in previous 

releases. However, each mix number is now stored in eight half-bytes. Log, Trace View, 

and Examiner files are not compatible with previous releases. See your MCP Based LINC 

Administration and Operations Guide for details. 

Mixed Kanji Data in Ad Hoc Queries 

v 1-11

New Features for OS 2200 LINC Systems 

For LINC Release 16.3, you can now use mixed Kanji data in Ad Hoc queries. You must 

reedit any existing Ad Hoc queries to take advantage of this new functionality. 

New Features for OS 2200 Based LINC Systems 

The following new features apply to OS 2200 based LINC Systems. 

Installing with SOLAR 

For LINC Release 16R3, the installation tools have been changed to use the designated 

Unisys tool, SOLAR, to install LINC Deployment. You still use COMUS to configure and 

build the LINC Deployment prior installing it using SOLAR. 

Enhanced Debugging Facility 

In LINC Release 16R3, the LINC System command :DBG has been enhanced. You can use 

this command for LINC Systems and LINC Reports to: 

$ Output a full dump of your database and OLTP buffers. 

$ Print traced information in your own format, by using the USERDBG routine. This 

feature applies only to LINC Systems and LINC Reports generated in UCS mode. 

See your OS 2200 Based LINC Administration and Operations Guide. 

Dynamically Changing Recovery Method 

In LINC Release 16R3, you can use LRU to dynamically change your choice of database 

recovery method. In previous releases, you were required to choose your recovery method 

(Quick Look method or Deferred Updates method) before generating your LINC System. 

This change does not apply to LINC Reports. 

Immediate Effect of LSM Changes 

In LINC Release 16R3, the LINC Security Module (LSM) has been enhanced to action 

changes immediately. When LINC Security is turned on, security checking is actioned 

immediately for all users, even those currently signed on to the LINC System. This may 

cause the Userid/Password screen to be displayed when the next transmit occurs. 

See your OS 2200 Based LINC Administration and Operations Guide for a description of 

LSM. 

Confirming Installation after Generation 

1-12 v


For LINC Release 16R3, the Confirm generates with install? field has been added to the 

OS 1100 Generate Options screen. If you enter Y in this field when you are generating your 

LINC System, you are asked to confirm that you want your generated system to be 

installed automatically. 

See your LINC Generate Operations Guide for details of the OS 1100 Generate Options 

screen. 

Increased Efficiency of Storage of Numeric Items 

LINC Release 16R3 enables you to take advantage of System Software level SB5R4 to 

reduce the amount of storage required for numeric values longer than length 10. With these 

changes, the existing System binary numerics field have been extended, and from LINC 

Release 16R3, binary numeric settings will apply to all numeric items. 

See the description of the System binary numerics field in your LINC Generate 

Operations Guide. 

Support for SDF Format Tapes 

LINC Release 16R3 supports the SDF tape format for Extract files. In previous releases, 

only the Interchange and IBM tape formats were supported. 

See the description of the Extract File Options Screen in your LINC Generate Operations 

Guide. 

Rebuilding Profiles from Ispec Tables 

In LINC Release 16R3, you can use the Configure function of LRU to rebuild LINC Profiles 

from the LINC Ispec tables associated with the Profile. This will enable you to take 

advantage of situations when it is quicker to rebuild a Profile file from the base table rather 

than recover the whole database. You may also find this feature useful if your Profile data 

has been corrupted. 

Implementation of GLB.TASK 

In LINC Release 16R3, the System Data item GLB.TASK has been implemented to enable 

you to pass task status information when running LINC Reports. The value of GLB.TASK is 

stored in the Run Condition Word. 

Note: LINC Reports generated as LINC Subroutines cannot use this feature. 

See your LINC Programming Reference Manual for details of GLB.TASK. 

Efficiency of SA$ Storage Area 

v 1-13


For releases prior to LINC Release 16R3, the SA$ file contained a variety of RDMS tables. 

The same storage area parameters applied for all tables, and as these were often accessed 

at the same time, the efficiency of the use of system resources was decreased. 

For LINC Release 16R3, the RDMS storage area SA$ has been divided into separate files, 

with each file now containing tables that have common uses. This change improves the 

efficiency of access to the appropriate RDMS tables and therefore improves the 

performance of your LINC System, especially when initiating and terminating LINC 

Reports. 

Remapping and Relinking All Reports 

In LINC Release 16R3, you can use the MAPALLREPS SGS parameter to enable the 

remapping and relinking of all your LINC Reports when reconfiguring your LINC System 

from disk. For previous LINC Releases, you had to remap and relink your LINC Reports 

using the Report Batch Generate facility. 

Initializing with MCB When Using USERPRT 

In LINC Release 16R3, a new execution option for LINC Reports causes your Direct 

Reports to initialize with the MCB before the call to USERPRT. See your OS 2200 Based 

LINC Administration and Operations Guide for details. 

Note: You must regenerate LINC Reports in your current release of LINC before 

migrating to the LINC Release 16R3. 

Operator Keyins 

In LINC Release 16R3, LINC Deployment has been enhanced to: 

$ Replace II keyins with operator console commands for the LINC Background Run and 

HUB Background run. This enables you to enter commands more conveniently. 

$ Provide the ability to enter ROC spooler commands from an operator console (in 

addition to entering them from a TIP terminal), and expands the range of ROC spooler 

commands. 

1-14 v

New Features for LINC Systems based on the UNIX operating system 

New Features for LINC Systems based on the UNIX 

operating system 

The following new features apply to LINC Systems based on the UNIX operating system. 

Terminating Your LINC System 

The shell script runsys stop and LINC System command :STO can be used to terminate 

LINC Systems based on the UNIX operating system. In releases prior to LINC Release 16.3, 

these two methods differed slightly in their effect. 

In LINC Release 16.3, the shell script runsys stop has been changed to terminate your LINC 

System in the same way as the LINC System command :STO. Both methods will close 

down the LINC System and all Reports. With both methods you can choose to disable the 

LINC System. 

See your LINC Administration and Operations Guide for the UNIX Operating System 

for details of these methods. 

Improvements to Disk Space Use for ORACLE 

LINC Release 16.3/16R3 improves the disk space usage characteristics of the reorganization 

process of ORACLE LINC Systems. It also significantly reduces the likelihood of users 

reaching the 2 Gigabyte limit on file sizes that exists on most current UNIX host types. 

Two new LINC variables now available are LINCII_REORG_COMPRESS and 

LINCII_REORG_SINGLE. These variables enable data involved in database reorganization 

to be compressed on disk and structures to be reorganized serially. The default values for 

these variables is N, which matches the current implementation. 

This feature is implemented in the shell scripts and utilities associated with the database 

generation process of an ORACLE LINC System. In particular this will affect the dac utility, 

the dmake6 driving shellscript, and the load and unload utilities. 

Transferring LINC Systems in Object Format 

From LINC Release 16.3/16R3 you can transfer LINC systems as object code between 

compatible UNIX machines. You can transfer LINC system object code via transfer media 

such as tape or disk or via TCP/IP. The minimum system transferred comprises 

$ Bound executables 

$ Ispecs, reports, and separately compiled global logics 

$ LINC system control files 

v 1-15

New Features for LINC Systems based on the UNIX operating system 

Transferring a LINC system as object code eliminates the need to recompile and rebind the 

transferred LINC system on the target UNIX machine. Previously you could only transfer a 

UNIX system as source which you then had to recompile and rebind. 

You can access this new functionality through the Runtime System Transfer Menu. 

Upgrading Your Own LINC Executables with Object Packaging 

From Release 16.3, LINC software based on the UNIX operating system is distributed in 

object code format as well as in executable format. Also from Release 16.3, LINC 

Engineering Interim Fixes (EIFs) based on the UNIX operating system are distributed only 

as object code. Object packaging means you can maintain your own LINC environment on 

site. You can use Object Packaging to build new executables from LINC and EIF object 

code. You can then install your newly created LINC executables. This approach means 

timely support for newly qualified software and for new LINC features and fixes. 

Object Packaging allows you to create new packages qualified with different versions of 

support software and to create backup packages in both executable and object formats. 

When they are made available in EIFs, you will have a choice of versions of the following 

underlying software: 

$ ORACLE 

$ Griffin 

$ Tuxedo 

$ COBOL 

You access Object Packaging through the Product Menu utility. 

1-16 v

Section 2 

Migrating to LINC Release 16.3/16R3 

Overview 

This section covers the following topics: 

$ ‘‘Terminology Changes in LINC Release 16.3/16R3’’ 

$ ‘‘Migrating from Releases Earlier than LINC II Release 16.2/16R2’’ 

$ ‘‘Migrating to LINC Release 16.3/16R3’’ 

$ ‘‘Addressing Migration Issues’’ 

$ ‘‘Generating Your LINC Systems after Migration ’’ 

Terminology Changes in LINC Release 16.3/16R3 

Significant terminology changes have been made in LINC Release 16.3/16R3. The following 

table contains the equivalent terms from the previous release. 

LINC II Release 16.2/16R2 LINC Release 16.3/16R3 Comment 

LDA III LDA Primary development tool 

LINC Development System LINC Generate Generates systems 

LINC Run Time LINC Deployment Deploys systems 

v 2-1

Migrating from Releases Earlier than LINC II Release 16.2/16R2 

Migrating from Releases Earlier than LINC II Release 

16.2/16R2 

Finding Documentation 

Using LCOPY 

If you are migrating from LINC II Release 16.1/16R1, in addition to this guide you should 

refer to the LINC II Release 16.2/16R2 New Features Guide. 

If you are migrating from an earlier release, for example LINC II Release 15.3/15R3, refer to 

the following sections of the LINC II Release 16.1/16R1 Library in addition to the LINC II 

Release 16.2/16R2 New Features Guide: 

$ Section 5 of the A Series LINC II Installation and Configuration Guide 

$ Appendix D of the OS 1100 LINC II Installation and Operations Guide 

$ Appendix D of the LINC II Administration and Operations Guide for the UNIX 

operating system 

When copying LINC Specifications by using LCOPY, you must use the release of LINC 

Generate or LINC Development System, as shown in the following table. 

Loading into earlier releases 

From To 14 To 15 To 16 

14 Y Y Y 

15 - Y Y 

16 - - Y 

Using LCOPY, you can load LINC Specifications created in (or migrated to) LINC II 

Release 16.3/16R3 into LINC II Release 16.1/16R1 and LINC II Release 16.2/16R2. You may 

encounter syntax errors if the LINC Specification includes features specific to LINC 

Release 16.3/16R3. 

When you load a LINC Specification in this way, all logic lines are marked for re-edit. 

You require an EIF to your LINC II Release 16.1/16R1 and 16.2/16R2 Software in order to 

load LINC Specifications from LINC Release 16.3/16R3. Contact your Unisys representative 

for details. 

2-2 v

Migrating from Releases Earlier than LINC II Release 16.2/16R2 

Using LCOPY Compare across major LINC Releases 

Between major releases of LINC Generate (for example, LINC Release 15 and LINC 

Release 16), there are often differences in how LINC Specifications are stored. 

You cannot use the LCOPY Compare function to compare LINC Specifications across 

major releases. 

v 2-3



This subsection describes the procedure for migrating to LINC Release 16.3/16R3. 

Migration Procedure 

Use the following procedure to migrate your LINC Systems. 

1. Study the new feature descriptions in Section 1. It is important that you understand 

the implications of each new feature. 

2. Take note of the various migration issues outlined in ‘‘Addressing Migration Issues’’. 

3. Ensure that your existing LINC Systems and LINC Specifications are backed up. 

4. It is recommended that you perform a syntax-only generate of your LINC System. 

5. Ensure that the appropriate system software is installed. 

6. Use one of the following procedures to migrate from LINC II Release 16.2/16R2 to 

LINC Release 16.3/16R3: 

$ Use LCOPY to extract your LINC Specifications from LINC II Release 16.2/16R2 

and load them into LINC Release 16.3/16R3. See ‘‘Using LCOPY to Migrate to 

LINC Release 16.3/16R3’’. 

$ Install LINC Release 16.3/16R3 over your existing installation. See ‘‘Installing 

Over LINC II Release 16.2/16R2’’. 

7. Address any migration issues, as outlined in ‘‘Addressing Migration Issues’’. 

8. Generate your LINC Systems. See ‘‘Generating Your LINC Systems after Migration ’’. 

Generating OS 2200 Reports before Migrating 

For LINC Release 16R3, a new execution option has been implemented for LINC Reports. 

This option causes your generated Direct Reports to initialize with the MCB, before the call 

to USERPRT. 

To use this feature, you must perform one of the following. 

$ Add the N option to the @XQT report statement in the system*REP$RUN.report 

element. 

$ Manually add the N option to the @XQT report statement when running the Direct 

report from Demand mode. 

You must regenerate LINC Reports in your current release before migrating to LINC 

Release 16R3. 

Updating local patches to CCsversion for MCP based hosts 

If you are migrating from LINC II Release 15 to MCP based LINC Release 16.3, and you 

have applied a local patch to set CCsversion in the DASDL, Update programs, and Reports, 

you must ensure that the correct CCsversion is applied in the DASDL Defaults screen 

before your first generate your LINC Systems under LINC Release 16.3. 

2-4 v


This removes the need for any unnecessary reorganizations, and marks all of the Updates 

and Reports for extraction and compilation. 

Notes: 

$ As the PROGRAM COLLATING SEQUENCE is defined in Update programs and 

Reports, changes in functionality may occur in your LINC System. 

$ As Update programs and Reports automatically use the same CCsversion defined for 

the database, a performance impact may be noticed. 

Migrating to LINC Deployment for Windows NT 16.3 

If you are migrating from LINC Deployment for Windows NT Release 16.2 to Release 16.3, 

you can no longer deploy a LINC Systems generated on an MCP based LINC System. You 

can only deploy LINC Systems generated using the Direct Generate feature of LDA. 

See LINC Deployment for Windows NT Getting Started for more information. 

Using LCOPY to Migrate to LINC Release 16.3/16R3 

Use the following procedure to migrate from LINC II Release 16.2/16R2 to LINC 

Release 16.3/16R3: 

1. Unload your existing LINC Specifications (including GLOBAL) from your LINC 

Development System, by using LCOPY. 

2. Install LINC Release 16.3/16R3. 

3. Load your LINC Specifications into your new LINC Generate, by using LCOPY. 

4. Generate your LINC Systems, as described in ‘‘Generating Your LINC Systems after 

Migration ’’. 

Detailed documentation 

LCOPY is documented in LINC Developers Guide: LCOPY. 

Installing Over LINC II Release 16.2/16R2 

When you install LINC Release 16.3/16R3, you can choose to retain the LINC Specifications 

in your existing LINC II Release 16.2/16R2 LINC Development System. 

Generate your LINC Systems, as described in ‘‘Generating Your LINC Systems after 

Migration ’’. 

You can use this method to migrate directly from LINC II Release 16.1/16R1. You must 

however, refer to the migration issues contained in the LINC II Release 16.2/16R2 New 

Features Guide, as well as those included in this guide. 

v 2-5


Detailed documentation 

The installation procedure is described in your LINC Installation and Configuration 

Guide. 

2-6 v

Addressing Migration Issues 


Before you generate your LINC Systems in LINC Release 16.3/16R3, you must address the 

following issues: 

$ Environmental Settings 

$ Date Handling 

$ Initialization of Group Setup Data Items 

$ Numeric Data Items for OS 2200 LINC Systems 

$ PowerClient (Designer Workbench) Release 2R1 

Environmental Settings 

Date Handling 

You may wish to check the environmental settings for each LINC Specification. Examples 

of possible changes are: pack allocations, integrity settings, log settings, subsystem 

allocations, and whether audit files are to be copied to tape. However, before you make 

any such changes, first check that the migration information (both in this section and in 

your release information) does not specifically exclude that type of change. 

Do not, for example, change any data items or logic. 

In LINC Release 16.3/16R3, the handling of dates has been improved. This feature is 

described in ‘‘Enhanced Handling of Dates ’’, in Section 1. 


To migrate your LINC Systems and take advantage of this feature: 


2. Perform a syntax-only generate of your LINC System, and of its Reports. This ensures 

all logic lines are not marked for regeneration. Otherwise the performance of the 

CONVDATE report can be affected. 

3. Check changes by running CONVDATE in print mode. When ready, run in update 

mode. Logic lines which move the value of GLB.CENTURY are converted to use 

GLB.DC-CC. 

4. Set the DC; sets GLB.CENTURY field on Primary Specification Options screen to 

N. 

For LINC II Releases 16.1 and 16.2, there is no DC; sets GLB.CENTURY field. Instead, 

you must use DCSET + and DCSET - Supervisor (SUP) commands in LINC Generate 

(although these commands are not listed on the screen). You require an EIF to enable the 

use of these commands. Contact your Unisys representative for details. 

v 2-7


About CONVDATE 

The report CONVDATE searches a LINC Specification to find all uses of GLB.CENTURY as 

input, and converts them to use GLB.DC-CC: 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The report can be run in print and in update mode (that is, run the report in print mode to 

print all the lines of logic that it will change in update mode). 

Running CONVDATE 

1. Initiate the Report. 

$ For MCP based LINC Systems, use the following LINC System command from 

LINC Generate 

 

$ For OS 2200 LINC Systems, enter the following @XQT command from a Demand 

session (here generate is the name of LINC Generate): 

 

When the Report is complete, enter the following @XQT command from a 

Demand session 

 

$ For LINC Systems based on the UNIX operating system, from the shell, move the 

directory of LINC Generate, and enter the following command: 

 

2. You are asked for the details in the following table. 

2-8 v

Detail Description 


Specification name Enter the name of a LINC Specification. You may not enter the name 

of a Module, nor may you enter GLOBAL or ALL. 

Mode Enter P to print the lines of logic that will be changed, U to update the 

lines of logic, or B to print and update. 

Apply change control to 

affected lines 

Audit changes to 


Enter Y to apply changes for affected lines. You are only asked this 

question if auditing is set for your LINC Specification. 

Enter Y to audit changes to affected lines. You are only asked this 


Change identifier Enter an existing change identifier if change identification is in effect 

for the LINC Specification. 

Patch number If patch identification is in effect you can enter an existing, open 

patch, or a new patch number. Alternatively you can make no entry, in 

which case the next available patch is used. The patch is left open on 

completion of the report. 

Initialization of Group Setup Data Items 

In LINC Release 16.3/16R3, the handling of the initialization of Setup Data items has been 

improved. This feature is described in ‘‘Consistent Initialization of Group Setup Data 

Items’’, in Section 1. 


To migrate your LINC Systems and take advantage of this feature is: 


2. Perform a syntax-only generate of your LINC System, and of its Reports. 

3. Check changes by running CONVINIT in print mode. 

4. Run CONVINIT in update mode. 

About CONVINIT 

The report CONVINIT searches a LINC Specification to find all uses of MOVE; 

GLB.SPACES {item} and converts them to use the new command, as follows: 

$ Replaces MOVE; GLB.SPACES {group} with INITIALIZE; {group}. 

$ Replaces similar logic that uses GLB.ZEROS, GLB.LOW, and GLB.HIGH. 

$ Reports logic in the form DO.WHEN; {group} = GLB.SPACES (or GLB.ZEROS, 

GLB.LOW, or GLB.HIGH). You may need to modify these tests, because with the new 

command this test will now fail if the group contains numeric items. These are only 

printed if you entered R for the Mode when you ran CONVINIT. (See "Running 

CONVINIT", later in this subsection.) 

v 2-9


$ In Global Logics, replaces MOVE; GLB.SPACES {item} with the equivalent INITIALIZE; 

command, where {item} is a Setup Data item defined outside the Global Logic, and is 

defined as a Group Setup Data item somewhere in your LINC Specification. Each 

INSERT; command of the Global Logic is marked for re-edit. 

The CONVINIT report can be run in print and in update mode (that is, run the report in 

print mode to print all the lines of logic that it will change in update mode). You should run 

the report after a syntax-only system generate (by entering Y in the Syntax only field of 

the Generate Options screen), and a syntax-only Report Batch generate (by entering Y in 

the syntax-only field of the Report Batch Options screen) of all reports. 

Running CONVINIT 

1. Initiate the Report. 

$ For MCP based LINC Systems, use the following LINC System command from 


 

$ For OS 2200 LINC Systems, enter the following @XQT command from a Demand 

session (here generate is the name of LINC Generate): 

 

When the Report is complete, enter the following @XQT command from a 

Demand session 

 

$ For LINC Systems based on the UNIX operating system, from the shell, move the 

directory of LINC Generate, and enter the following command: 

 

2. You are asked for the details in the following table. 


Specification name Enter the name of a LINC Specification. You may not enter the name 

of a Module, nor may you enter GLOBAL or ALL. 

Mode Enter R to print the lines of logic that require checking or enter U to 

update and print all changed lines. 

Apply change control to 


Audit changes to 


Enter Y to apply changes for affected lines. You are only asked this 


Enter Y to audit changes to affected lines. You are only asked this 


Change identifier Enter an existing change identifier if change identification is in effect 

for the LINC Specification. 

continued 

2-10 v

continued 



Patch number If patch identification is in effect you can enter an existing, open 

patch, or a new patch number. Alternatively you can make no entry, in 

which case the next available patch is used. The patch is left open on 

completion of the report. 

Numeric Data Items for OS 2200 Based LINC Systems 

In LINC Release 16R3, additional facilities are provided for the handling of numeric data 

items. When you migrate your LINC System to LINC Release 16R3, the Data Attribute 

NUMERIC.FORMAT; DEC is added to numeric data items whose length attribute is greater 

than 10. This ensures that the definition of the numeric item remains the same as you 

defined for the previous release, and therefore does not cause a reorganization of your 

LINC Database. 

You may wish to review the settings of the NUMERIC.FORMAT; Data Attribute for the data 

items in your LINC Specification. See ‘‘Increased Efficiency of Storage of Numeric Items ’’ 

in Section 1. 

PowerClient Release 2R1 

Using PowerClient 

If you do not wish to use PowerClient, set the DW capable system field on the System 

Environmental Options screen to N. 

If you intend to use PowerClient, then before generating any migrated 

PowerClient-capable LINC System, use the Designer Workbench Options screens to enter 

values corresponding to the information in your existing WDPMAP file. 

Migrating existing PowerClient screens 

LINC Release 16.3/16R3 supports PowerClient Release 2R1. By using PowerClient 

Release 2R1, you can make many forms changes at your PC without causing the screen 

layouts to be downloaded from the host. 

Caution 

If you make changes, you are responsible for ensuring that the data item definitions 

in the forms match those defined in your LINC System. 

v 2-11

Generating Your LINC Systems after Migration 

Generating Your LINC Systems after Migration 

Procedure 

To generate your migrated LINC Specifications, perform the following procedure. 

1. Sign on to LINC Generate for LINC Release 16.3. 

2. Log on to a migrated LINC Specification. 

Note: For Modules, you must complete a syntax-only generate of the 

Module Master (including all Reports) before you generate any 

Modules. 

3. Access the Generate screen. Enter N in the Stop on first error field, and Y in the 

Syntax only field, and generate the system. 

The first system generate following migration may take longer than at other times. 

4. Correct any errors found. 

Note: If your LINC Specification contains nested Performable Global 

Logics that bring data into memory, errors may be reported where 

an Ispec manipulates data read in by a Performable Global Logic. 

The error can be resolved by including a dummy read, or by 

repositioning the logic that performs the read. 

5. At this point, you may wish to run the CONVINIT and CONVDATE reports, so that 

you can take advantage of LINC Release 16.3/16R3 features. See ‘‘Addressing 

Migration Issues’’. 

6. Access the Generate screen again. Enter Y in the Stop on first error field, and N in 

the Syntax only field, and generate the system. 

7. When your LINC System generation and reorganization are complete, generate all 

Reports. 

8. If you are using System Transfer and Configure for your LINC Systems, perform the 

transfer and configure of your LINC Systems. 

Caution 

Do not start up your system until the generation process has been fully completed. 

2-12 v

Section 3 

Migrating to LINC Development 

Release 2.3 

Read this section in conjunction with your LINC Development Installation and 

Administration Guide if you are migrating an existing LDA installation to LDA Release 2.3. 

Note: You must extract and reload your repository and reorganize any existing 

runtime databases. Release 2.3 uses a new repository and a new runtime 

Database. See your LINC Development Installation and Administration Guide. 

Considerations 

In migrating LINC development you must be aware of the following: 

$ The LDA Repository and database structure have changed for Release 2.3. You must 

perform a full extract and reload of your LDA Repository and your security database. 

Refer to your LINC Development Installation and Administration Guide for more 

information. 

$ Ensure that each machine meets the minimum requirements specified in your LINC 

Development Installation and Administration Guide. For best user response time, 

provide the recommended values, not the minimum ones. 

$ An empty LDA Repository for LINC Development Release 2.3 requires more disk space 

than an empty LDA Repository for Release 2.2. For Release 2.3 you need 8.0MB for an 

empty LDA Repository whereas for Release 2.2 1.28MB was required. 

$ Some additional disk space may be required to store Systems data. If the Model you 

are migrating from LINC Development / LDA III Release 2.2 to LINC Development 

Release 2.3 does not contain Generate Set data, there may be a slight increase in the 

size of the LDA repository. 

Because Generate Sets are now fully supported in LINC Development, the load 

process will require you to define a System Name if it detects that the Model file being 

migrated to LINC Development Release 2.3 is from an earlier release or created by host 

LINC, and contains Generate Set data. In previous releases, Generate Set data was 

stored in the LDA Repository and you did not have access to it from the LINC 

Development environment. 

$ If you are using the Direct Generate facility to generate LINC Runtime systems to a 

Windows NT target host, you will require additional disk space to store generate 

history information. 

$ If you plan to audit development operations, you may require a considerable amount of 

extra disk space to store audit logs. 

v 3-1

Repository 

Repository 

$ If you plan to use the new LDA Version Control feature, you will require additional 

disk space. As a minimum, the Version Control Server requires a Pentium 133 with 

64MB of RAM and a 100MB pagefile. Each connection to the Version Control Server 

takes 10MB. The Universal Repository (UREP) software requires a minimum of 30MB. 

The minimum requirement for the Version Control Bank is 350MB. When the OSMOS 

database is created it pre-allocates the hard disk space required. As you add objects to 

the Bank, the pre-allocated space is used up. Once the space is used up, you cannot 

add any more objects to the Bank with expanding it. 

$ If you are migrating from Release 1.3, you should also consider the following: 

v LDA Release 2.3 requires a 32-bit operating system. The LDA Server runs only on 

Windows NT. Windows NT is also recommended for the client workstations. 

v Since LDA Release 2.2, numerics in the database are stored in a different format. 

You need to convert existing numeric data to this format. This is done by 

physically reorganizing the LDA Run Time database. If a physical reorganization is 

not done and old format numerics are found, you will be warned that you can only 

continue by using logical reorganization. 

To ensure successful migration: 

1. Install the software according to the recommendations in your LINC Development 

Installation and Administration Guide. 

2. Configure the software according to the recommendations in your LINC 

Development Installation and Administration Guide. 

3. Reload the repository and security details, and validate each business segment. 

4. Reorganize the LDA Run Time database. 

To extract the existing repository, use the procedure in your LINC Development 

Installation and Administration Guide. 

3-2 v

Section 4 

Loading LINC Specifications from LDA 

into LINC Generate 

Overview 

This section contains the following topics: 

$ ‘‘Preparing to Load an LCIF File’’ 

$ ‘‘Restrictions on CASE Load’’ 

$ ‘‘CASE Load Screen’’ 

$ ‘‘Generating Your LINC System after Loading’’ 

$ ‘‘Recovering a Failed CASE Load’’ 

$ ‘‘Running CASE Load in Batch’’ 

$ ‘‘Description of the Load Process’’ 

Unloading (Extracting) a LINC Specification from LINC Generate 

To unload (extract) a LINC Specification from LINC Generate, use the CASE Extract 

screen in LINC Generate, as described in Section 5. 

v 4-1

Preparing to Load an LCIF File 

Preparing to Load an LCIF File 

Ensure there are no locks 

Ensure that no parts of the LINC Specification that are to loaded are locked. If they are, the 

load may fail. 

LCIF release levels 

Only LCIF files from LDA Release 1.3 and Release 2.1 or later can be loaded. 

KANJI LCIF Files for OS 2200 based LINC Generate 

For Kanji, the LCIF file is always in SHIFTEDJIS format. Any Kanji translation from 

SHIFTEDJIS format to the host Kanji representation is performed by the upload / 

download program supplied by Nihon Unisys Limited (NUL). 

LCIF Files Created by LDA 

LCIF file creation by LDA trims trailing spaces from all record types. When you transfer an 

LCIF file from LDA to an MCP or an OS 2200 based host, fixed-length records are written. 

Generate Set Considerations 

As the LCIF file formats for LDA Release 1.3 contain only Environmental options records 

for each host, the Environmental option record for current host type is used as the Primary 

Generate Set. A full CASE Load generates a Primary Generate Set of the name of the LINC 

System. A partial CASE Load uses the existing Primary Generate Set. 

The other environmental options records (those for host types other than that on which 

the load is being run) are loaded into Generate Sets named ASERIES, OS1100, orUNIX,as 

appropriate. For a full load, these Generate Sets are created, if required. For a partial load, 

they are used only if they already exist. 

From LDA Release 2.1, all Generate Set information contained in the LCIF file is loaded 

during a full load and extracted when you run a CASE Extract. If the primary Generate Set 

is not for the appropriate host type, the first Generate Set (alphabetically) for the host type 

is used. If there is no such Generate Set, then a primary Generate Set named ASERIES, 

OS1100, orUNIX, as appropriate, is created. 

4-2 v

Restrictions on CASE Load 

The following restrictions apply to the CASE Load program: 

Restrictions on CASE Load 

$ Only LCIF files from LDA Release 1.3 and Release 2.1 and later can be loaded. 

$ CASE Load locks the whole LINC Specification for a full load until the load is 

complete. For a partial load, the affected parts of the LINC Specification are locked. 

Locks are released when the load is complete. You can unlock manually by using the 

RESET CLD Supervisor command. 

$ The loading of an LCIF file is subject to the same validation rules as is normal user 

input using LINC Generate. There are some minor exceptions for historical reasons. 

For example, Ispec names from an LCIF file are allowed to contain hyphens, whereas 

Ispecs created by using LINC Generate are not. 

$ The number of concurrent copies of the CASE Load program that can be run is subject 

to the same limits applicable to all LINC Reports. Currently this means a limit of 150 

concurrent reports for MCP based LINC Generate. 

v 4-3

CASE Load Screen 


Overview 

This subsection consists of the following topics: 

$ Accessing the CASE Load Screen 

$ CASE Load Screen for MCP based LINC Generate 

$ CASE Load Screen for OS 2200 based LINC Generate 

$ CASE Load Screen for LINC based on the UNIX operating system Generate 

Accessing the CASE Load Screen 

Access the CASE Load screen from inside LINC Generate by using the CLD Activity code. 

For example, to load into the current LINC Specification, enter GO CLD in any Action 

field. 

You can access the CASE Load screen directly from the Log In screen by entering the name 

of a LINC Specification, and CLD in the Activity field. If you enter the name of a new LINC 

Specification, that LINC Specification will be loaded in full. If you enter the name of an 

existing LINC Specification, you can choose whether to replace it or to modify it with 

changes from your LCIF file. 

If you wish to load changes to the GLOBAL Specification, you must first log on to it. 

CASE Load Screen for MCP Based LINC Generate 

Fields on the CASE Load Screen for MCP based LINC Generate are described in the 

following subsections. 

Specification name 

LCIF file name 

This field displays the name of the current LINC Specification. It cannot be changed. 

Enter the name of the LCIF file. You can include a username (in parentheses) Usercode 

field. For example, you can enter: 

 

4-4 v

on 

Enter the name of the pack on which the LCIF file is stored. 

Usercode/password 

Enter a usercode and password that provide access to the LCIF file. 

Accesscode/password 


Enter the accesscode and password of the LCIF file in these fields. You must enter a valid 

accesscode for the specified usercode if your host is using the accesscode security feature. 

Delete existing specification 

Partial load 

Patch number 

Enter Y to delete an existing LINC Specification and perform a full load. Enter N to 

perform a full load for a new LINC Specification, or to perform a partial load on an existing 

LINC Specification (you must also enter Y in the Partial load field). 

Enter Y to perform a partial load into an existing LINC Specification. Enter N to perform a 

full load (for an existing LINC Specification you must also enter Y in the Delete existing 

specification field). 

Enter a patch number if patch control is enabled in LINC Generate. Make no entry to use 

an number allocated automatically by LINC Generate. 

Change identifier 

Enter the required change identifier. Your entry is prefixed with CLD and used as the 

change identifier for this run. 

Allow Local Conflict with GLOBAL Dictionary 

Enter N to avoid loading Local Dictionary items that conflict with Global Dictionary items. 

Enter Y to load Local Dictionary items that conflict (have different edit, length, and 

decimals) with Global Dictionary items. Items are loaded with their Allow global 

conflict? field set to Y. Any text and conditions for the data item are also loaded. 

v 4-5


In addition, if you load a Local Dictionary item that exists in the Global Dictionary, the 

setting of the Override LINC Dictionary Item text and conditions field is used, as 

follows: 

$ If set to N, the item is not added. 

$ If set to Y, the item is added to the Local Dictionary as if it was in conflict. 

Issues with this setting 

In a partial load, if a data item of the same name as a conflict item exists in your LINC 

Specification, the conflict item is not loaded. An error message is produced in the load. 

Override LINC Dictionary Item Text and Conditions 

Display activity 

Report to 

Enter Y to replace text and conditions of existing Dictionary items with text and conditions 

in the file. Enter N to leave the text and conditions in the LINC Specification unchanged. 

Text and conditions are: 

$ DATA.DISPLAY 

$ DESCRIPTION 

$ TEXT 

$ SYNONYM 

$ EXTREF 

$ VALUE 

The setting of this field also affects the functioning of the Allow Local Conflict with 

GLOBAL Dictionary field. 

Enter Y to display messages describing the progress of the CASE Load on the Status line. 

Enter N if you do not wish these messages to be displayed. 

Use this field to choose the type of output device to which output from the CASE Load is to 

be directed. Enter one of the values from the following table. 

4-6 v

RP/TP Printer name 

Value Device 

LP Line printer 

VD Video 

TP Terminal printer 

RP Remote printer 


If you entered TP or RP in the Report to field, use this field to enter the name of the 

terminal printer or remote printer to which your output is to be directed. 

Load Change information (only for LDA 2.2 and above) 

Enter Y to load LDA 2.2 patch and change information from the LCIF. Entering N in this 

field will cause all LDA 2.2 patch and change information from the file to be ignored. 

If the Specification in LINC Generate has either change-id or patch-id set, the default value 

for this field is Y, otherwise the default is N. 

Audit with CC info from file (only for LDA 2.2 and above) 

Enter Y to create Audit records using the patch and change information from the LCIF. 

The default value is N. 

Caution 

Audit records are created using the last updated date and time information 

received from the LCIF. This may corrupt the Audit records for a Specification as 

records with an earlier date and time may be added after a later date and time. 

Because of this possibility, when Audit records are created by the CASE Load run, 

the Patch Identification received in the LCIF is flagged as having come from LDA 

(that is, status = L). You cannot change this patch status or logon to patches with 

this status. You cannot extract or apply them, but you can archive, consolidate, or 

purge them. 

CASE Load Screen for OS 2200 Based LINC Generate 

Fields on the CASE Load Screen for OS 2200 based LINC Generate are described in the 

following subsections. 

v 4-7





Enter the name of the LCIF file. 


Partial load 

Patch number 



















follows: 



4-8 v











$ DESCRIPTION 

$ TEXT 

$ SYNONYM 

$ EXTREF 

$ VALUE 













v 4-9


Caution 








purge them. 

CASE Load Screen for LINC Based on the UNIX operating system 


Fields on the CASE Load Screen for LINC based on the UNIX operating system Generate 

are described in the following subsections. 



on LINC PACK 


Enter the name of the LCIF file. 

Enter the name of the LINC Pack on which the LCIF file is stored. 


Partial load 







4-10 v

Patch number 














follows: 











$ DESCRIPTION 

$ TEXT 

$ SYNONYM 

$ EXTREF 

v 4-11


$ VALUE 


Report to 

Printer name 





Use this field to choose the type of output device to which output from the CASE Load is to 

be directed. Enter one of the values from the following table. 

Value Device 

LP Line printer 

EX Extract file 

Enter the name of the line printer or Extract file to which your output is to be directed. 









4-12 v

Caution 









purge them. 

v 4-13

Generating Your LINC System after Loading 

Generating Your LINC System after Loading 

To complete your load process, sign on to your LINC Generate and initiate a syntax only 

generate of your LINC System. This type of generate checks all code, and edits every logic 

line. 

Recovering a Failed CASE Load 

The CASE Load program stores recovery information at regular intervals. In the event of 

an abnormal termination, the load can be restarted, and only the unprocessed records from 

the LCIF file will be processed. 

To restart a load after an abnormal termination: 

1. Access the Supervisor screen in LINC Generate. 

2. Use the RESET CLD command. 

If there are existing parameters for your station and for the current LINC 

Specification, the CASE Load Recovery screen is displayed, showing the various field 

settings. 

3. In the Enter ’YES’ to restart the run or ’NO’ to abort the run field, enter YES to 

unlock your LINC Specification and restart the run. 

Enter NO to unlock your LINC Specification and clear the parameters. This may leave 

your LINC Specification partially updated. 

You can enter a command in the Action field to exit from the screen, leaving the 

locks and parameters in place. 

4-14 v

Running CASE Load in Batch 

Overview 


$ Batch CASE Load for MCP based LINC Systems 

$ Batch CASE Load for OS 2200 Based LINC Systems 


$ Batch CASE Load for LINC Systems based on the UNIX operating system 

$ Creating the Batch Parameter File 

Batch CASE Load for MCP Based LINC Systems 

You can initiate CASE Load in batch mode by using the LINC/RIP (Report Initiation 

Program). LINC Generate must be active. From CANDE, enter: 

 

 

 

The file (usercode)file ON pack is an ACCEPTFILE that contains your batch parameters, as 

described in ‘‘Creating the Batch Parameter File’’. 

You may also run the CASE Load Report as a freestanding Report. 

Batch Security 

Your usercode for a batch CASE Load run is the usercode under which you start the WFL. 

If the initiating WFL for your batch CASE Load is run with a non-privileged usercode, 

security checks will be made to see if it is able to access the files requested in your batch 

parameter file. The usercode is also used for LSM security checking. 

Batch CASE Load for OS 2200 Based LINC Systems 

You can initiate CASE Load in batch from Demand or Batch, using the following ECL 

(where generate is the name of your LINC Generate): 

 

Batch parameters must be contained in a file called generate*ACCEPTFILE, or that is 

specified by an @USE statement that must appear in the runstream before the @XQT 

statement. Use the @ASG statement to assign the parameter file to your runstream. Details 

of the batch parameter file is given in ‘‘Creating the Batch Parameter File’’. 

v 4-15


Batch CASE Load for LINC Systems Based on the UNIX Operating 

System 

To run CASE Load in batch 

1. Sign on with a username that may access LINC Generate. 

2. Create the batch parameter file. Refer to ‘‘Creating the Batch Parameter File’’. 

3. From the shell, enter 

 

Here file is the name of the batch parameter file. 

Creating the Batch Parameter File 

Batch Parameter File Rules 

In the batch parameter file 

$ Each record may contain up to 72 characters. 

$ Enter batch commands in uppercase, in order. 

$ Entries may be in free format, with one command to a record. 

$ Leading spaces are ignored. Commas and parentheses are optional, although all 

parentheses must be preceded and followed by a space. 

$ Multiple batch runs are allowed if they have different BATCHID values. 

If multiple batch CASE Load runs are initiated without unique BATCHID values, 

unexpected results may occur. 

Batch File Parameter Commands 

The commands in the following table are available. 

Parameter Description 

LANGUAGE = language Optional. If omitted, ENGLISH is used. 

BATCHID = identifier Optional. Specifies a batch identifier. If omitted, BATCH is used. 

NODISPLAY Optional. Indicates that progress messages should not be displayed. 

USERCODE = identifier Optional. Required for OS 2200 LINC Specifications with LSM security 

enforced. 

CCPATCH = number Optional. Specifies a patch identifier. Only valid if your LINC 

Specification patch identification enabled 

continued 

4-16 v

continued 

Parameter Description 


CCID = identifier Optional. Specifies a change identifier. Only valid if your LINC 

Specification has change identification enabled. 

device-type [=printer ] Indicates the output device. Optionally names printer printer. 

SPECIFICATION = 

specification 

Required. Names the LINC Specification to be loaded. SPEC is a valid 

abbreviation for SPECIFICATION. 

DELETE Optional. Indicates that the existing LINC Specification should be 

deleted. Required for an existing LINC Specifications if PARTIAL is not 

included. 

PARTIAL Optional. Indicates a partial load. If omitted, the load is a full load. 

CONFLICT Optional. If omitted, no conflicts are permitted. 

OVERRIDE Optional. Indicates that Dictionary text and conditions are to be 

overridden. If omitted, Dictionary text and conditions are not 

overridden. 

FILE Required. Specifies the location of the LCIF file file. 

CCLOAD Optional. Specifies that LDA 2.2 patch and change information are to 

be included in the load. If omitted, LDA 2.2 patch and change 

information will be ignored. 

CCAUDIT Optional. Specifies that Audit records are to be created during the 

CASE Load run, using the LDA 2.2. patch and change information. If 

omitted, Audit records will not be created unless auditing is set for the 

Specification, and then the Audit records will be created using the 

CASE Load run identifiers. 

device-type 

Be aware that Audit records are created using the last updated date 

and time information received from the LCIF. This may corrupt the 

Audit records for a Specification as records with an earlier date and 

time may be added after a later date and time. 

For MCP based LINC Generate, valid values of device are TP (Terminal printer), RP (MCP 

based Reprints remote printer), and LP. ForTP and RP you must supply a printer name 

printer. 

For LINC based on the UNIX operating system Generate, valid values of device are LP and 

EX.ForEX you must supply a file name printer. 

This parameter is not valid for OS 2200 based LINC Generate. 

v 4-17


FILE 

The form of the file name depends on your host type: 

$ For MCP based LINC Generate: 

 

$ For OS 2200 based LINC Generate, the following variants are for a file on fixed disk, 

removable disk, and a LINC pack lpack, respectively. 

 

 

 

$ For LINC based on the UNIX operating system Generate, the following variants are for 

a file on disk and on a LINC pack lpack, respectively: 

 

 

4-18 v

Description of the Load Process 

Overview 


This subsection contains descriptions of the processes involved when a LINC Specification 

is loaded into LINC Generate. 

$ Process for a Full Load 

$ Process for a Partial Load 

$ Effect of Granularity Flags in Partial Loads 

$ How Conflicts are Resolved in Partial Loads 

$ How Dictionary Items are Loaded 

$ Extract and Load Rules for LCIF Files 

Process for a Full Load 

You can choose to load a full LINC Specification over an existing LINC Specification by 

entering Y in the Delete existing specification field on the CASE Load screen). In this 

case, the existing LINC Specification is deleted and the LINC Specification from the LCIF 

file is loaded. 

If there is no existing LINC Specification, then a full load is performed. 

Process for a Partial Load 

Description of the process 

When you load an extracted LCIF file from LDA into an existing LINC Specification in 

LINC Generate, the following process occurs: 

1. Structures with names not present in the LINC Specification are added. 

v 4-19


2. Structures with names present in the LINC Specification are assessed. If they are of 

similar general type (Ispec, Report, Global Logic or Profile), then: 

$ If their specific details are compatible, the existing structure is updated with 

details from the LCIF file, according to the granularity flags in the file. See ‘‘Effect 

of Granularity Flags in Partial Loads’’. 

$ If their specific details are different, the existing structure is deleted, and the 

structure from the LCIF file is added. For example, if you are changing a 

Standard Component to an Event, the Standard Component is deleted and the 

Event is added. 

If the structures are of different general type, the existing structure is not deleted, 

but is left unchanged. When the new structure from the LCIF file is loaded, it is 

possible that this load will fail (as there is an existing structure of the same name). 

For example, if your LINC Specification has an Ispec TEST1, and your LCIF file has a 

Profile TEST1, the Ispec will not be deleted. The load of the Profile TEST1 from the 

LCIF file will fail, as a new Profile may not have the same name as an existing Ispec. 

3. Changes are made to individual Global Setup Data items. 

It is possible that Global Setup Data items will be truncated in the load process. This 

is because the definition of these items in LINC Generate is limited by line length. 

Truncation may involve the initial value or the comment associated with an item. Any 

truncation will be reported. 

4. Changes are made to the Data Dictionary for your LINC Specification by using 

Dictionary Maintenance (DMA). For details, see ‘‘How Dictionary Items Are Loaded’’. 

Problems with the Event Structure 

If you replace an existing LINC Specification using the CASE Load facility for OS 2200 

based LINC Generate, you may encounter problems with the Event structure. This is 

because the old LINC Specification in LINC Generate is deleted, and the new LINC 

Specification loaded. This will cause the EVENT generate counter to be reset, and which in 

turn can cause timestamp mismatches with generated Reports, which will not run 

successfully. 

How Logic is Loaded 

$ Global Setup Data item and Business Rule text for each item is merged in the LINC 

Global Setup Data (GSD) section. 

$ Local Setup Data items are placed at the beginning of Pre-Screen logic, Global Logic, 

or Report Main logic. Any Business Rules (description text) for a Setup Data item are 

inserted after that Setup Data item. 

It is possible that Setup Data items will be truncated in the load process. This is 

because the definition of these items in LINC Generate is limited by line length. 

Truncation may involve the initial value or the comment associated with an item. Any 

truncation will be reported. 

$ Edit logic is inserted (between BEGIN.EDIT; and END.EDIT; commands) at the 

beginning of Main logic. 

Logic lines are unedited when loaded from your extracted LCIF file into LINC Generate. All 

logic lines are marked for reedit. Logic lines are resequenced when loaded. 

4-20 v

How Screen Layouts are Loaded 


Each data item in the LCIF file is painted at the position specified in the LCIF file. The 

attributes SAME.AS, NO.LOOKUP, and LINK; IF.PRESENT are applied at the end of the 

load process. 

If you paint on line 24 in LDA Development and later extract the full or partial Business 

Segment for loading into an OS 2200 based LINC Generate, the OS 2200 CASE Load 

program drops line 24 and issues an error message. 

The new CASELOAD report reduces the impact of replacing an Ispec by not deleting the 

Ispec. It removes any data items in the Ispec that are not in the LCIF file, then changes any 

remaining I-O data items to the usage output. 

All displays and usage input or inquiry data items are then removed from the screen. 

CASELOAD completely clears the screen to avoid the need to handle difficult merging 

situations such as multiple items rotating positions. The screen is then repainted and any 

I-O items are moved back to the screen. In some cases errors may occur that inhibit data 

items being manually painted properly, these errors will be reported in the CASEID error 

listing. In the case of errors with existing I-O data items, these will be left as usage output. 

This provides a consistent approach as the item’s old position may now be occupied by 

another item. 

Reserved Word Checking is Performed 

The LINC System checks reserved words against a combination of host lists, which are 

defined in the LINC System itself. 

See Appendix A for further information on reserved words, and your LINC Generate 

Operations Guide for details of host list maintenance. 

Effect of Granularity Flags in Partial Loads 

What are Granularity Flags 

Granularity flags are part of the LCIF. They indicate which parts of your Business Segment 

have been extracted from LDA Development. 

For a partial extract file, the CASE Load process expects that the granularity flags will be 

used. If records exist in the LCIF file for an area that does not have its granularity flag set 

in the structure header record, they are ignored. 

Load process 

The partial CASE Load process selectively deletes all or part of each Ispec, Global Logic, 

Profile, or Report, depending on the granularity flags in your LCIF file header records. 

Each structure has its own header record. 

For the LINC Specification, if the Specification text flag is set in the LCIF file 00 record, 

the CASE Load process deletes the text. 

v 4-21


If the Other Specification data flag is set, your CASE Load process deletes LINC 

Subsystems (for MCP based LINC Systems), Report Generate Groups, and the Logical 

Databases. It merges all of the other record types. 

If the Specification options flag is set, your CASE Load process loads these options from 

the LCIF file. If the Whole structure (Ispec, Report, Global Logic, or Profile) granularity 

flag is set in the structure header record for any of these types of structures, the CASE 

Load process updates the whole structure. 

A Report Frame is deleted only if the Whole structure flag for the Frame is set. 

After CASE Load has set up your host LINC structure locks, it then deletes all Ispecs, 

Reports, Global Logics, Profiles, or parts of these structures (if you have selected partial 

structures) at the start of the load process. This is done after the primary edit has finished, 

and before any loading has begun. If you extract every structure affected by a change, 

CASE Load should thus be able to load it all in. 

The CASE Load process deletes Teach screens from your LINC Specification if the Teach 

screen granularity flag is set, and then adds all Teach screens from the LCIF file. All Teach 

screens are deleted, even if the Teach screens in the LCIF file have different names. 

How Conflicts are Resolved in Partial Loads 

The following table shows the actions taken when resolving a partial load into your LINC 

Generate. 

Condition Action 

Duplicate Business 

Segment 

Duplicate Functional Area Not applicable. 

Duplicate Activity Not applicable. 

Duplicate Global 

Dictionary item 

If the Delete Specification field is set to Y, existing LINC 

Specification is deleted and the incoming Business Segment is 

created. If Delete Specification field is set to N, theloadmust 

be a partial load, and the Partial Load field must be set to Y. 

Rejected and reported in favor of Local or Global dictionary if 

there is a conflict; otherwise loaded. 

Duplicate Global Logic Update existing Global Logic with incoming Global Logic. 

Duplicate Ispec Update existing Ispec with incoming Ispec. 

Duplicate local Dictionary 

item 

Rejected and reported in favor of Local or Global Dictionary if a 

conflict; otherwise loaded. 

Duplicate Report Update existing Report with incoming Report. 

Duplicate Profile Update existing Profile with incoming Profile. 

Duplicate Wildcard Not applicable. 

continued 

4-22 v

continued 

Condition Action 


Changed Global option Replace existing Global option with incoming Global option (if 

Specification Options granularity flag is set). 

Changed Ispec / Report 

/ Profile options 

Changed Local Dictionary 

item 

How Dictionary Items Are Loaded 

Replace existing Ispec, Report, or Profile option with incoming 

option (if Whole Structure option granularity flag is set). 

Rejected and reported in favor of Local or Global Dictionary if 

there is a conflict; otherwise loaded. 

This subsection describes how Dictionary items are loaded into LINC Generate. 

Key to the Tables 

The following table describes the headings and values for the tables in the following 

subsections: ‘‘Dictionary Item Handling in a Full Load’’ and ‘‘Dictionary Item Handling in a 

Partial Load’’. 

Heading Description 

Status GDI indicates a Global Dictionary item. No Refs indicates not 

referenced. DCT indicates a Local Dictionary item. None 

indicates the items is not in either Local or Global Dictionary, 

but is used in the LINC Specification. 

Conflict Setting of the LDA conflict option. 

Override Setting of the LDA override option. 

Attributes The values Same, Diff. (different), and N/A (not applicable) refer 

to the attributes (length, edit, and decimals). 

Local Dict. S indicates a sibling Local Dictionary item is created. C 

indicates a Local Dictionary item with conflict allowed is 

created. L indicates a Local Dictionary item is created. Error 

indicatesanerrorisreturned. 

TX/VL The entry indicates the source of Text and Value logic: LINC 

(exists in LINC Generate), or LCIF (from the LCIF file). 

Painter Error indicates that an error will result in the LINC Painter. OK 

indicates the item is accepted. 

Note Refer to the Notes following each table. 

v 4-23


Dictionary Item Handling in a Full Load 

The following table shows the results of various attempts to add a data item to the Local 

Dictionary in host LINC during a CASE Load of a full LINC Specification transferred from 

LDA. 

For a description of the headings and values, refer to ‘‘Key to the Tables’’. 

Status Conflict 

Override Attributes 

Local 

Dict. 

TX/VL Painter Note 

GDI No N/A Same S LINC OK 1 

GDI No N/A Diff. Error Error Error 2 

GDI Yes No Same S LINC OK 1 

GDI Yes Y/N Diff. C LCIF OK 3 

GDI Yes Yes N/A C LCIF OK 3 

No Refs. N/A N/A N/A L LCIF OK 4 

Notes 

1. The data item already exists in the LINC Global Dictionary with the same attributes. 

A sibling (S) Local Dictionary record will be created the first time this is painted. No 

errors are logged. 

2. The following error is logged when this data item is checked against the LINC Global 

Dictionary. 

 

An error is logged when an attempt is made to paint this data item, as the Length, Edit 

and Decimal attributes input to Painter will differ from the LINC Global Dictionary 

attributes. 

3. The data item is added to the Local Dictionary, with the Conflict allowed field set to 

Y. The data item is painted with the attributes from LDA, and it will inherit the 

LDA-defined text and conditions. No errors are logged. 

This data item can be modified for the LINC Specification only by using Local 

Dictionary Maintenance (DMA). A Global DMA performed on a Global Dictionary 

data item of the same name would not be propagated to this data item. 

4. As there is no entry in the Global Dictionary, a new entry is made in the Local 

Dictionary. This data item may be modified on your host platform by using DMA. No 

errors are logged. 

Dictionary Item Handling in a Partial Load 

4-24 v


The following table shows the results of various attempts to add a data item to the Local 

Dictionary in host LINC during a CASE Load of a partial LINC Specification transferred 

from LDA. 

The same results apply where there are further existing references to the data item in the 

LINC Specification, beyond those in structures which are also included in the LCIF file. 

Where there is no other such reference, the results are those of a full load. 

For a description of the headings and values, refer to ‘‘Key to the Tables’’. 

Status Conflict 

Override Attributes 

Local 

Dict. 

TX/VL Painter Note 

GDI Yes No Diff. Error LINC Error 1 

GDI Yes Yes Same Error Error OK 2 

GDI Yes Yes Diff. Error Error Error 1 

DCT N/A No Same S LINC OK 

DCT N/A Yes Same S LCIF OK 

N/A N/A N/A Diff. L LINC OK 3 

None N/A N/A Same L LCIF OK 

None N/A N/A Diff. L LINC OK 3 

Notes 

1. An error is logged stating that an invoked Global Dictionary data item cannot be 

loaded as a Local Dictionary item with the Allow conflict field set to Y. 

The data item is rejected when painting, because of the mismatched attributes. 

2. An error is logged stating that an invoked Global Dictionary data item cannot be 

changed to a Local Dictionary data item with its Allow conflict field set to Y. 

The data item is painted successfully because the attributes match (this may not give 

the desired result, as defined in your LDA Business Model). 

3. A Dictionary item is loaded and the Dictionary Maintenance (DMA) process is used to 

update the LINC Specification with the change. 

Extract and Load Rules for LCIF Files 

There are several rules that control the extract and load of structures and parts of 

structures in LINC Generate. These rules are as follows. 

$ If a whole structure (Ispec, Report, Global Logic, Profile, or Frame) is extracted, and 

there is an existing structure with the same name during the load, then the existing 

structure is deleted or merged and the extracted structure replaces it. 

v 4-25


If only parts of a structure are extracted, and an existing structure with the same name 

is detected during the load, then only the parts of the structure that were extracted 

replace any existing ones. For Reports, this means that if a whole Report is extracted, 

then all existing Frames are deleted or merged, and all extracted Frames are added. 

If parts of a Report are extracted, then any existing Frames with the same Frame 

numbers as extracted ones are deleted or merged, and are replaced by the extracted 

ones. Any other existing Frames remain, and any other extracted Frames are added. 

If either a whole structure or parts of a structure are extracted, and during the load 

there is not an existing structure with the same name, then all of the extracted 

information is used to create a new structure. 

$ Structure options, environmental options, DMS options, and trace items for Ispecs, 

Reports, Global Logics, and Profiles are always extracted when any part of the 

structure is extracted. They are loaded if the whole structure is loaded or if there is no 

existing structure with the same name. 

Frame descriptions are always extracted when any part of the Frame is extracted. 

They are loaded only if the whole Frame is loaded or there is no existing Frame. 

$ The load process overwrites some items and merges others. 

Generally, if an item is regarded as a whole entity, it is overwritten; otherwise it is 

merged. For example, LINC Specification text or Subsystem information is 

overwritten, but Keywords, Report Generate Groups, and Local Dictionary items are 

merged. 

$ Setup Data items are extracted for: 

v Ispecs, if Pre-Screen logic is extracted 

v Reports, if the logic for Frame 00 is extracted 

v Global Logics, if logic is extracted 

They are loaded under the same circumstances. 

Because Setup Data items are extracted only in specific situations (for example, 

Pre-Screen logic in Ispecs and Frame 00 in Reports), you may get unexpected results 

from the CASE Extract process, depending upon what is extracted. 

For example, if you extract a full Ispec from host LINC, and that Ispec has Setup Data 

items declared in Pre-LINC logic; then you load it into LDA; then extract Pre-Screen 

logic only from LDA to load it back to host LINC, you will get errors when you 

generate on the host, as the Setup Data items will then be defined in both Pre-Screen 

logic and in Pre-LINC logic. 

$ Edit logic is extracted for Ispecs if Main logic is extracted. It is loaded under the same 

circumstances. 

$ In LDA Development, Frames can have Business Rules associated with them. These 

are extracted if the Frame logic is extracted. These are loaded into LINC Generate as 

comments at the start of the Frame logic. 

$ For the extraction of changed structures, all Global Setup Data items are extracted if 

any have changed. 

$ The extract painted layout part is ignored for Performable Global Logics. 

4-26 v


$ The following records are extracted if you enter Y in the Other Spec Data field when 

you extract an LCIF file in LINC Generate: 

v Environmental Option 

v DMS Option 

v Pack Allocation 

v Report Generate Group 

v Logical Database 

v Subsystem 

v Keyword 

v Generate Set information 

When these records are loaded, the Environmental Option, DMS Option, Pack 

Allocation, and Subsystem information replaces any existing information. The other 

information is merged with any existing information of the same type. 

$ For the extraction of changed items, information about structures which have been 

deleted cannot be extracted. 

Note: This means that a series of extracts of changed items cannot be 

guaranteed to keep two systems in step. 

$ When selecting Dictionary items that are used in the structures being extracted 

v Dictionary items used in a screen layout are extracted if the screen is extracted. 

v Dictionary items used in the definition of screen data items (by using the 

SAME.AS; command) are extracted if the screen is extracted. 

v Dictionary items used in the definition of Setup Data items (by using the SAME.AS; 

command) are extracted if the Setup Data items for that structure are extracted. 

v Dictionary items used in the definition of Global Setup Data items (by using the 

SAME.AS; command) are extracted if Global Setup Data items are extracted. 

v 4-27

Section 5 

Unloading a LINC Specification from 

LINC Generate for LDA 

You use the CASE Data Extract Request (CEX) screen in LINC Generate to extract full or 

partial details of the current LINC Specification from LINC Generate into an LCIF file, 

called the LCIF file. This file can be transferred to a PC for loading into LDA. 

This section contains details of this screen and issues relating to the LCIF file. 

$ ‘‘Using the CASE Data Extract Request Screen ’’ 

$ ‘‘Completing a Partial Extract ’’ 

$ ‘‘Important Issues with the LCIF File ’’ 

To load a LINC Specification extracted from LDA, you use the CASE Load facility. For 

details, see Section 4. 

Using the CASE Data Extract Request Screen 

You use the CASE Data Extract Request (CEX) screen to extract details of a LINC 

Specification from LINC Generate into a file for development in LDA Development. 

To extract details of several LINC Specifications, you must sign on and extract each LINC 

Specification using this screen. 

Before Extracting Your LINC Specification 

It is important that you generate your LINC System before extracting a LINC Specification. 

A generate of your LINC System reduces the possibility of unexpected errors in logic (such 

as invalid relationships) when the LCIF file is loaded into LDA Development. 

There is no need to generate DMS/COBOL prior to extracting MCP based or OS 2200 based 

LINC Systems for transfer to LDA. 

Accessing the Screen 

To access the CASE Data Extract screen in LINC Generate, perform one of the following 

actions: 

$ Enter CEX in the Choice field on the Utilities menu. 

v 5-1


$ Enter GO CEX in the Action field on any screen. 

The CASE Data Extract Request screen is then displayed. Use this screen to extract details 

of the LINC Specification into an LCIF file for transfer to your PC-based LDA Repository, 

as described in the following subsections. 

The fields on the CASE Data Extract Request screen are described in the following 

subsections. 

What happens next 

When you transmit the CASE Data Extract Request screen and you have not requested a 

partial extract, the extract process is started. When the extract has completed, an 

appropriate message is displayed in the Status Line. 

Fields on the CASE Data Extract Request Screen 

Action 

Choice 

Fields on the CASE Data Extract Request screen are described in the following 

subsections. 

Enter a GO command to move to another part of LINC Generate. Enter HE to access help 

information for the screen. Enter BYE to sign off from LINC. 

If you make an entry in this field, entries in all other fields are ignored. 

Use this field to specify the type of extract required. Enter one of the values shown in the 

following table. 

Value Type of Extract 

LDA313 LDA Release 1.3 



CCINFO Extract all patch and change 

identification information 

GLOB Global Dictionary extract only 

The CCINFO option is available only for a GLOBAL Specification and only if LDA 2.2 is set 

as the extract level for your LINC system. 

5-2 v

Partial spec 


Use this field to choose whether or not to extract selected parts of a LINC Specification. 

Enter N to extract a complete LINC Specification. You must enter N if you are extracting 

the Global Dictionary. 

Enter Y to extract selected parts of the current LINC Specification. You will be presented 

with screens that enable you to make your selections. For more details, see ‘‘Completing a 

Partial Extract ’’. 

Output file name 

On LINC pack 

or on Pack ids 

Equipment type 

ACR 

Use this field to specify the name of the LCIF file. For MCP and OS 2200 based hosts, a 

suggested standard file name (that includes the current LINC Specification name) is 

initially displayed as a default. For example, the initial value in this field for MCP based 

hosts is: 

 

There is no default value in this field for LINC Systems based on the UNIX operating 

system. 

Enter the LINC pack name if you are using the LINC pack facility. This field is valid only 

for OS 2200 based LINC Systems. 

Enter up to six pack ids in this field (unless you entered a pack in the On LINC pack 

field). This field is valid only for OS 2200 based LINC Systems. 

Enter the equipment type of your disk (unless you entered a pack in the On LINC pack 


Enter an optional ACR code in this field (unless you entered a pack in the On LINC pack 


Reset previous run 

v 5-3


If the previous extract failed, the parameters associated with the previous request must be 

cleared before a new extraction may be made. Enter Y in this field to reset the request. The 

default is N. 

5-4 v

Completing a Partial Extract 


When you enter Y in the Partial Spec field on the CASE Data Extract Request screen, the 

Partial CASE Extract screen is displayed. 

For more details about partial loads, refer to your LINC Development Installation and 

Administration Guide. 

Partial CASE Extract Screen 

Use the Partial CASE Extract screen to select parts of your LINC Specification for 

inclusion in the LCIF file. 

Selecting All or Parts of Selected Structures 

Enter Y in the All or Selected field against each of the structure types. 

For each structure type you can choose to include all of the structure (enter Y in the ALL 

field), or you can select the required parts of your structure by entering Y in the fields 

outlined in the following table. 

Field Description 

TX Text 

PA Screen or Frame layout 

PS Pre-Screen logic 

PL Pre-LINC logic 

LG Main logic 

TE Teach screens 

If you enter Y in the Selected field, additional screens are displayed, as outlined in ‘‘Using 

the Partial CASE Extract Screens for Structures ’’. 

Selecting Structures Changed From a Specific Date 

Enter the date and time in the All changed structures since field to extract all Ispecs, 

Reports, Profiles, and Global Logics that have been modified or added, on or after your 

specified date. Any Global Setup Data items that have been changed since the specified 

date are extracted in their entirety. 

Selecting Structures Changed Since the Last Generate 

v 5-5


Enter Y in the All items needing generate field to extract all Ispecs, Reports, Profiles, 

and Global Logics that are marked as needing generate. Any Global Setup Data items that 

are marked for generation are extracted in their entirety. 

Note: As you should not extract structures marked as NEEDEDIT, perform a 

syntax-only generate before entering Y in the All items needing generate 

field. 

Selecting Dictionary Items 

Enter Y in the Extract local dict items used in extracted items field to extract all 

Local Dictionary items used in the selected structures (as well as other items). For details 

of rules applying to this field, see ‘‘Restrictions on CASE Load’’. 

Using the Partial CASE Extract Screens for Structures 

The display of the following screens is determined by your entries in the Selected field on 

the Partial CASE Extract screen. 

$ Partial CASE Extract - Ispecs 

$ Partial CASE Extract - Global Logics 

$ Partial CASE Extract - Profiles 

$ Partial CASE Extract - Reports 

On the Partial CASE Extract - Reports screen, you can enter Y in the FRMS field. The 

Partial CASE Extract - Report Frames is then displayed, enabling you to select individual 

Frames. 

Completing the Screens 

When you are using the Partial CASE Extract screens for the various types of structures 

$ If you enter Y in the Or start CASE extract field, this always overrides any further 

navigation, and the CASE Extract program is started immediately. 

This field is prefilled with a Y value when it is possible to determine that all selections 

have been made. You can override this setting and navigate to make further selections, 

if required. 

$ Full backwards and forwards navigation between your selected structure types is 

permitted. You can switch between structure types, as well as switching to a specified 

start point. 

$ Literal values displayed next to the Type field indicate what is permitted. For 

example, when you have selected Reports, FRM (Frame) is also valid. This enables 

you to select the Report Frames to be extracted for your Reports. 

$ Navigation fields are prefilled with the next choice for that structure type or the 

succeeding structure type, if applicable. 

5-6 v

Important Issues with the LCIF File 

Overview 

This subsection contains the following topics: 

$ Compatibility of LDA and LINC Generate 

$ Relationships in the LCIF File 

$ Checking the LCIF File 

$ Transferring the LCIF file to LDA 

Compatibility of LDA and LINC Generate 


Releases of LDA and LINC Generate are not always perfectly aligned. Refer to the release 

literature for LDA for features introduced in a new release of LINC. 

For example, the LCIF file accepts EDIT; W (Hankaku-Katakana) data items. While these 

data items will be extracted successfully from LINC Generate, you may be unable to load 

them into LDA. 

Relationships in the LCIF File 

Relationships are not validated until your LCIF file is loaded into LDA. 

Checking the LCIF File 

When you extract a LINC Specification, the Report initiated by the CASE Extract process 

(LEX), produces a listing which details all Setup Data items and Global Setup Data items 

that are marked for reedit. It is important that you check this, and confirm the accuracy of 

the extraction. 

See also ‘‘LINC Syntax Conversion ’’, for details of conversion of your LINC Specification 

for loading into LDA. 

Reducing the Size of Extract Files from Host LINC 

Model files that originate in host LINC (extracted from your LINC System for transfer to 

LDA) have 300-byte fixed-length records. MODELTRIM is an add-on host utility that trims 

trailing spaces from records and reduces them to about 25 percent of their original size. 

v 5-7


Restrictions 

You must not reload trimmed model files into your host LINC System using CASE Load 

(CLD). 

Model Files Originating on Your Workstation 

Model files extracted from LDA are already trimmed. 

When you transfer a model from your workstation to an MCP or OS 2200 based host, 

fixed-length records are written. 

Model Files Originating in Host LINC 

When you transfer a model file from an MCP based host to your workstation, the FTP 

utility trims trailing blanks, adds end-of-line delimiters and converts from EBCDIC to 

ASCII, so it is not necessary to use MODELTRIM. However, MODELTRIM is available, and 

will compact 300-byte model file records into fixed-length physical records containing one 

or more logical records, each separated by a carriage return / line feed pair. 

Use the MODELTRIM program on OS 2200 based hosts to remove trailing spaces to 

produce true variable length records. 

Use MODELTRIM on UNIX hosts to remove trailing spaces and produce a standard UNIX 

stream file of true variable-length records. The trimmed file is terminated with a new line 

character. 

Run MODELTRIM prior to using FTP to transfer the file to your workstation. All existing 

LINC CASE Load or Extract file formats remain unchanged. 

MODELTRIM creates a trimmed model file, with the characteristics shown in the following 

table. 

Using the MODELTRIM Program 

MCP based OS 2200 

based 

UNIX 

Record Size (bytes) 1080 Variable length Variable length 

Records per Block 10 N/A N/A 

EXTMODE EBCDIC ASCII ASCII 

FILEKIND DATA DATA Stream 

When you use MODELTRIM, no default model file name applies if you do not supply a 

model-filename value in the command line. 

5-8 v

MCP Based Hosts 


It is not necessary to use MODELTRIM on MCP based model files, as the FTP utility 

provides sufficient compression. 

If you wish to use MODELTRIM, enter the following command from CANDE: 

 

 

If you specify a destination-model-filename value, the model-filename file is unaltered, 

and a new destination-model-filename file is created. 

If you do not specify a destination-model-filename value, the model-filename file is 

overwritten. 

OS 2200 Based Hosts 

Enter the following command: 

 

Use ACCEPTS to enter the destination model file name and the model file name values. 

You must enter both file names. 

UNIX Hosts 

Enter the following command: 

 

If you specify the -s option, no error messages will be produced. If you specify the -c 

option, lines will be terminated with a carriage return as well as a new line character. 

If you specify a destination-model-filename value, the model-filename file is unaltered, 

and a new destination-model-filename file is created. 

If you do not specify a destination-model-filename value, the model-filename file is 

overwritten. 

Transferring the LCIF File to LDA 

When transferring an LCIF file to LDA 

$ Host LINC files that have been extracted for transfer to LDA are held in fixed sized 

records of 300 bytes for each record. As the informational content of many of the 

record types takes up much less than the full 300 bytes, the remaining bytes are 

padded with spaces. 

$ You can use any file transfer utility that transfers a file with non-standard text 

characters (that is, values less than ASCII 20) from your host to your PC. For more 

information on suitable packages, contact your Unisys representative. 

v 5-9


$ When an LCIF file is transferred from an MCP based host using FXHost, the resultant 

LCIF file on the PC contains variable-length records with no trailing spaces. The 

SAMPLE LCIF file size is 254,881 bytes. 

$ When an LCIF file is transferred from a UNIX host using FTP (TCP/IP), the resultant 

LCIF file on the PC contains 300 byte records including the trailing spaces plus a 

carriage return / linefeed pair. The SAMPLE LCIF file size is 1,031,330 bytes. 

LINC Syntax Conversion 

A CASE Extract run produces a printed list of any LINC syntax conversions performed. 

You can use this output to see what changes have been made. The types of syntax 

conversions are described in the following subsections. 

Global Setup Data Items 

Profiles 

The following conversions are performed when the LCIF file is produced: 

$ Any lines containing only comments are assumed to be associated with the next 

Global Setup Data item defined. These comment lines are written into the LCIF file as 

Business Rules associated with the Global Setup Data item. Any comment lines after 

the last Global Setup Data item defined are included in the Business Rules of the last 

Global Setup Data item. 

$ Global Setup Data item definitions are used by LDA Development to create the Global 

Setup Data item dictionary containing the necessary attributes. 

$ The LDA Development load process places any comments that were included on the 

end of the line defining a Global Setup Data item into the Description field for that 

Global Setup Data item, up to a maximum of 30 characters. 


$ Profiles have attributes describing the Ispecs and data items involved. Profile 

conditions are stored in tabular form. The CASE Extract program handles the 

conversion of this logic into the required tabular format. 

$ Lines containing comments only, and comments on the end of any Profile logic 

command, are added to the Profile text area as additional Business Rules. 

$ Profile DATA commands are transferred and loaded into a table within LDA 

Development. However, LDA Development ignores this information. The table is used 

only during the LDA Development extract process to restore these commands into the 

Profile logic. The Profile DATA commands are directly extracted with the rest of the 

Profile logic. 

5-10 v

Keywords 


The concept of Keywords is not supported in LDA, but the information relating to 

Keywords is transferred to LDA Development and transferred back to your host by means 

of the LCIF file. Keyword information is not maintained within LDA Development. 


$ CASE Extract indicates Ispecs using Keywords by adding an additional flag to the data 

item relationship record. This is a one-byte field containing Y if it is a Keyword, 

otherwise N or a space. 

$ In LDA Development, the Load utility loads this information, along with the Keyword 

table, which is extracted from the host on a full extract. 

$ In LDA Development, the Extract utility extracts this information, along with the 

Keyword table, which is extracted from LDA Development only for a full extract or the 

selection of the Business Segment Other Information check box. 

$ Any data item that has the Keyword attribute set can not be modified in LDA 

Development. 

However, Keywords can be repositioned in LDA Painter. They can also be deleted, in 

which case the corresponding entry in the Keyword table is deleted if its usage count is 

equal to zero. 

$ All names in the Keyword table are treated as reserved words, and no structure can be 

created with a name that already exists in this table. This is restricted to the LDA 

Development Business Segment where this Keyword is defined, and to the Global 

Dictionary. 

$ The host CLD program attempts to load data items that have the Keyword flag set. 

If there is a conflict with the host LINC Specification, the incoming data item is 

rejected, and an error is logged. 

Screen Layouts and Data Items 

Data arrays defined by using the START.ARRAY Painter command are not supported in 

LDA Development, and are converted by CASE Extract to a single occurrence data item 

that has no association with the array indexes. 

Setup Data Items 

LDA Development has a separate window dialog box for you to define any Setup Data 

items. 


$ Remove all Setup Data item definitions from logic, creating a separate Setup Data item 

description. 

v 5-11


Logic 

$ If no initial value is assigned to the Setup Data item, insert a command at the place 

where the data item was originally defined in the logic, to move GLB.SPACES (if 

alphanumeric) or GLB.ZEROS (if numeric) to the Setup Data item. 

$ To ensure there is no change in the behavior of logic or in the initialization of these 

items (except for the initialization of Setup Data items in Global Logics), the 

initialization of Setup Data items is included in a condition in the following 

circumstances: 

Error 

v For Copy.From Ispecs, after the following command: 

 

v For Insertable Global Logics, after the following command: 

 

If you have coded a Setup Data item to check for SAME.AS; (SAS) a Setup Data Group 

name in your LINC host, then when loading the extracted LCIF file into LDA Development, 

the SAS will be rejected and an error written to the .ERR file. The Setup Data item itself 

will have the EDIT, LENGTH, and DECIMAL attributes that were extracted from your 

LINC host. 


$ The form of the ACCEPT; command that defines a Setup Data item to hold the input 

value is changed to the alternative form and a new Setup Data item is created. 

$ All logic between BEGIN.EDIT; and END.EDIT; commands is separated out from Main 

logic by CASE Extract, and placed in a new logic section. The BEGIN.EDIT; and 

END.EDIT; commands are also removed. 

$ COMPUTE.FROM; commands are converted to COMPUTE; commands. 

$ All occurrences of the GLB.STATUS; command (as opposed to the System Data item 

GLB.STATUS) are changed by CASE Extract to use the abbreviation GS;.Thisis 

necessary because the LDA Development parser is context-independent, and cannot 

distinguish between the data item and the command. 

$ All occurrences of System Data items without a prefix of GLB. are given this prefix. 

For example, TODAY is replaced by GLB.TODAY. 

$ Equals signs (=) used as command delimiters instead of semicolons (;) are replaced by 

semicolons. 

$ All occurrences of an asterisk (*) to indicate a comment line are replaced by a colon. 

5-12 v

Appendix A 

Reserved Words 

When you are creating a LINC Specification, you may find that some words cannot be used 

(or can only be used in certain ways). These are reserved words. 

The appendix consists of the following subsections: 

$ ‘‘Reserved Words Used by Software ’’ 

$ ‘‘Reserved Words Created with Your LINC Specification ’’ 

$ ‘‘Checking Reserved Words’’ 

v A-1

Reserved Words Used by Software 

Reserved Words Used by Software 

Some words have a special meaning to LINC or COBOL. For example, if you try to create a 

Report called ACCEPT, you are informed that ACCEPT is a reserved word. 

LDA 2.3 provides a Reserved Words List utility for checking the reserved words on each 

target host type. See ‘‘Checking Reserved Words’’ for information about this utility and how 

to use it. 

LDA 

When loading an extracted LINC Specification into LDA Development, you should make 

sure that reserved word checking is turned on in both your LINC Generate and LDA 

Development. Any reserved word conflicts found during loading will give a warning. 

When you transfer a LINC Specification from LDA Development to LINC Generate, the 

CASE Load program performs reserved word checking against the host lists defined on the 

LINC host. Reserved word conflicts will cause errors and the problem Ispecs or Reports 

will not be loaded. 


The list of reserved words is different for each host type. You must enable reserved word 

checking for all appropriate hosts when you are developing LINC Systems. Be sure to 

check reserved words before you transfer your LINC Specification to another host type, as 

there is no reserved word checking with LCOPY. 

It is possible that reserved words have been added to a LINC Specification without being 

detected (for example, using LCOPY). You can use the Supervisor HOSTMAINT command 

in LINC Generate to change the host reserved word checking. The HOSTMAINT command 

can also be used to check for reserved words in your LINC Specification. See your LINC 

Generate Operations Guide for details of the HOSTMAINT command. 

Some uses of reserved words are not detected in some cases. When you change your host 

list (using the Supervisor HOSTLIST command), you should ensure that you refer to the 

output of the SLD Report to establish any conflicts. 

A-2 v

Reserved Words Created with Your LINC Specification 

Reserved Words Created with Your LINC 

Specification 

Many parts of your LINC Specification require unique names, which effectively become 

reserved words when those parts are created, as in the following examples: 

$ Ordinates 

Creating a data item with the name of an Ordinate means that an automatic look up is 

performed (the value of the data item is verified against the values of the Ordinate). 

$ Event data items 

Event data items are shared amongst all Events. Names of Event data items therefore 

have special meaning. 

$ Dictionary items 

Dictionary data items are available throughout a LINC Specification. They cannot have 

different meanings in different parts of the LINC Specification. 

$ Ispecs 

The Ispec name is used in logic and data qualification to reference a group of records 

associated with the Ispec. When a new Ispec name is created, that name becomes a 

reserved word. In certain situations (such as when the Ispec has Memo Data), the Ispec 

name repeated (ispecispec) is also a reserved word (where ispec is the Ispec name). 

Compilation Errors 

In some situations, parts of your LINC Specification may produce compilation errors, even 

though they appear to be correct. These compilation errors usually arise from naming 

conflicts, as illustrated in the following examples: 

$ A compile error occurs if you create a Global Setup Data item ISP1-DA1 in a LINC 

System that also has an Ispec ISP1 with a data item DA1. 

Ispec names are used in data qualification, in the form ispec.item. In the code of your 

generated LINC System, these items are included in the form ispec-item. Avoid naming 

parts of your LINC System that may result in conflicts with generated names. 

$ A compile error occurs if you create a Global Setup Data item B for a LINC System that 

makes use of Extract file B. 

The letters A through Z are used as identifiers for Extract files. Avoid the use of names 

that conflict with these identifiers. 

Additional Considerations for UNIX 

The following are additional considerations for LINC Systems based on the UNIX 

operating system: 

$ For LINC Systems based on the UNIX operating system, some reserved words are 

prefixed with the letter X, and the name is truncated to ten characters. For example, 

AREA is stored as XAREA. This can lead to duplicate data item names. 

v A-3

Checking Reserved Words 

$ For ORACLE LINC Systems, Profiles created automatically for Standard Components 

are named Fispec in LINC Systems based on the UNIX operating system, and not 

Fordinate as for MCP based (or Griffin) LINC Systems. For example, naming two 

Ispecs PROD and FPROD will result in errors in your LINC System based on the UNIX 

operating system. 

$ For ORACLE LINC Systems, descending Profile Ordinates are created in the Ispec 

table as Xordinate in LINC Systems based on the UNIX operating system, where 

ordinate is the name of the Profile Ordinate. For example, naming two data items 

PRODCODE and XPRODCODE will result in errors in your LINC System based on the 

UNIX operating system if PRODCODE is declared as a descending Profile Ordinate. 

$ Reports should not be given names that conflict with program names. 

Avoid the names A---A, G---G, L---L, U---U, and DBACCESS, as these are LINC program 

names. Also avoid names ending with ZZZZ, as Ispec screen layout programs are given 

this suffix. 

You should avoid naming parts of your LINC System that may lead to conflicts. 

Checking Reserved Words 

Your installation of LDA 2.3 includes the Reserved Words List utility (reserved.exe). Use 

this utility to check the reserved words for the following target hosts: 

$ MCP based hosts 

$ OS 2200 based hosts 

$ UNIX based hosts 

$ Windows NT 

To see a list of reserved words for one or more of these hosts: 

1. Double-click on reserved.exe (in the installation directory). The Reserved Word List 

dialog box is displayed. 

2. Select the host or hosts for which you want to see a list of reserved words. The list of 

reserved words is displayed in alphabetical order. 

3. Use the scroll bar to scroll up and down the list. 

A-4 v

Appendix B 

LINC Limits 

Overview 

This appendix summarizes the limits that are currently in effect with LINC Generate and 

LINC Deployment. See Appendix E for differences in LDA. 

The limits are grouped under the following topics: 

$ ‘‘Conventions’’ 

$ ‘‘Data Items’’ 

$ ‘‘Dictionary Items’’ 

$ ‘‘Global Logics’’ 

$ ‘‘Global Setup Data items’’ 

$ ‘‘Ispecs’’ 

$ ‘‘Profiles’’ 

$ ‘‘Reports’’ 

$ ‘‘Setup Data Items’’ 

$ ‘‘Utilities’’ 

$ ‘‘System Software’’ 

Limits on LINC Logic commands and System Data items are described in your LINC 

Programming Reference Manual. 

Conventions 

In this appendix, limits are summarized in tables. Additional information may be included 

after each table. 

The phrase No limit means that there is no direct limit, although system software and size 

considerations (and the associated increase in edit and generate times) may have an 

impact. 

The phrase System means that the limit is imposed by system software, such as the 

COBOL compiler. 

v B-1

Conventions 

OS 2200 based LINC Systems 

Wherever there is an upper limit subject to the HVTIP program limit, this represents the 

limit imposed by the maximum size of a HVTIP IBANK, which is 65K words for TPE 

systems, and 262K words for UCS systems. This limit does not apply to LINC Systems 

generated as UCS subsystems. 

B-2 v

Data Items 

Data Items 

This subsection contains limits for the various types of data items. Additional limits on 

data items, such as the number of data items in an Ispec, are contained in other parts of 

this section. Limits for Global Setup Data items and Setup Data items are included in their 

own subsections. 

Data items 

The following table contains limits for Data items (defined using the DATA LINC Data 

command). 

Display items 

Type of Data Item Maximum 

Alphanumeric 78 

Usage Inquiry, Alphanumeric 80 

Usage Output, Alphanumeric 4095 

Ispec, Numeric, with NO.DECIMAL.KEYED 18 

Ispec, Numeric, with DECIMAL.KEYED 17 

Report, Numeric 18 

Date Exactly 6 by default (can 

be specified as 8 to 

include the century) 

Report, Alphanumeric Length of printline 

The maximum length for a Display item is 80 characters. 

Keywords 

The total length of a Keyword may not exceed 80 characters. 

Literals 

A numeric literal longer than 18 characters is treated as an alphanumeric literal. Any signs 

or decimal points are included in the literal length. For Setup Data items or Global Setup 

Data items with initial values, signs and decimals are not included when calculating the 

length of the item. 

For example, the following is valid: 

 

v B-3

Global Logics 

However, the following MOVE; command is invalid, since the literal is interpreted as 

alphanumeric, as its length is greater than 18. 

 

Ordinates 

The maximum length of each type of Ordinate is shown in the following table. 

Dictionary Items 

Edit Type Maximum 

Alphanumeric 78 

Usage Output alphanumeric 4095 

Unsigned numeric 12 

Signed numeric 11 

The following table contains a summary of the limits for Dictionary items. The total 

number of Ispecs, Reports, Global Logics, and Dictionary items must be less than 999,999. 

Limit OS 2200 MCP UNIX 

Number of items 999,999 999,999 999,999 

Size of a system for Dictionary Maintenance No limit No limit No limit 


In practice, the limit is lowered by the LINC Generate symbol table limit (about 140,000 

symbol items in total). 

Global Logics 

Summary 

The following table contains a summary of the limits for Global Logics. 

B-4 v

Global Logics 


Number of Global Logics 4,088 No limit No limit 

Logic Lines in a Global Logic 999,999 999,999 999,999 

Global Logics in an Ispec No limit No limit 

(900 

Performable 

Global 

Logics with 

Integrity) 

No limit 

Nested Global Logics No limit No limit No limit 

Macro Global Logics in Module Master No limit No limit No limit 

Macro Global Logics inserts in Module 3,000 3,000 3,000 

Number of Global Logics 


The sum of the number of separately compiled Global Logics and the number of Ispecs 

must be less than 4,088 for the HVTIP limit (calculated as 4,095 minus 7, for the seven 

subprograms). No other limits are known. 

Logic Lines in a Global Logic 

There is a limit of 999,999 lines in a Global Logic. 


In practice, generate times and the HVTIP program limit will be reached before this (2,000 

to 5,000 total lines in a Global Logic). Also, there is a limit of slightly less than one million 

total logic lines in LINC Generate for all LINC Specifications, and about 2 million lines of 

generated COBOL. 

Global Logics in an Ispec 

No limit. 

MCP based LINC Systems 

There is a limit of 999 Performable Global Logics in an Ispec (or Global Logic) for an 

Integrity system. 

There is a limit of 9,000 on the total number of inserts of a Global Logic into another Global 

Logic. 

v B-5

Global Logics 

UNIX and OS 2200 based LINC Systems 

For Performable Global Logics, there is a limit of 500 on the number of inserts of a Global 

Logic into an Ispec (including nested inserts). 

Nested Global Logics 

The upper limit for nested Global Logics is the limit on the number of Global Logics in an 

Ispec. 


Separately compiled Global Logics cannot be nested more than five deep (EXEC TIP 

parameter). 

B-6 v

Global Setup Data items 

Summary 


The following table contains a summary of the limits for Global Setup Data items. 


Number of Global Setup Data items No limit No limit No limit 

Size of an alphanumeric Global Setup Data item 9,999 9,999 9,999 

Size of a Global Setup Data item with alphanumeric 

literal 

58 58 58 

Size of a numeric Global Setup Data item 18 18 18 

Size of a Global Setup Data item with numeric literal 18 18 18 

Total size of a Global Setup Data array (characters) 65,000 65,000 65,000 

Size of all Global Setup Data items with initial values No limit No limit No limit 

Size of all Global Setup Data items without initial 

values 

No limit 6,336K 

bytes 

No limit 

Global Setup Data items in an Ispec No limit No limit No limit 

Global Setup Data items in Report No limit No limit No limit 

Number of Global Setup Data Items 


There is no limit on the number of Global Setup Data items (other than the LINC Generate 

symbol table limit of approximately 140,000). However, since Global Setup Data items are 

included in every Ispec and Report (COBOL common storage), their maximum combined 

size, plus the following, must not exceed the HVTIP program limit: 

$ Size of the largest Ispec (not including Global Setup Data items) 

$ Size of any Global Logic in that Ispec (in words) 

Size of Global Setup Data Items 

Maximum size of a single Global Setup Data item is 9,999 bytes. 


Total size of all Global Setup Data items without initial values has a maximum of 6,336K 

bytes. 

v B-7


Number of Global Setup Data Items in an Ispec 

No limit. 

Number of Global Setup Data Items in a Report 

No limit. 

B-8 v

Ispecs 

Summary 

The following table contains a summary of the limits for Ispecs. 


Number of Ispecs 1000 1500 1000 

Number of Data Items in Output Structure 2,400 3,020 254 

Length of Data Items in Output Structure 7,000 bytes 24,570 

characters 

No limit 

Number of Logic Lines in an Ispec 999,999 999,999 999,999 

Number of Nested Database Commands 19 No limit No limit 

References to other Ispecs No limit 999 No limit 

Painted Items in an Ispec No limit No limit No limit 

Painted Items in Copy.From area 100 100 100 

Number of Ispecs 


Ispecs 

The EXEC allows 4,095 HVTIP subprograms, but the code required to call an Ispec will 

cause the ICP to exceed the HVTIP program limit before this limit is reached. The exact 

point of this is unknown, as this is affected by the size of the Global Logic and other such 

issues. 

In the current product, when a system is marked as a Production system (in your LINC 

Generate), the RDMS storage areas have the KEEP-ASSIGNED attribute set to TRUE. 

There is one separate RDMS storage area for: 

$ Each Usage Input-Output or Usage Output Component 

$ The EVENT structure 

$ All Event Profiles 

$ All non-primary and non-Automaint Profiles 

UDS has a limit of 4095 EXEC files assigned at one time, which sets an upper limit on these 

items, unless you turn the KEEP-ASSIGNED attribute off after each database 

reorganization or creation. There are no other known limits. 

v B-9

Ispecs 

TIP storage areas do not have this KEEP-ASSIGNED restriction, but are limited by the 

system maximum number of TIP files (up to 4095). For LINC Systems generated as 

self-contained UCS subsystems, the number of Ispecs is limited by the maximum number 

of dynamically allocated shared BDIs configured in the operating system. 

Number of Data Items in Output Structure 


You can have up to 10 RDMS tables of approximately 240 columns each (2,400 items), 

although no table can exceed 7000 bytes. In practice, you will exceed the HVTIP program 

limit before the maximum number of items can be reached. 


The maximum number of Usage Input-Output and Usage Output items is 3,020 (and is 

limited by the accumulated size). 

LINC Systems based on the UNIX operating system 

There are two distinct limits to the number of Usage Input-Output or Usage Output data 

items in an Ispec. ORACLE allows a maximum of 254 fields in a table. At the edit checking 

phase of the generate process, LINC imposes a limit of 250 Usage Input-Output or Usage 

Output data items in an Ispec. 

Of these, LINC reserves a certain number for the following types of LINC-generated fields: 

$ Standard Ispec fields. These are added to an Ispec record, depending on the type and 

options of the Ispec. These are counted at the edit checking phase of the generate 

process. 

$ Descending key fields. For each data item that is defined as a descending key in any 

profile over the Ispec, an additional data item is added. These are not counted at the 

edit checking phase of the generate process. 

Therefore, there are two rules that apply to the maximum number of Usage Input-Output 

or Usage Output data items: 

$ The number of Standard Ispec fields plus the total number of Usage Input-Output or 

Usage Output data items cannot be more than 250. 

$ The number of descending key fields plus the number of Standard Ispec fields plus the 

total number of Usage Input-Output or Usage Output data items cannot be more than 

254. 

The number of fields reserved for the different types of LINC-generated fields are listed in 

the following table. 

B-10 v

LINC-generated field Subtract 

GLB-DTIME (Memo component) 1 

GLB-DTIME, MAINT (Std component) 3 

ACTMTH, GLB-DTIME, GLB-REPORT, INPUT-DATE, ISPEC, 

XTRANNO (Combined Event) 

LAST-LINE (Any Repeat.from Ispecs) 1 

Descending key fields 1foreach 

Note: Although these are ORACLE limitations, they apply to both ORACLE and 

Griffin LINC Systems. 

6 

Ispecs 

In ORACLE, a data item requiring more than 2000 bytes of database storage is called a long 

data item. The maximum size of a long data item is 2 Gigabytes. There may only be one 

long data item for an Ispec, for both ORACLE and Griffin LINC Systems. 

Note: Component arrays often result in a long data item. 

Size of Ispec or Profile Record 


The maximum length of an Ispec or Profile database record is governed by the RDMS limit 

on maximum database page size (7,168 words) and the RDMS requirement that 4 

maximum-sized records should be able to fit in a page. After allowing for page and record 

control information, this means that approximately 7,000 characters is the maximum 

combined length of all data items in an Ispec or Profile, without the overhead and 

restrictions of the Ispec data being split across two or more tables. 

RDMS also documents that the UNLOAD command can produce data images of up to 8,188 

characters in length. 

An Ispec can have up to 10 tables of approximately 240 columns each (2,400 items). A split 

into extra tables will also occur when the data item length of a table approaches 7,000 

bytes. 

It is strongly recommended that Ispecs are not allowed to become so large that they are 

broken into two or more database tables, particularly for performance reasons. Ispecs that 

have large database field lengths will also suffer from restrictions on lengths for interfaces 

(Automatic Entries, GLI, and NOF). PLE number 15630469 describes special handling for 

Ispecs with very large database fields. 


Usage Input-Output and Usage Output data items are limited to an accumulated size of 

4,065 words (24,570 characters), which is the DMS II record size limit. 

v B-11

Ispecs 


A data item of type long may not be used as an Ordinate or Profile Ordinate. For ORACLE 

LINC Systems, a numeric item included in an index (Ordinate or Profile Ordinate) always 

uses 22 characters. See ‘‘Number of Data Items in Output Structure’’, for a discussion of 

long items. 

The size of a composite key (all Profile Ordinates of a Profile) must be smaller than half 

the database block size. 

Number of Logic Lines in an Ispec 

There is a limit of 999,999 logic lines in each of Pre-Screen, Pre-LINC, and Main Logic. 


In practice, long generate times and the HVTIP program limit will be reached before this 

(from approximately 2,000 to 5,000 total lines in an Ispec). Also, there is a limit of slightly 

less than one million total logic lines in a LINC Generate for all systems, and approximately 

2 million lines of generated COBOL (file sizes). 

Database Commands 


There is a maximum of 19 levels of database commands, that is 19 levels of DETERMINE; 

or LOOK.UP; loops. 

If you exceed 19 levels, LINC will abort with a warning message highlighting the cursor 

name, and a dump of the cursor stack. You can find the cursor name in your Ispec or Report 

symbolic, from which you can find the point in your logic at which the limit was exceeded. 


There is a limit of 999 references to other Ispecs (all Events count as one reference) from 

an Ispec. 

Painted Items in an Ispec 

No limit. Maximum of 100 items in the Copy.From area of the screen layout for a 

Copy.From Ispec. 

Internal Database Storage Order 


Ispec data items are stored in the database in the following order: alphanumeric items (in 

alphabetical order), numeric items (in alphabetical order), and a filler item if defined. 

B-12 v


Ispecs 

Data items used as Ordinates are defined first (in their defined order), followed by all other 

data items (in alphabetical order). 


Data items used as Ordinates are defined first (in alphabetical order), followed by all other 

data items (in alphabetical order). 

v B-13



Summary 

The following table contains a summary of the limits for Profiles. 


Number of Profiles No limit No limit No limit 

Number of Ordinates in a Profile 20 20 20 

Length of Profile Ordinates 157 bytes No limit 240 bytes 

Number of Lines in a Profile Definition 99 99 99 

Number of Profiles 


No limit, other than the UDS file limit. However, there can be no more than 99 Profiles over 

a particular Component or the Event table structure. 


No limit, although DASDL may impose an upper limit. 

Number of Ordinates in a Profile 

There is a maximum of 20 Ordinates to a Profile. 


For ORACLE LINC Systems use only the first 16 Profile Ordinates. 

Length of Profile Ordinates 


The length of all the Ordinates for a Component and all its Profiles may not exceed 157 

characters. In calculating the length of numeric Ordinates, add one to the length defined by 

the LENGTH; Data Attribute, and add another one if the Ordinate has the DECIMALS; Data 

Attribute. 

If a Profile is not an Automaint or Primary Profile and it has a numeric Ordinate that is 

binary on the RDMS database, you must also allow for the database storage size for the 

Ordinate; that is, 4 characters for INTEGER and NUMERIC, and 2 bytes for SMALLINT. 

B-14 v

If an Ordinate exists in the Component and in one or more Profiles, you only count its 

length once. Event Ordinate lengths should be counted in the same way. 


The System Data item GLB-DTIME plays the part of an Ordinate for Memo Components 

and the Event Structure, therefore you must allow eight characters for it in all except 

Standard Components. 


No limit, although DASDL may impose an upper limit. 


The sum of the lengths of all Profile Ordinates is limited to half the database block size. A 

data item of type long may not be used as an Ordinate. For ORACLE LINC Systems, a 

numeric item included in an index (Ordinate or Profile Ordinate) always uses 22 

characters. 

Number of Lines in a Profile Definition 

There is a limit of 99 lines when defining your Profile (that is, lines for COMP.NAME; or 

EVENT.NAME; commands, ORDINATE; commands, DO.WHEN; conditions and, for MCP 

based LINC Systems, DATA; commands). You should use this limit at your discretion as 

your system may experience memory problems. 

v B-15

Reports 

Reports 

Summary 

The following table contains a summary of the limits for Reports. 


Reports in a LINC System No limit No limit No limit 

Logic Lines for a Report Frame 999,999 999,999 999,999 

Database Commands No limit 19 No limit 

References to Ispecs (all Events count as 1 reference) 

from an Report 

999 999 999 

Performable Global Logics in a single Frame 900 900 900 

Performable Global Logics in a Report 900 900 900 

Display items in one Report Frame 204 204 204 

Display and data items in one Report Frame 450 450 450 

Global Setup Data items in a Report 220K words 

(TPE) 

Setup Data items in a Report Frame 220K words 

(TPE) 

999x64K 

bytes 

64K bytes 

64K bytes 64K bytes 

Size of generated Report code System System System 

Files Used in a Report System System System 

Extract files in a Report 26 26 26 

Physical size of Extract files created within a Report 262,143 - No limit 

tracks/positions 

Size of Extract file (Extracted Frame, 80-byte records) No limit Expected 

number 

field to 

99,999,999 

Size of Extract file (Ispec) No limit Expected 

number 

field to 

99,999,999 

Attached Reports running at one time for a LINC 

System 

Standalone Reports running at one time for a LINC 

System 

- 150 - 

No limit 

No limit 

System System System 

continued 

B-16 v

continued 

Reports 


Sorting No limit Sor memory 

999K 

words, Sort 

disk 

999,999K 

words 

Size of RIP file card equates - 1,990 

characters 

Number of Logic Lines for a Report 

999,999 lines for each Frame, and 999,999 lines for Main logic. 


No limit 

In practice, the limits are similar to Ispecs, except that UCS Reports have a much larger 

limit. 

Setup Data items in a Report Frame 

MCP Based LINC Systems 

A separate limit of 64K bytes applies to Setup Data items with initial values and Setup Data 

items without initial values. 

Database Commands 


There is a maximum of 19 levels of database commands, that is 19 levels of DETERMINE; 

or LOOK.UP; loops. 

If you exceed 19 levels, LINC will abort with a warning message highlighting the cursor 

name, and a dump of the cursor stack. You can find the cursor name in your Ispec or Report 

symbolic, from which you can find the point in your logic at which the limit was exceeded. 


There is a limit of 999 references to other Ispecs (all Events count as one reference) from 

an Ispec. 

Global Setup Data Items in a Report 

There is no limit to the number of items. 

v B-17 

-

Reports 


TPE Reports have an approximate limit of 220K words. 


The accumulated size is limited to 64K bytes. 


The accumulated size is limited to 64K bytes. 

Setup Data Items in a Report Frame 

There is no limit to the number of items. 


TPE Reports have an approximate limit of 220K words. The limit is not known for UCS 

Reports. 


The accumulated size is limited to 64K bytes for every Report Frame. 


The accumulated size is limited to 64K bytes for every Report Frame. 

Size of Generated Report Code 

This limit is a function of system software. See ‘‘System Software’’. 

Files Used in a Report 

This limit is a function of system software. See ‘‘System Software’’. 


LINC uses the SORT program, and is subject to its particular limits. 

LINC creates the sort sizes in the Report Runstreams. If these are insufficient for a 

particular Report, manually change these assignments. 

Physical Size of Extract Files Created Within a Report 


The EXEC file size limit of 262,143 tracks or positions applies. 

B-18 v


If the Extract is a Frame, a limit of 99,999,999 records applies (set on the Extract File 

Options screen). 

Reports 

If not an Extract Frame, the file size is taken from the value of the Expected Number field 

for the Ispec (limit of 99,999,999 records set on the Extract File Options screen). 

v B-19



Summary 

The following table contains a summary of the limits for Setup Data items. 


Number of Setup Data items No limit No limit No limit 

Size of an alphanumeric Setup Data item 9,999 9,999 9,999 

Size of a Setup Data item with alphanumeric literal 58 58 58 

Size of a numeric Setup Data item 18 18 18 

Size of a Setup Data item with numeric literal 18 18 18 

Total size of a Setup Data array (characters) 65,000 65,000 65,000 

Size of all Setup Data items with initial values No limit No limit No limit 

Size of all Setup Data items without initial values No limit See text No limit 

Setup Data items in an Ispec No limit No limit No limit 

Setup Data items in Report No limit No limit No limit 

Number of Setup Data Items 

No limit. 

Size of Setup Data Items 

Maximum size of a single Setup Data item is 9,999 bytes. 


Setup Data items without initial values have a maximum limit of 99 Ispecs with greater 

than 64K byes of Setup Data items or the equivalent size in one Ispec. 

Setup Data Items in an Ispec 

B-20 v



There is no limit on the number of Setup Data items (other than the LINC Generate symbol 

table limit of approximately 140,000). However, since Setup Data items are included in 

every Ispec and Report (COBOL common storage), their maximum combined size, plus the 

following, must not exceed the HVTIP program limit: 

$ Size of the Ispec (including Global Setup Data items) 

$ Any Global Logic in that Ispec (in words) 

Setup Data Items in a Report 

See ‘‘Reports’’. 

v B-21

Utilities 

Utilities 

Summary 

The following table contains a summary of the limits for Utilities. 


Automatic Entry buffer 2000 bytes 2000 bytes 2000 bytes 

DMU No limit 3855 Ispecs No limit 

Generation No limit No limit No limit 

GLI programs No limit 1 No limit 

LINC System Transfer No limit 2000 

Reports 

No limit 

Log No limit 3855 Ispecs No limit 

NOF programs No limit No limit No limit 

Recovery No limit 195 RUN; 

commands 

No limit 

Reorganization No limit Some limits No limit 

Translation (language) 15 15 15 

For LCOPY, see your LINC Developers Guide: LCOPY. 

Automatic Entries (HUB) 

Generation 

The Automatic Entry buffer size is 2000 bytes. 

No limit. 

GLI Programs 

LCOPY 


Only one GLI program may be running. 

B-22 v

See your LINC Developers Guide: LCOPY for limits on LCOPY. 

LINC System Transfer 


Up to 2000 Reports can be transferred in a single non-tape transfer and configure. 

NOF Programs 

Recovery 

The only limits are those relating to how you write your NOF program. 


Utilities 

The initiation information for the last 195 Reports initiated by Ispecs and by all START; 

LINC logic commands is retained so that the Report or WFL can be correctly rerun in 

recovery. 

Reorganization 

Translation 


There is no limit to the number of DASDL structures in an online reorganization 

There is a limit of 3,855 DMS II structures in a DASDL where that DASDL can be processed 

by using DMU. There is a limit of 1,000 datasets of Memo data that can be reorganized. This 

applies to reorganizations initiated by DMU (for example, a garbage collect) and by a 

generate. 

You are limited to fifteen languages for a LINC System. 


Data Displays are in an RDMS table, and should not be limited there. Translatable Global 

Setup Data items are all in the G---G Ispec so their combined size (including up to 15 

languages) is subject to the HVTIP program limit. 

v B-23

System Software 


Summary 

These are not LINC limits, but will apply to your generated code, and should be taken into 

account during design of a system. 

Stations/Users 


Stations/Users No limit COMS limit No limit 

Size of LINC Generate Database No limit System limit No limit 

Size of Generated Code System System limit System 

Size of Generated Report Code System System System 

Sorting order ASCII EBCDIC ASCII 


COMS limit. 

Size of LINC Generate Database 


Approximate sizes of some LINC Generate files follow. 

$ LOGST (LDL lines): about 1.5 million records 

$ GSRCE (generated COBOL): about 2 million records 

$ SYMBL (symbol table): about 200,000 records 

$ LXREF (overflow of code): about 220,000 records 

$ EVENT (Data definitions, screen definitions, and so on): about 663,000 records 

These numbers represent a lower limit to the maximum number of records that these files 

will hold. Due to space compression on trailing blanks, in practice you may get 

considerably more records than those quoted. Absolute maximums are difficult to quote 

due to the variable nature of the data. 

Size of Generated Code 

B-24 v



$ TPE 65K word limit. 

2,000 to 3,000 lines of LINC code will generally be enough to approach this limit. 

$ Maximum SUP limits apply for transactions for generate and LINC Generate. Some 

large Ispecs can exceed the SUP limits for transactions before commit points (this has 

been noted on a Ispec with 450 screen items). 

$ HVTIP II is available on 2200 M-Series machines only and implemented for LINC in 

UCS mode generation only. 

LINC does not currently support all of the features of HVTIP II. The total number of 

BDIs allocated to program level heap banks cannot exceed 63. 

For LINC Systems generated as UCS subsystems, code size is limited by the maximum 

number of dynamically allocated, shared BDIs configured in the operating system. 


COBOL74 compiler limits, for example, STACK SIZE and CODE SEGMENT SIZE. 

The compiler limit is extended by two to three times if the option to have large COBOL 

programs is invoked (this is the default). See your MCP Based LINC Administration and 

Operations Guide for more details. 


MicroFocus COBOL compiler limits. 

Size of Generated Report Code 

Sorting Order 


The TPE limit is approximately 220K words. UCS is limited by UCOB compiler limits. 


MicroFocus COBOL compiler limits. 

The sorting sequence is different on the different host types. Where high or low 

alphanumeric values are required, use the System Data items GLB.HIGH and GLB.LOW to 

avoid any problems this could cause. 


ASCII 


EBCDIC 

v B-25



ASCII 

B-26 v

Appendix C 

Features of OS 2200 Based LINC 

Systems 

This subsection covers the following topics. 

$ ‘‘Features of LINC Logic’’ 

$ ‘‘Features of LINC System Commands’’ 

$ ‘‘Features of System Data Items’’ 

$ ‘‘Features of Utilities and Report Handling’’ 

$ ‘‘Features of LINC Generate’’ 

$ ‘‘Miscellaneous Differences’’ 

Features of LINC Logic 

The following points relate to differences between OS 2200 and MCP based LINC logic 

commands. 

$ The ACCESS.EXT; command is not available for OS 2200 based LINC Systems. The 

ACCESS.EXT; command is a facility which allows you to inquire against DMS II 

databases from within your LINC System on MCP based machines. To access a 

DMS 1100 database, you must write an access routine and initiate it using the CALL; 

command. See your LINC Programming Reference Manual for more information on 

the CALL; command. 

$ Differences in results of the COMPUTE.FROM; command be experienced, since 

intermediate results are stored in different ways. Intermediate results from an MCP 

based host will always contain enough decimals, regardless of the precision of the final 

result. On OS 2200 based LINC Systems, the intermediate results have the same 

precision as the final result, and truncations may occur. 

$ DO.WHEN; commands with more than 50 conditions will cause COBOL compilation 

errors when configuring your OS 2200 based LINC System. 

$ For multiple line messages, a MESSAGE; command must be coded for each line. The 

messages are displayed on MCP based LINC Systems in reverse order to which they 

are coded, but on OS 2200 based LINC they are displayed in the order specified on the 

OS 2200 based System Environment Options screen. 

$ The RUN; logic command must be coded with a device, otherwise the LINC Editor will 

return an error. However, this does not affect the execution of the Report. The output 

is directed to the default device specified for the Report. 

v C-1

Features of LINC System Commands 

$ A SECURE; option with a LOOK.UP; or DETERMINE; command in your current 

transaction that accesses a database table from which you have already updated a 

record earlier in the same transaction, results in an RDMS error 6002 and an RDMS 

error 23030. Here a transaction is defined as including the Pre-LINC and Main Logic of 

the current Ispec, plus the Pre-Screen logic of a recalled Ispec. To avoid this, position 

your updating logic after commands with the SECURE; option. 

$ The START; command executes a user-written OS 2200 based ECL runstream. No 

status is returned to your LINC System on the success or otherwise of the runstream, 

although if the runstream cannot be found, GLB.STATUS will contain INVAL. Ifthe 

runstream has been found and at least started, GLB.STATUS will contain all spaces. 

Note: The account code and userid, under which the runstream is run, 

must match those of the LINC Background Run. The default account 

code and userid are the ones specified when LINC Deployment was 

installed. 

To use the START; command, place the runstream you wish to start in the following 

file: 

 

The START; command should be coded in LINC logic as follows. 

 

The element value gives the name of the element in the system*START$ file that 

contains your runstream. To use the START; command, create the required ECL and 

copy as an element into the system*START$ file. You cannot pass any parameters to 

the runstream. 

If the Ispec is repeated as part of recovery, the START; command is repeated. 

$ The STN.INFO; command has no effect on OS 2200 based LINC Systems. If used, it will 

always return GLB.STATUS of *****. 

Features of LINC System Commands 

The following LINC System (colon) commands are not available on OS 2200 based hosts. 

:ADH :AHB :ALR :AST :AUP :BDD :CDT :DBS 

:ISP :LIS :LOG :MAX :MIN :MOR :MXL :NEX 

:REL :ROC :RPR :SHR :SIN :SMG :STO :SUB 

:TEA :TIN :UPD :USR :WHA :WHO 

You cannot enter a device with the :RUN LINC System command. The default device is 

always used. 

C-2 v

Features of System Data Items 

Features of LINC Generate 

The following System Data items are not valid for OS 2200 based LINC Systems: 

 

 

 

 

 

 

 

 

GLB.MACHINE is set to 1 for all LINC Systems running on OS 2200 based hosts. 

Features of Utilities and Report Handling 

The following points relate to differences between MCP and OS 2200 based LINC Utilities 

and Report handling. 

$ LINC Ad Hoc Inquiry is not available for OS 2200 based LINC Systems. However, 

IPFSQL and MRI can inquire directly against the RDMS Database which LINC creates 

for you, but neither product should be used to update the database. See your OS 2200 

Based LINC Administration and Operations Guide for more details about IPFSQL 

and MRI. 

$ OS 2200 based ROC handles Report output for all LINC Systems within LINC 

Deployment. That is, there is only one ROC System for every copy of LINC 

Deployment. 

$ When printing a Report, the following fields on the ROC Write Request screen are 

ignored: Banners, Dest.host, Align form, Align file. 

$ The LINC Terminal Printer Spooler (TPS) is not available for OS 2200 based LINC 

Systems. 

$ The LINC Log and LINC Monitor facilities are not available for OS 2200 based LINC 

Systems. 

$ If you specify the default output device for a Report as VD (for video), the output is not 

automatically displayed at your terminal as soon as the Report is finished (as it is for 

MCP based users). To view the output, you must access ROC. 

Features of LINC Generate 

The following points relate to differences between OS 2200 and MCP based LINC Generate. 

$ Embedded control characters that may be meaningful in MCP environments may 

cause screen corruption in OS 2200 environments. You should be aware of this when 

copying MCP based LINC Systems to OS 2200 environments. 

v C-3

Miscellaneous Differences 

$ Reports produced by LINC Generate utilities (for example, an LDL listing) can only be 

directed to a line printer. 


The following points relate to other miscellaneous differences between OS 2200 and MCP 

based LINC. 

$ The use of the Profile attribute that does not allow duplicates has no effect on OS 2200 

based systems. You must add your own logic to prevent duplicates. 

$ The sorting sequence is different. MCP environments uses EBCDIC, while OS 2200 

environments use ASCII. Where high or low values are required, use the GLB.HIGH 

and GLB.LOW System Data items for compatibility. 

$ Reserved words list differs between MCP and OS 2200 based LINC Systems. 

$ A relational database (RDMS) is used on OS 2200 based hosts. RDMS does not have a 

concept of subsets of indexes, therefore conditional Profiles are implemented by 

creating an additional table containing the appropriate index. 

$ There is no concept of an MCP based LINC Update program on OS 2200 based hosts. 

The functions of an Update program are performed by an ICP (Initial Control Program) 

and COBOL subprograms for each Ispec. This means if you change only some Ispecs, 

these will be compiled and installed without recompiling the remaining Ispecs. 

Because there are no Update programs, there are no LINC Subsystems. The 

manipulation of relative transaction priorities must be performed by the user by using 

the standard TIP Utilities. 

$ All alphanumeric fields are truncated by RDMS before a record is stored. Trailing 

spaces are removed, although one space is always stored. This results in 

variable-length records. A database therefore uses less storage on an OS 2200 based 

host, thus the needs to rationalize the Event set or to use Memo Data rather than 

Events is reduced. 

$ The MCP based concept of multiple screen pages has been implemented in OS 2200 

based LINC Systems, by using Function keys. 

$ A new Data attribute (DIM) has been provided for OS 2200 based terminals, to display 

fields in low intensity. 

$ The BRIGHT Data attribute has no effect on OS 2200 based terminals, other than to 

reset the DIM attribute. 

$ Only 23 lines of the screen may be used on OS 2200 based Systems, compared to 24 

lines for MCP based LINC Systems. 

If a screen that uses line 24 is transferred from an MCP based host, and the screen 

contains blank lines, the first blank line is deleted and the remaining lines are moved 

up. If all 24 lines are used, attempts to generate the Ispec for your OS 2200 based LINC 

System will fail. The screen must be rearranged using Painter in LINC Generate. 

C-4 v


$ MCP based hosts treat numeric fields containing spaces as if they contained zeros. 

Moving GLB.SPACES to a Group Setup Data item with elementary numeric fields does 

not cause problems in an MCP based LINC System. For OS 2200 based LINC Systems 

this gives unpredictable results. Use the INITIALIZE; command to alleviate this 

program. See your LINC Programming Reference Manual. 

$ The MEMO Data attribute has no effect with OS 2200 based LINC Systems. 

$ Highlighting attributes are handled differently. For MCP based LINC Systems, a 

highlighting attribute is turned on by a control character which occupies the character 

immediately before the data or display item. For OS 2200 based LINC Systems, the 

attribute is turned on by an FCC that is contained in the first character of the data or 

Display item. For compatibility with MCP based LINC Systems, a data or Display item 

with highlighting attributes should not start in column one. 

$ In OS 2200 based LINC Systems, unlike MCP based LINC Systems, you do not require a 

physical screen position for field delimiters or attributes. The Suppress Delimiters 

field on the OS 2200 based System Environment Options screen gives you the option to 

free these positions, giving you more screen space for your fields and field names. 

However, if you take the option to suppress delimiters on any host other than OS 2200 

based hosts, you may only do so if your LINC Specification has an OS 2200 based 

target host. 

Another consequence of this option is that attributes cannot be shown on painted 

screens. You should enable Menuassist in the LINC Painter to show the Data attributes 

applied to fields. 

v C-5

Appendix D 

Features of LINC Systems Based on the 

UNIX Operating System 

Overview 

Features of LINC Systems based on the UNIX operating system are discussed under the 

following headings: 

$ ‘‘Structural Features ’’ 

$ ‘‘ORACLE and Griffin Considerations ’’ 

$ ‘‘Features of LINC Logic ’’ 

For further detail of differences between the various host types, refer to the other 

appendixes of this guide. 

Structural Features 

Overview 


$ Architecture 

$ Identification 

$ Profiles 

$ Reports 

$ Reserved Words 

$ Terminals 

Architecture 

$ Translation 

$ LINC Systems based on the UNIX operating system consist of separate subprograms 

for each Ispec, Report, and separately compiled Global Logic. These subprograms 

communicate through a controlling program (ICP). There is no concept of subsystems 

for LINC Systems based on the UNIX operating system. 

v D-1


Identification 


$ For LINC Systems based on the UNIX operating system, the code for Global Logics is 

included with the code in each Ispec program. Performable Global Logics can be 

compiled as separate programs. 

$ LINC Systems based on the UNIX operating system can be compiled to interpretive 

(intermediate) or native code. The latter run faster but create larger code files. 

$ LINC Systems use ORACLE or Griffin as the underlying Database Management System 

(DBMS). LINC Generate uses Griffin as its underlying DBMS. See ‘‘ORACLE and Griffin 

Considerations ’’, for specific differences. 

$ In a LINC System based on the UNIX operating system, a pack is a physical location, 

that is, a directory for LINC System files, or an ORACLE or Griffin Tablespace for a 

LINC Database. 

Packs are related to directories, or to ORACLE or Griffin Tablespaces by using the 

LINC Pack Definition screen based on the UNIX operating system in LINC Generate. 

These relationships can be modified using the LINC Configure Utility when a LINC 

System is loaded on to the UNIX host. 

$ In some circumstances, if you move group data items, your data may not be converted 

consistently. The stability of this type of operation depends on the architecture, 

compiler, and the release you are running. 

For example, if the signed data is placed in an unsigned field, the contents of SDDEC 

are undefined and are not guaranteed to contain the signed or the unsigned definition 

you may have expected. 

 

 

 

 

 

 

 

 

 

Identification of a user of a LINC System is based on username rather than station. For 

LINC Systems based on the UNIX operating system, GLB.STN, and GLB.USERCODE 

contain the username of the current user. 

Users with the same username may not access the same LINC System at the same time. If 

there are to be multiple users of a LINC System, each user must have a different username. 

For LINC Systems based on the UNIX operating system, all Profiles allow duplicates. The 

setting of the Profile field Allow Duplicates is ignored for LINC Systems based on the 

UNIX operating system. 

D-2 v

Reports 


$ The LINC Report Output Control System (ROC) handles all Report output. See your 

LINC Administration and Operations Guide for the UNIX Operating System for 

details. If a :RUN command is entered with an output device of VD, output is not 

displayed at the terminal. To view the output, access the LINC Report Output Control 

System. 

$ Reports initiated using the LINC System :RUN command run in the foreground by 

default. 

$ All lines in an Extract file must have the same length. 

Use the fixformat script to adjust lengths of Extract files. See your LINC 

Administration and Operations Guide for the UNIX Operating System for more 

details. 

Records in Extract files created by LINC Systems based on the UNIX operating system 

include a separator character (for example, formfeed or newline) between each 

record. 

Reserved Words 

Terminals 

The list of reserved words for LINC Systems based on the UNIX operating system is 

different across the various host types. See the Reserved Words appendix for a list of 

reserved words and considerations when developing LINC Systems. 

The following issues are significant in the operation of LINC Systems based on the UNIX 

operating system. See your LINC Administration and Operations Guide for the UNIX 

Operating System for details of function keys and terminal settings. 

$ For LINC Systems based on the UNIX operating system, multiple error messages are 

automatically returned to page 3 of your terminal (not page 2 as on A Series). 

$ Do not use hard-coded control characters in literals. Use hexadecimal literals instead 

(for example, @5D@). Hexadecimal characters cannot be used to control screen 

formatting. Literals are described in the LINC Generate Operations Guide. 

$ Do not use the literals @00@ and @25@ in LINC Specifications. These will cause 

COBOL syntax errors. Literals are described in LINC Generate Operations Guide. 

$ Highlighting characters used for a LINC System based on the UNIX operating system 

are different from those for an MCP based LINC System. Data Attributes (such as 

BRIGHT and REVERSE) must be used to produce highlighting. Browsing Report 

output using the LINC Report Output Control System (ROC) does not display some 

highlighting attributes. 

$ You may choose whether full page transmission is used; that is, whether all of the 

fields on a screen are transmitted regardless of the position of the cursor. See your 

LINC Administration and Operations Guide for the UNIX Operating System for 

details of the function key that controls this function. 

v D-3

ORACLE and Griffin Considerations 

Translation 

$ When running LINC Systems based on the UNIX operating system on a terminal that is 

not capable of displaying 25 lines, 24 lines, including the Status line, are displayed on a 

screen. You can use the STATUS key to control whether the Status line is displayed. 

If it is displayed, the Status line covers a line on the screen. If the cursor is moved to 

the covered line, the Status line will move either to the top or the bottom of the screen 

so that screen data is visible on the cursor line. 

If your terminal (or emulator) is capable of displaying 25 lines, set the environment 

variable LINCII_TERM25 to YES. See your LINC Administration and Operations 

Guide for the UNIX Operating System for details. 

$ Files used in translation (for example LLANGUAGE), must have a fixed length of 80 

characters. Use the fixformat script to adjust lengths of these files. See your LINC 

Administration and Operations Guide for the UNIX Operating System for more 

details. 

$ The LINC System command :SLA does not support the following form for LINC 

Systems based on the UNIX operating system: 

 

ORACLE and Griffin Considerations 

The following restrictions and limits arise from differences between ORACLE and Griffin. 

Some ORACLE limits have been applied to Griffin LINC Systems to maintain compatibility 

between the two types of database. 

$ ORACLE does not have the concept of subsets and indexes. Conditional Profiles are 

implemented internally by creating an additional table containing the appropriate 

Profile Ordinates as fields. Conditional Profiles in Griffin LINC Systems are 

implemented internally by using conditional indexes. 

$ Memo Data (created using the MEMO Data Attribute) is not supported by ORACLE or 

Griffin LINC Systems. 

$ Reducing the number of decimals associated with a number means that the number is 

rounded following a reorganization of the LINC Database, not truncated as on some 

other host types (for example, for MCP based LINC Systems). 

$ All alphanumeric fields are compressed (by removing trailing spaces) by ORACLE 

before being stored, resulting in variable-length records. A database therefore uses 

less storage to store the basic Ispec tables. The need for rationalizing the Event set and 

the use of Memo Data is reduced. 

Conditional Profiles do, however, require extra space. 

$ Negative numbers may be stored in the LINC Database in EDIT; N data items by the 

FLAG; or AUTO; commands. For an MCP based LINC System, such items are stored as 

positive numbers. 

D-4 v


Changing the edit type of a data item from alphanumeric to numeric (or the reverse) 

results in the loss of data when your system is generated and its database is 

reorganized. The changed data items will contain zero or spaces as appropriate. 

$ For ORACLE LINC Systems, ORACLE Hints may be used to optimize performance. See 

your LINC Administration and Operations Guide for the UNIX Operating System 

for details. There is no equivalent for Griffin LINC Systems. 


The following are features of LINC logic and System Data items for LINC Systems based on 

the UNIX operating system. See your LINC Programming Reference Manual and LINC 

Programming Reference Handbook for differences in the implementation of System Data 

items and LINC Logic commands across the various host types. 

$ For LINC Systems based on the UNIX operating system, setting Integrity means that 

when records (rows) are read, they are locked. When the records are to be updated, 

the record is locked exclusively. Locked records may not be updated by another user 

until the lock is released. 

$ See your LINC Generate Operations Guide. 

$ If spaces are moved to a Group Setup Data item, the value of a numeric Setup Data 

item in that group is spaces. For an MCP based LINC System, the result is zeros.Use 

the INITIALIZE; command to address this difference. See your LINC Programming 

Reference Manual. 

$ The ACCESS.EXT; command is not available for LINC Systems based on the UNIX 

operating system. An equivalent function to this command may be created using the 

CALL; command. See your LINC Administration and Operations Guide for the UNIX 

Operating System for details. 

$ The parameters associated with the CALL; command have different functions for LINC 

Systems based on the UNIX operating system. 

$ The use of GLB.EOP with the CURSOR; command enables all screen fields to be 

transmitted. Since this occurs automatically in LINC Systems based on the UNIX 

operating system, the use of GLB.EOP is ignored unless full page transmission has 

been disabled. 

$ For ORACLE LINC Systems, DETERMINE; BACK and DETERMINE; LAST commands 

can make significant demands on resources. See your LINC Administration and 

Operations Guide for the UNIX Operating System for details. There is no equivalent 

for Griffin LINC Systems. 

$ ORACLE uses different cursors for nested DETERMINE; LINC logic commands that 

use the same Profile, which means that such commands are independent. Nested 

commands for Griffin LINC Systems (and MCP based LINC Systems) are not 

independent. 

$ The EXCLUSIVE.USE; command locks all the records of one Component, or of all 

Events. It is ignored if the Ispec has already been accessed using the SECURE; 

command. 

v D-5


$ The directory in which the Extract file is to be stored must exist before the EXTRACT; 

command is executed. See your LINC Administration and Operations Guide for the 

UNIX Operating System for details. 

$ SLEEP; or CRITICAL.POINT; commands must not be included in loops created by 

DETERMINE; or LOOK.UP; commands, where either the SECURE; command is used, 

or when Integrity is set for the LINC System. 

$ The START; command executes a UNIX shell script, whose name is given by the first 

parameter. The script is run in the background asynchronously with the current 

transaction. 

$ You should avoid coding a WAKE.UP; command immediately after updating your 

database, as the updates may not have been committed before the Report is initiated. 

Suggestions for handling this situation are: 

v Include a SLEEP; command before the WAKE.UP; command, ensuring that there 

is sufficient time for the update to be committed. 

v Recall another Ispec that performs the WAKE.UP; command. 

v Include logic in your Report to handle this situation. 

$ For LINC Systems based on the UNIX operating system, GLB.HIGH should not be 

moved to numeric data items. The resulting COBOL code moves zero to the data item. 

D-6 v

Appendix E 

Differences between Host LINC and LDA 

This appendix describes the current differences between host LINC and LDA. It details 

host LINC features not implemented in LDA and features that are implemented differently 

in LDA. Differences are included under the following headings: 

$ ‘‘System-Wide and General Differences’’ 

$ ‘‘Ispec and Report Differences’’ 

$ ‘‘Data Item Differences’’ 

$ ‘‘Data Attribute Differences’’ 

$ ‘‘Profile Differences’’ 

$ ‘‘Generation and Validation Differences’’ 

$ ‘‘Logic Differences’’ 

$ ‘‘System Data Item Differences’’ 

$ ‘‘Global Logic Differences’’ 

$ ‘‘Run Time Testing Differences’’ 

v E-1

System-Wide and General Differences 


This subsection outlines system-wide and general differences between LDA and LINC 


External Automatic Entries (HUB and OLTP) 

For LDA Run Time, NODB is returned in GLB.STATUS. 

Generalized LINC Interface (GLI) 

GLI is not implemented in LDA Run Time. 


A direct generate function is available in LDA, but only to NT LINC. LINC Specifications 

(Business Segments in LDA) are interpreted directly from the Repository by LDA Run Time. 

LINC Ad Hoc Inquiry 

This utility is not implemented in LDA Run Time. 

LINC Report Output Control System (ROC) 

This utility is not implemented in LDA Run Time. The ROC.MODE; command performs a 

recall to the Pre-Screen logic of the calling Ispec. 

LINC System Commands 

LINC System commands are not implemented in LDA. 

Logical Databases 

Logical databases are not implemented in LDA. 

LINC Modules 

The host development Modules functionality is not implemented in LDA. 

Macro Global Logics 

The host development macro global logic functionality is not implemented in LDA. 

Multiple error messages 

For host LINC Systems, multiple error messages are displayed on Page 2. 

For LDA Run Time, they are displayed in separate dialog boxes. Press Ctrl+M or 

ALT+TAB to see error messages. 

Offline 

Offline is not implemented in LDA Run Time. 

E-2 v

Output Control Codes 


Output Control Codes are not implemented in LDA Run Time. However, if this data is 

transferred to LDA Development from the host it will be preserved so that it can be 

transferred back. 

Change identifiers 

The change identifier in LDA is always the user name that is entered in the login dialog 

box. However, unlike the host development system LDA also keeps the PC name 

associated with every change - on the host you must choose one or the other. 

Patch identifiers 

Patch identifiers in host LINC have a maximum length of six numeric digits, and must be 

unique within the Specification (Business Segment). 

Patch identifiers in LDA have a maximum length of 17 alphanumeric characters, and must 

be unique across all Business Segments. You can specify an alphanumeric prefix of up to 

11 characters that will be added to patch identifiers extracted from host LINC and loaded 

into LDA Development, by setting the PatchName parameter in the LINC.INI file. 

When you extract from LDA, the full 17-character patch Identifier is extracted. When you 

load the LCIF file into host LINC, CASE Load will attempt to strip off the alphanumeric 

prefix of the patch identifier and load only the numeric suffix. If you want to load patch id 

information from LDA to host LINC, you should take care to create patch identifiers in 

LDA with unique numeric suffixes. 

Patch extraction and application 

In LDA there is no facility to extract and apply patches by lines changed, because LDA 

does not track line numbers. 

Change, Patch and Audit control 

LDA uses the Security module to administer change, patch and audit control for the 

development environment. 

Version Control 

LDA has the ability to track multiple versions of LINC source through the use of an 

optional external Version Control Bank based on UREP technology. The host development 

environment does not have this capability. 

Report generates 

LDA supports report generation for NT LINC only. LDA Run Time produces reports 

directly from the repository. 

Report tracing 

This facility is not implemented in LDA Run Time or Direct Generate. 

v E-3


Resource locking 

For host LINC Systems, you can lock groups of objects. For LDA Run Time, you can lock 

individual objects only. 

Security 

The LDA Security module provides the same functionality as the host LINC Security 

Module (LSM), but without the access and station options. 

Supervisor functions 

Supervisor Mode (SUP) of LINC Generate is not implemented in LDA Development. 

Some similar functions are available in the LDA Development environment, for example, 

Ispec, Global Logic and Report lists. 

Teach screens 

For host LINC Systems, Teach screens are displayed on Page 2. For LDA Run Time, they 

are displayed in a separate dialog box. 

Type checking rules 

LDA does not enforce the type checking rules of host based LINC systems. LDA does not 

allow the use of an Ispec-qualified numeric data item with an alphanumeric data item in 

the DO.WHEN; and FLAG; commands. 

USER interface 

USER is not implemented in LDA Run Time. 

E-4 v

Ispec and Report Differences 

Ispec and Report Option Differences 

This subsection outlines Ispec and Report option differences between LDA and LINC 


Fields not implemented 

The following fields are not implemented in LDA Development: 

Extract path 

Field 

LINC Security level 

Updates allowed 

For LDA Run Time, you can define a path for each Report. If not specified, the database 

default path is used. Extract paths for deployment can be fully defined within Systems. 

Ispec Types 

Table Components are implemented in LDA as standard Components. There are no 

functional differences however; a Table Component does not get completely loaded into 

memory. 

Repeat.From Ispecs 

Repeat.From Ispecs are not implemented in LDA. There is no check to ensure that the 

value of GLB.BALANCE is 0 (zero). 

COPY.FROM Ispecs 

On host based LINC system, you must enter BEGIN.EDIT and END.EDIT to define logic. In 

LDA, you enter logic in a different section. This makes writing COPY.FROM update 

screens easier and less error-prone. 

Overlapping fields 

For LINC Generate, overlapping fields are truncated, although overlapping fields are not 

allowed if a double byte character set is used, or if the session language is Kanji. 

LDA has a Business Segment option to determine whether or not overlapping fields are 

allowed. By default, LDA treats overlapping fields in the same way as LINC Generate. If the 

Business Segment option is reset, LDA does not allow any field overlaps. 

v E-5

Data Item Differences 


This subsection outlines data item differences between LDA Development and LINC 

Generate. Included are details of Global Setup Data items, Setup Data items, and System 

Data items. 

Long names 

LDA allows the use of long data names (including Kanji) up to 30 characters in length. The 

host development environment does not have this flexibility. 

Maintenance of Setup and Global Setup Data Items 

For LDA Development, Setup Data items cannot be defined in LDL logic as they can be in 

LINC generate. Therefore, it is not possible to include part of the definition of Group Setup 

Data items by using an Insertable Global Logic. If you transfer a host LINC Specification 

into LDA that uses this method to define Setup Data items, you will receive unexpected 

results. See also "Initialization of Setup Data items". 

LDA sorts the Global Setup Data item lists unless the Global Setup Data item is defined 

within a group. Consequently, Specifications loaded from the host will likely have their 

Global Setup Data item lists displayed in a different order within LDA. 

Data arrays 

Component data arrays are not implemented in LDA. 

Data item, Setup Data item, and Global Setup Data item lengths 

Differences in the maximum lengths of various types of data items, Setup Data items, and 

Global Setup Data items are listed in the following table. 

Dictionary maintenance 

Item LDA LINC 


Signed items 17 18 

Report Numeric item with decimals 17 18 

For LINC Generate, Dictionary Maintenance uses a commit phase to handle changes to the 

Dictionary. 

For LDA Development, maintenance of the Dictionary is more flexible, but also requires 

more care, as there is no commit phase. For example, it is possible for one user to access a 

dictionary item while another is modifying it. Stringent project practices are required to 

control changes to the Dictionary. 

E-6 v

Display items 


In LDA, there is no limit to the number of Display items that may appear in a Report. 

Initialization of Setup Data items 

For LINC Generate, Setup Data items are initialized in logic where they are defined. 

For LDA Run Time, this initialization is not performed, as Setup Data items are not defined 

in logic. This is particularly important to consider when you are creating COPY.FROM 

Ispecs in LDA, as Setup Data items are only initialized automatically in the first copy. 

Keywords 

The keyword function in LDA is performed by Automaint Profiles in Multiple Ordinate 

Memo Components, which are easier to program and offers a more flexible range of 

functions. 

Numeric items in Setup Data and Global Setup Data arrays 

For LINC Generate, numeric items in Setup Data and Global Setup Data arrays are 

computation (usage comp). 

For LDA, these items are display items. 

For example, you declare an alphanumeric data item to contain an array of ten numeric 

items each of 10 digits. For LINC Generate this data item requires 50 bytes, while in LDA 

the item requires 100 bytes. 

v E-7

Data Attribute Differences 


This subsection outlines Data Attribute differences between LDA and LINC Generate. 

Attributes not implemented 

The Data Attributes in the following table are not implemented in LDA Run Time. 

Attribute Attribute Attribute 

BCD BIG BINARY 

DIM LEFTBAR MEMO 

NO.LEFTFILL OUTPUT.CONTROL PITCH 

RIGHTBAR UNDERSCORE UPPERSCORE 

BLINK 

The BLINK attribute is maintained in the LCIF file, but is not displayed in LDA. 

BRIGHT 

For LINC Generate, these attributes remain in effect until the next RESET character. For 

LDA, these attributes remain in effect until the end of the current data item or Display item. 

CLEAR 

For LDA Development, you use a dialog box to clear attributes. 

CLEAR.WHEN 

For LDA, an attribute CLEARWHEN in the LINC.INI file controls the way in which 

CLEAR.WHEN is implemented. This is in addition to system and field options. 

DECIMALS 

The maximum decimals are as follows: 

RESET 

LDA LINC Generate 

Unsigned 17 decimals 18 decimals 

Signed 16 decimals 17 decimals 

Attributes are automatically reset at the end of the field. 

E-8 v

REVERSE 


For LINC Generate, this attribute remains in effect until the next RESET character. For 

LDA Development, this attribute remains in effect until the end of the current data item or 

Display item. For LDA Development, this attribute is ignored in Reports. 

v E-9

Profile Differences 

Profile Differences 

This subsection outlines Profile differences between LDA and LINC Generate. 

Creating or adding Profiles 

For LINC Generate, there is a screen (Profile Options screen) followed by the LINC Editor, 

in which you define the Profile. The relationship between the Profile and the Ispecs it is 

"over" is built into your code. 

For LDA Development, Profiles are created using a dialog box. Each "over" relationship 

between a Profile and an Ispec is specified as a separate step using the Profile list matrix. 

Length of Profile Ordinates 

For OS 2200 based LINC Systems, the combined maximum length of all Profile Ordinates is 

157 characters (including 8 chars for GLB.DTIME). 

For LDA, the total length is 512 bytes. 

Profile collating sequence 

The collating sequence for all architectures including LDA is ASCII, with the exception of 

the LINC for MCP-based systems. Therefore, when you are testing MCP targeted systems, 

this can lead to differences when returning data based on ordinate values at runtime. 

Profile data 

This facility is not implemented in LDA. 

Data Invocation 

Data invocation is not implemented in LDA. 

KEYONLY access via Profile 

KEYONLY access via Profile is not supported in LDA. 

Profile options 

The Security level Profile option is not implemented in LDA Development. 

E-10 v

Generation and Validation Differences 

Generation and Validation Differences 

This subsection outlines differences in the generation process of LINC Generate and the 

validation process for LDA Development. 

Generation 

For LDA Development there is a direct generate function for NT LINC only. 

Development 

Additional validation is sometimes required on input, as compared with the host LINC 

development environment. For example, a Fireup Ispec must exist before it can be added 

to the options of a Business Segment. (For LINC Generate, such an Ispec need not exist 

before being named on the Primary Specification Options screen.) 

Logic Status 

For LINC Generate, the need compile flag (displayed on inquiry screens) indicates that 

logic has changed. For LDA Development, the logic status list indicates that logic has 

changed. 

Validating logic 

For LINC Generate, the contents of the screen in the LINC Editor are validated (unless a 

range is specified). Changes to logic are stored immediately. 

For LDA Development, you choose when logic is to be validated. Validation is performed 

on an entire unit (for example, Pre-Screen, Pre-LINC, and Frame logic). Any changes 

require that the entire section is revalidated. You can choose whether or not to save your 

changes. 

v E-11

Logic Differences 


This subsection outlines general LINC logic command differences between LDA and LINC 


Commands implemented differently for LDA 

The logic commands in the following table are partially implemented in LDA Run Time, or 

are implemented in a different way from host LINC systems. In some cases, different host 

LINC systems implement the logic commands differently from each other and LDA. To see 

how an individual logic command is implemented, see the LINC Programming Reference 

Manual or LDA online help. 

Command Comment 

ACCEPT; Only one form implemented. Alternate form produces syntax 

error. 

ADHOC.MODE; Recalls named or current Ispec only. 

ADVANCE; CHANNEL; command option ignored. 

ATTACH; No upper limit on size of item created. 

ATTACH&SPACE; No upper limit on size of item created. 

AUTO.ENTRY; EXTERNAL; command option ignored. 

AUTO; WRITE External Automatic Entries not implemented. GLB.STATUS 

returns NODB in LDA Run Time. 

AUTO; WRITE&CLEAR See AUTO; WRITE. 

COMPUTE; The maximum number of operators and operands varies. 

CRITICAL.POINT; 

CURSOR; GLB.EOP; command option ignored in LDA Run Time. When 

used in conjunction with the MESSAGE; ERROR command and 

there are multiple lines of error messages, the cursor is 

positioned at the field specified by the CURSOR; command. 

DETERMINE; commands On OS 2200, UNIX and NT based LINC systems, two nested 

DETERMINEs can refer to the same index. This is not possible 

on an MCP based LINC system. 

The Target Host option on the Business Segment, or the 

TargetHost LINC.INI parameter (if more than one host type is 

specified for Target Host), determines the host type thatLDA 

Run Time will emulate. This in turn defines the behavior in 

regard to nested DETERMINEs using the same profile. 

DISCOUNT.CASH; The LENGTH and DECIMAL characteristics may vary. 

DIVIDE; The GLB.STATUS value is checked differently. 

continued 

E-12 v

continued 

Command Comment 


EXTRACT; PACKED BINARY and TAPE options not implemented, Report 

field Extract path determines location of Extract files. 

GLB.STATUS; Use GS; abbreviation. GLB.STATUS; is interpreted as the 

System Data item, and may produce a syntax error. 

INSERT; May not use Macro Global Logics (modular generation not 

implemented). 

LOWER.CASE; OS 2200 based LINC systems use only the US English ASCII 

character set. 

MATCH; End of file is handled differently in OS 2200 host based LINC 

systems. 

MESSAGE; Message display varies between LDA and different hosts. 

MOVE; See notes following the table. 

MOVE.ARRAY; MOVE.ARRAY for EDIT; K data items is only supported on OS 

2200 based LINC systems. 

MOVE.AUTO; External Automatic Entries not implemented. 

RECALL; See notes following the table. 

RUN; Output can be to hard copy only. 

SECURE; Some differences can be expected in locking in UNIX, NT, and 

OS 2200 host based LINC systems, due to the underlying 

relational databases. 

SEND.MESSAGE; Destination station is ignored, and the message is displayed 

immediately on the Status Line (or in the message window for 

Reports). 

SET.TITLE; File name length varies on different host LINC systems. 

SLEEP; Implementations differ on LDA, OS 2200 and UNIX host based 

LINC systems. 

START; Starts a program or .BAT file. 

SWITCH.TO; Use of the INHERIT; command option is ignored. 

UPPER.CASE; OS 2200 based LINC systems use only the US English ASCII 

character set. 

WAKE.UP; Implementations vary on the different host based LINC systems. 

v E-13


Commands not implemented for LDA 

The logic commands in the following table are ignored if executed in LDA Run Time. 

Command Command Command 

ACCESS.EXT; BEGIN.EDIT; END.EDIT; 

END.USE; EXCLUSIVE.USE; ROC.MODE; 

SEND.PRINT; STN.INFO; TRACE; 

MULTI; PAGE; SET.DB; 

KEYONLY; 

COMPUTE.FROM is not implemented in LDA Development or in LDA Run Time. 

Data invocation 

For LDA, the concept of data invocation does not apply. 

Database access 

For LINC Deployment, the whole LINC Database is "opened". 

For LDA Run Time, individual database files are opened. This is a D-ISAM restriction. 

There is a limit of 128 files in LDA. that can be opened by an Ispec or Report. 

Note: Reading a Profile and either adding records using AUTO; commands, or 

updating records using FLAG; commands opens two files (not one). 

Edit logic for COPY.FROM Ispecs 

For LINC Generate, edit logic is defined by using BEGIN.EDIT; and END.EDIT; logic 

commands. 

For LDA Development, Edit logic is a separate logic type (in addition to Pre-Screen, 

Pre-LINC, and Main logic). 

MOVE; Command 

For LINC Generate, an alphanumeric data item of length 24 or greater cannot be moved to 

a numeric or signed data item. For LDA, this restriction only applies when the source of 

the MOVE; (or AUTO;) command is a System Data item. 

HUB Capabilities 

This facility is not implemented in LDA Run Time. 

E-14 v

OLTP capabilities 


This facility is not supported in LDA Run Time. However, OLTP View Ispecs can be created 

and maintained in LDA Development. 

RECALL; commands in COPY.FROM Ispecs 

For LINC Generate, a RECALL; command is required for every copy of a COPY.FROM 

Ispec, or at least when GLB.COPY is equal to 1. For example, if a RECALL; command is 

executed in copy 3, only those data values from copy 3 onwards will be displayed. For 

LDA, one RECALL; command is sufficient for all copies to be displayed. 

Relationships between LINC objects 

For LDA Development, it is a general rule that when one object refers to another, then the 

object being referenced must exist when the reference is entered. Automaint Profiles for 

Memo Components are created automatically by LDA Development if the Profile name is 

specified when the Memo Component is created. 

When you create a new Business Segment, you cannot enter a Fireup Ispec name or GSD 

work area name until you have created these items. 

v E-15

System Data Item Differences 


This subsection outlines general System Data item differences between LDA and LINC 

Generate. See your LINC Programming Reference Manual for full details. 

Usercode and station name 

For LDA, usercode and station are synonymous. GLB.STATION is derived from the value 

held in Computername in the Windows NT registry, or from the value of the Usercode 

entered when signing on, if Security is enabled. 

This may cause problems if there is logic that tests the value of GLB.STATION. However, 

you can alter the value of GLB.STATION when you are using the LDA Debugger. 

System Data items implemented differently for LDA 

System Data items in the following table are implemented differently for LDA. 

System Data Item Comment 

GLB.DEVICE Can be used for Shadow Reports, in the form GLB.DEVICEx, 

where x is the one-character Shadow Report designator 

GLB.FORMDEPTH Defaults to 66 lines. 

GLB.FORMID No output control mechanism. 

GLB.INITSTN Initialized and set to GLB.STN at Report startup, using a 

parameter record in the database keyed on the user id. Starting 

with the -c option will initialize this with ’BATCH’ when calling a 

LINC subroutine or coroutine, or when running a report from 

startup global logic. 

GLB.MACHINE This is determined by the Target Host option on the Business 

Segment options dialog box. 

GLB.NOFORM No Automatic entry to NOF. 

GLB.PARAM Used to pass information to Reports. For LDA, its length is 

assumed to be greater than 24. 

GLB.PREVISPEC Ignored for LDA Run Time. 

GLB.SOURCE Defaults to T. Ignored for LDA Run Time. 

GLB.STALANG Read only in LDA Run Time; set by value in GLB.LANGUAGE. 

GLB.STATION See GLB.STN. 

GLB.STN For Ispecs, set to user id. For Reports, the value must be set 

by the Report to indicate the output device. 

GLB.TITLE See GLB.FORMID 

continued 

E-16 v

continued 

System Data Item Comment 

GLB.USERCODE Defaults to user id. 


GLB.WORK For LDA, its length is assumed to be greater than 24. 

LAST-LINE No REPEAT.FROM Ispecs. 

System Data items not implemented for LDA 

The System Data items in the following table are not used by LDA Run Time. Their values 

are set to zero or spaces, and are ignored thereafter. Logic that uses the value of these 

items cannot be tested in LDA Run Time, unless you use the LDA Debugger to assign 

appropriate values to them. 

Item Item Item 

GLB.ALTUSER GLB.ASCPRT GLB.ASCPRTHOST 

GLB.BACKUP GLB.BALANCE GLB.CHARGECODE 

GLB.DBG- items GLB.DESTENV GLB.DESTHOST 

GLB.DESTINATION GLB.DESTNOFORM GLB.DLRECOVER 

GLB.EXNAME GLB.EXTEXT GLB.EXTDB 

GLB.EXTDBSTATUS GLB.FILEINFO GLB.FORMID 

GLB.HTIMEOUT GLB.HUBSTATUS GLB.HUBTIMEOUT 

GLB.LINEUP GLB.LINEUPNAME GLB.NUMCOPIES 

GLB.ORIGINENV GLB.ORIGINISPEC GLB.ORIGINXNID 

GLB.PITCH GLB.PRINTAT GLB.PRINTBANNER 

GGLB.PRIV GLB.PRINTHOST GLB.PRIORITY 

GLB.REPLANG GLB.REPGENDATE GLB.REPGENTIME 

GLB.REPUNIQUE GLB.REPVERSION GLB.SAVEDAYS 

GLB.SECONDARY GLB.SELFENV GLB.SELFXNID 

GLB.STNHOST GLB.SUBSYS GLB.SYSGENDATE 

GLB.SYSGENTIME GLB.SYSVERSION GLB.TRANSTATE 

GLB.USER GLB.VERSIONID TODAYS-DATE-NUM 

TODAYS-DAY TODAYS-MONTH TODAYS-MONTH-NUM 

continued 

v E-17


continued 

TODAYS-YEAR 

Item Item Item 

E-18 v

Global Logic Differences 

Global Logic Differences 

This subsection outlines differences in Global Logics between LDA and LINC Generate. 

Fields not implemented 

The LINC Security level field is not implemented in LDA. 

STARTUP and CLOSEDOWN 

For LDA Run Time, these System Global Logics are not automatically invoked for a 

session open or close. You must invoke them manually. This leads to inherent differences 

in the implementation of the SWITCH.TO; LINC logic command. 

STARTUP logic for a business segment will be invoked if you use the Run System Logic 

command on the LINC menu of LDA Run Time. It is also possible to specify -s in the LDA 

Run Time command line, but only if a Business Segment name (segment) is also included, 

for example: 

 

The parameters must be entered in this order. 

If your system has CLOSEDOWN logic, you must remember to invoke it with the Run 

System Logic command on the LDA Run Time LINC menu. 

v E-19

Run Time Testing Differences 

Run Time Testing Differences 

This subsection outlines differences between testing in LDA Run Time and host LINC. 

Character-mode screens 

Character-mode screens (with, for example, underline and bold) are supported in LDA Run 

Time, but not in a form compatible with LINC Deployment. 

Database reorganization 

For LDA Run Time, logical reorganization enables you to proceed with testing without 

performing a physical reorganization. You would only use this facility to test Ispec logic 

changes if another programmer has altered a different part of the database. With logical 

reorganization, you cannot always write to the altered structures, and you therefore may 

not be able to read back the record you have written. 

DEBUG traces 

This feature is available for UNIX, NT, and OS 2200 based LINC Systems. It is not available 

for MCP based LINC Systems or for LDA Run Time. 

Debugging 

For MCP based and OS 2200 based LINC Systems, use the LITE product. Contact your 

Unisys representative for details. For LDA Run Time, use the LDA Debugger. 

Report tracing 

This feature is not implemented in LDA Run Time. 

Transmitting fields 

Host LINC Systems offer the choice of full or partial screen transmit. With partial screen 

transmit, fields values up to the cursor position are transmitted. 

For LDA Run Time, all Usage Input fields are transmitted regardless of the cursor position. 

If you do not want to transmit the value of such a field, you must remove the value in the 

field. In addition, there is no equivalent of the terminal programming available on TD830 or 

T27 terminals. 

Function key support 

OS 2200 based hosts allow for the use of function keys. LDA Run Time will emulate a 

number of function keys, but not all the function keys supported. 


Output Control Codes are not implemented in LDA Run Time. However, if this data is 

transferred to LDA Development from the host it will be preserved so that it can be 

transferred back. 

E-20 v

Glossary 

A 

access class 

For LINC Ad Hoc Inquiry, a particular type of user access to queries, defined by a letter (A 

through Z) or an asterisk (*, for unrestricted access). Also called query class. 

Action line 

A field that appears on most screens in LINC Generate, enabling fast-track navigation to 

required functions. Also referred to as the Action field. 

Ad Hoc Inquiry 

See LINC Ad Hoc Inquiry. 

Automaint Profile 

The Profile of a Multiple Ordinate Memo Component that provides automatic access to the 

records of that Component. See Multiple Ordinate Memo Component, Profile. 

Automatic Entry 

(1) A facility that enables an Ispec to create a record in another Ispec. (2) A facility that 

enables an Ispec to modify an existing record in a Standard Component, Table Component, 

or Multiple Ordinate Memo Component. (3) Not applicable to Copy.From Ispecs. (4) See 

also Automatic Entry buffer, external Automatic Entry, internal Automatic Entry, HUB. 

Automatic Entry buffer 

An area in memory used by the Automatic Entry facility. See Automatic Entry. 

Automatic Lookup 

A process where a Component record is automatically read into memory from the 

database. 

v Glossary-1

Glossary 

B 

banner 

A system-generated page that prints at the start of a Report and provides control 

information about that Report. 

base year 

The year upon which the DATE.CONVERT; command bases relative day numbers. The 

year is defined using the Primary Database Options screen and may be accessed through 

the System Data item GLB.BASE. See relative day number. 

Buildable LINCIIDIR 

The LINC installation directory is defined by the environment variable LINCIIDIR. A 

LINCIIDIR that contains the LINC object packages necessary to build LINC executables 

using object packaging is a buildable LINCIIDIR. A buildable LINCIIDIR is necessary to use 

object packaging to maintain your LINC environment 

Bulk Option screens 

A group of screens in LINC Generate that enable options for several Ispecs, Reports, 

Profiles, or Global Logics to be entered together. 

C 

Change Control 

A method for tracking changes to LINC Specifications in LINC Generate. 


A alphanumeric value used to identify a single user or user terminal for change control 

purposes. Applies when the Change Identification option is selected for that LINC 

Specification. Contrast with Patch identifier. 

class 

See access class, security class. 

Column name 

For LINC Ad Hoc Inquiry, an SQL term equivalent to data item. 

Component 

(1) A business resource such as a customer, product or vendor. (2) A store of static data 

about a business resource. (3) Consists of a screen layout and associated logic (Pre-Screen 

logic, Pre-LINC logic, and Main logic). (4) Together with Events, Components form the 

fundamental building blocks of a LINC System. (5) See also Ispec, Standard Component, 

Table Component, Memo Component, Multiple Ordinate Memo Component. 

Component Profile 

For LINC Ad Hoc Inquiry, a Profile over one Component. (2) Contrast with Event Profile. 

Glossary-2 v

Glossary 

Component record 

For LINC Ad Hoc Inquiry, an individual database record for a Component. Equivalent in 

SQL terminology to a row. 

COMUS 

For OS 2200 based LINC Systems, a product used to build LINC Deployment before 

installation (see SOLAR). 

Copy.From Ispec 

An Ispec with a screen that has a number of identical recurring lines. Transmission of the 

whole screen produces a separate record in the database for each completed line. See also 

Ispec. 

Critical Point 

(1) A procedure used within a LINC Report to aid in recovery following a system failure. 

(2) Created by using the CRITICAL.POINT; LINC Logic command. 

D 

DAD 

See Data Display. 

Data Attribute 

An attribute of a data item. For example, LENGTH, EDIT, BRIGHT. 

Data Command 

A command that identifies or creates a data item used in a screen layout, LINC Report, or 

logic. 

Data Display (DAD) 

(1) Optional descriptive text for a data item. Used in status messages in place of the name 

of the data item. (2) Defined using the DATA.DISPLAY Data Attribute. 

Data item 

Part of a LINC Specification defined by using the DATA; command in LINC Painter. Used 

to enter, store and display data. 

data item 

The collective term for the variables used to enter, manipulate, store, and display data 

(Data items, Ordinates, Setup Data items, and so on). 

database 

See LINC Database. 

v Glossary-3

Glossary 

Database Management Utility (DMU) 

(1) A LINC Utility that enables you to maintain your LINC Database. (2) Use to perform 

such tasks as changing the amount of disk space allocated to database structures, initiate a 

full or partial database reorganizations (for MCP based LINC Systems), and creating 

ORACLE SIDs and Griffin Universes (for LINC Systems based on the UNIX operating 

system). (3) See also Griffin Database Management Utility (GMU). 

Development System 

See LINC Development and LINC Generate. 

Direct Component 

A Component type that uses a key for direct access to the dataset, saving on the number of 

Input/Output operations. It has a single numeric Ordinate with a maximum of 8 digits. See 

Component. 

Direct Report 

(1) A specific type of Report that uses the LINC Report Output Control System (ROC), and 

which sends output directly to an output device and not to the ROC database. (2) See also 

LINC Report Output Control System. (3) Contrast with Standard Report. 

Display item 

A string of descriptive information displayed on an Ispec screen layout or Report Frame, 

primarily used to inform the user which data items are which. 

DMU 

E 

Editor 

EIF 

See Database Management Utility. 

See LINC Editor. 

Engineering Interim Fixes (EIFs) are used to distribute new features, fixes, customer 

requests and newly validated versions of support software. 

Environmental Options screens 

Screens in LINC Generate that enable you to define options for your LINC Specification 

that apply to the generation on a particular host type. 

Event 

(1) An activity performed by an organization, for example a sale, purchase, or payment. (2) 

A store of data about an activity performed. (3) Consists of a screen layout and associated 

logic (Pre-Screen logic, Pre-LINC logic, and Main logic). (4) Together with Components, 

Events form the fundamental building blocks of a LINC System. (5) See also Ispec. 

Glossary-4 v

Event file 

For LINC Ad Hoc Inquiry, the file containing the Event records. 

Glossary 

Event Profile 

For LINC Ad Hoc Inquiry, a Profile over one or more Events. Contrast with Component 

Profile. 

Event record 

For LINC Ad Hoc Inquiry, an individual database record for an Event. Equivalent in SQL 

terminology to a row. 

Executables 

Executables are one of two methods of distributing LINC to customers. They are the 

compiled set of LINC files which are ready to install and run. Contrast this with Objects. 

external Automatic Entry 

An Automatic Entry to or from an external source, such as another LINC System. See 

Automatic Entry, HUB. Contrast with internal Automatic Entry. 

Extract file 

A non-database (text) file created or read by a LINC Report. 

F 

Fireup Ispec 

A particular Ispec that is displayed on your terminal when you sign on to a LINC System. 

G 


A facility that enables a non-LINC program to initiate transactions into a LINC Information 

System. 

Generate Group 

A specified group of Reports that can be generated together. 

Generate Set 

A named set of values for generating a particular LINC System from a LINC Specification; 

for example, for a particular host type. 

GLI 

See Generalized LINC Interface. 

v Glossary-5

Glossary 

Global Data Dictionary 

(1) A data dictionary that controls the use of data items over all LINC Specifications within 

the same LINC Generate. (2) Part of GLOBAL Specification. (3) See also LINC Data 

Dictionary, Local Data Dictionary. 

Global Logic 

(1) Part of a LINC Specification that can be reused in other parts of your LINC 

Specification. (2) Inserted into Ispecs, Reports, or Global Logics by using the INSERT; 

logic command. (3) See Insertable Global Logic, Performable Global Logic. 

Global Setup Data item 

A Setup Data item that can be used by any Ispec or Report logic within a LINC 

Specification. See Setup Data item, Group Global Setup Data item. 

GMU 

See Griffin Database Management Utility. 

Griffin Database Management Utility (GMU) 

The equivalent of the Database Management Utility (DMU) for Griffin. 

Griffin 

Database Management System used as the underlying database software for LINC Systems 

based on the UNIX operating system and LINC Generate. Griffin is produced by Unisys 

Corporation. See also ORACLE. 

Griffin Universe 

A Griffin term for a logical storage area that may contain one or more LINC Databases. 

Equivalent of ORACLE SID. See also Tablespace. 

Group Global Setup Data item 

A Global Setup Data item that is a concatenation of a number of other Global Setup Data 

items. See Global Setup Data item. 

group query 

For LINC Ad Hoc Inquiry, an SQL format query whose output lines are for groups of 

related records (rather than individual records). The group is defined by including a 

GROUP BY clause, or by including group functions (such as MAX, MIN, SUM, and AVG) in 

the select list. 

Group Setup Data item 

A Setup Data item that is a concatenation of a number of other Setup Data items. See Setup 

Data Item. 

Glossary-6 v

H 

Glossary 

highlighting attribute 

An attribute of a data item or Display item that affects its appearance when displayed on a 

screen or printed in a LINC Report. For example, BRIGHT or REVERSE. 

Home position 

Top left corner of the screen. Often used as the position from which commands are 

entered. 

Home screen 

For LINC Ad Hoc Inquiry, the base screen from which the main functions are chosen. 

host list 

(1) The list of valid host types for which LINC Generate can perform reserved word 

checking and generation of LINC Systems. (2) The initial list is specified on installation. (3) 

Can be changed in the GLOBAL Specification, using the Supervisor screen. 

HUB Background Run 

For OS 2200 LINC Systems, a background run that processes external Automatic Entries. 

There is one LINC Background Run for each LINC Deployment. See also HUB. 

HUB 

I 

ICP 

The facility that controls external Automatic Entries between LINC Systems. See 

Automatic Entry, external Automatic Entry. 

See Initial Control Program (for OS 2200 based LINC Systems) and Ispec Control Program 

(for LINC Systems based on the UNIX operating system). 

Initial Control Program (ICP) 

The program that controls the generated Ispec subprograms in OS 2200 based LINC 

Systems. Contrast with Update Program (for MCP based LINC Systems) and Ispec Control 

Program (for LINC Systems based on the UNIX operating system). 

Insertable Global Logic 

A sequence of business rules (logic) and a screen layout that can be copied into any 

number of Ispecs and LINC Reports. Contrast with Performable Global Logic. 

interdatabase access 

The accessing of the database of an OS 2200 based LINC System by another OS 2200 based 

LINC System. 

v Glossary-7

Glossary 

internal Automatic Entry 

An Automatic Entry from within the same LINC System. See Automatic Entry. Contrast 

with external Automatic Entry. 

interrogation point 

For LINC Ad Hoc Inquiry, a regular interval during query execution when the status of that 

query is written to the database. 

Ispec 

(1) A collective term for Components and Events. (2) A contraction of the term Interface 

Specification. (3)See also Component, Event. 

Ispec Control Program (ICP) 

The program that controls the generated Ispec subprograms in LINC Systems based on the 

UNIX operating system. Contrast with Update Program (for MCP based LINC Systems) 

and Initial Control Program (for OS 2200 based LINC Systems). 

K 

Keyword 

A data item that has multiple data entry fields and display items. See also Keyword Term 

Item, Keyword Term Display. 

Keyword Term Display 

The Display item associated with a Keyword. See Keyword. 

Keyword Term Item 

The data item associated with a Keyword. See Keyword. 

L 

LDA 

See LINC Development. 

LDL Listing Utility 

A facility in LINC Generate used for printing a LINC Specification. 

LCOPY Utility 

(1) A utility that provides a means of backing up, maintaining and controlling LINC 

Specifications, on the same or different machines (and host types). (2) Formerly known as 

LINC Copy. 


A facility used for making inquiries on a LINC Database. 

Glossary-8 v

Glossary 

LINC Administration Guide 

The LINC manual that contains instructions for administering and operating LINC Systems 

on a particular host type. See the front matter for details. 

LINC Background Run 

For OS 2200 LINC Systems, a background run that controls certain functions; for example 

recovery, report handling, and setting up of Common Banks. There is one LINC 

Background Run for each LINC Deployment. 

LINC Data Dictionary 

A collective name for the Local and Global data dictionaries. See Local Data Dictionary, 

Global Data Dictionary. 

LINC Database 

The database created in the generation of a LINC System. Used for storing data. 

LINC Deployment 

(1) A collective term for the software programs required to operate, control and audit a 

LINC System and its LINC Database. (2) Contrast with LINC Generate. (3) Formerly LINC 

Run Time. 

LINC Development 

(1) PC based development tool for creating and maintaining LINC Business Models (LINC 

Specifications). (2) LINC Business Models are transferred to host based LINC Generate for 

generation and deployment in LINC Deployment. (3) Formerly known as LDA III. 

LINC Development Environment 

A collective term for the tools used to design, develop and generate LINC Systems. 

Includes LINC Development, LINC Generate, and LINC utilities. 

LINC Development System 

See LINC Generate. 

LINC Development Test 

Part of LINC Development that enables testing of your LINC Business Model. 

LINC Editor 

A facility for specifying business rules (logic), expressed using LINC Logic commands and 

text. 


(1) The LINC Software used to generate LINC Specifications as LINC Systems for use in 

LINC Deployment. (2) Formerly known as LINC Development. 

LINCIIDIR 

LINCIIDIR is an environment variable specifying the LINC installation directory. 

v Glossary-9

Glossary 

LINC Installation Guide 

The LINC manual that contains instructions for installing and configuring LINC Systems on 

a particular host type. See the front matter for details. 

LINC Interactive Test Environment (LITE) 

(1) Software that enables testing and debugging of LINC Systems. (2) Interacts with LINC 

Generate and LINC Deployment. 

LINC Painter 

A facility of LINC Generate used to define an Ispec screen layout or Report Frame layout. 

LINC Report 

(1) Part of a LINC Specification, generated and used to produce output or to carry out 

specialized batch processing of a LINC Database. (2) Consists of Report Frames and 

Report Main logic, and a number of options that define the operation and output of the 

Report. (3) Many programs in LINC Generate and LINC Utilities are LINC Reports. 


A utility that provides control over the output of a LINC Report. 

LINC Run Time 

See LINC Deployment. 

LINC Security Level 

A value from 0 through 9 that is assigned to a specific user or terminal to restrict access to 

various functions. 

LINC Security Module (LSM) 

A utility which provides security facilities for both LINC Generate and LINC Systems. 

LINC Specification 

(1) The source definition of a LINC System. LINC Specifications are stored within LINC 

Generate. (2) The result of specifying a LINC Business Model using LINC Development. (3) 

The source from which a LINC System is generated. 

LINC System 

The set of programs (and database) generated from a LINC Specification. 

LINC System command 

A command to assist in the operation of a LINC System or LINC Report. Formerly known 

as a colon command. 

LITE 

See LINC Interactive Test Environment. 

Glossary-10 v

Glossary 

local Data Dictionary 

A data dictionary that controls the use of data items within a single LINC Specification. See 

also LINC Data Dictionary, Global Data Dictionary. 

locked query 

For LINC Ad Hoc Inquiry, a query that is not available for editing or running because it is 

currently queued for execution, or its execution has terminated abnormally, or it is being 

edited. 

logically deleted 

A term used to describe the status of an Ispec record that has been deleted from a database 

as far as all processes are concerned, but is physically still present. 

LSM 

See LINC Security Module. 

LSM security 

For LINC Ad Hoc Inquiry, the security imposed by the LINC Security Module (LSM). If in 

effect, user access to queries and the limits associated with queries may be restricted. 

M 

Main Logic 

A section of user-specified Ispec logic that is executed after any Pre-LINC logic and LINC 

automatic editing and validating sequences have been executed. 

MAINT 

(1) A System Data item, stored with each record of every Standard, Table, and Multiple 

Ordinate Memo Component, that indicates whether that record is added, changed or 

deleted. (2) A screen field for every Standard, Table, and Multiple Ordinate Memo 

Component used to indicate the database maintenance action request. 

Maintenance Mode 

A Painter facility that enables an existing Ispec screen layout or Report Frame to be 

modified. 

Memo Component 

A Component type that has no Ordinate, and which is used to store data of a memorandum 

nature. See Component, Multiple Ordinate Memo Component. 

Memo Data 

Memo-type, optional Ispec data that is stored separately to the primary Ispec records to 

assist with the optimization of disk usage. Valid for MCP based LINC Systems only. See 

Ispec. 

v Glossary-11

Glossary 

Menu Assistance 

A LINC Painter facility that provides assistance when painting an Ispec screen layout or 

LINC Report Frame. 

menu format query 

A query created using the various selection screens of LINC Ad Hoc Inquiry. Contrast with 

SQL format query. 

MLA 

Module 

See Multiple Language Mode. 

LINC Specification that is a subset of a Module Master. When generated a Module 

produces a complete LINC System. See also Module Master. 

Module Master 

A complete LINC Specification that contains defined parts (Modules) that can be 

generated as separate LINC Systems. See also Module. 

multiple language facilities 

A collective term for the LINC facilities that enable a LINC System to be translated and 

used in up to fifteen different languages, from a single LINC Specification. 

Multiple Language Mode (MLA) 

An facility in a menu of LINC Generate that enables a language name or number to be 

defined. (2) See multiple language facilities. 

Multiple Ordinate Memo Component 

(1) A Memo Component with one or more Ordinates defined by a specified Profile (that is 

sometimes referred to as its Automaint Profile). (2) Similar to a Standard Component, but 

with multiple Ordinates. (3) See also Component, Standard Component and Automaint 


N 

NOF 

NOFORM 

See NOF. 

(1) A facility for interfacing to and from a LINC System, usually to an non-LINC System and 

terminals. (2) The interface to PowerClient uses NOF. 

Non-Formatted Input/Output (NOF) 

See NOF. 

Glossary-12 v

O 

Glossary 

Object Packaging 

Object packaging allows the creation of LINC executables from supplied LINC object files, 

the installation of LINC, the installation of LINC EIFs, and the maintenance of your LINC 

environment. It also allows the creation of new LINC object and executable packages 

which can include supplied EIFs. Packages can be created for distribution and as backups. 

Objects 

Objects are one of two methods of distributing LINC to customers. They are the set of 

LINC object files which must be built into executables on your site before LINC can be run. 

Objects files are built using Object Packaging. Contrast this with Executables 

Offline interface 

A facility for passing batches of high-volume, non-LINC transactions for a LINC System. 

OLTP 

See Online Transaction Processing. 

On Change Statistical Routine 

A statistical routine (for example, AVERAGE;) that can be performed on a data item as 

part of an ON.CHANGE; LINC Logic command. 

Online Transaction Processing (OLTP) 

A generic method for transferring transactions to other systems. 

ORACLE 

Relational Database Management System used as the underlying database software for 

LINC Systems based on the UNIX operating system. ORACLE is produced by Oracle 

Corporation. See also Griffin. 

ORACLE SID 

An ORACLE term for a logical storage area that may contain one or more LINC Databases. 

Equivalent of Griffin Universe. See also Tablespace. 

Ordinate 

The data item of a Component that acts as the unique identifier of one record from 

another. The access path to individual Component records. 

v Glossary-13

Glossary 

P 

pack 

Painter 

patch 

The location in which part of a LINC System or LINC Database is stored. For a LINC System 

based on the UNIX operating system, a pack is either a Tablespace or a UNIX pathname. 

See LINC Painter. 

A set of changes to a LINC Specification made over a period of time by users signing on to 

LINC Generate under a specific patch identifier value. 

Patch identifier 

A number used to identify and group changes to a LINC Specification by one or more 

users. Applies when the patch identification option is selected for that LINC Specification. 

Contrast with Change identifier. 

Performable Global Logic 

A sequence of business rules (logic) that can be executed by any number of Ispecs and 

LINC Reports. Contrast with Insertable Global Logic. 

Pre-LINC Logic 

A section of user-specified Ispec logic that is executed before the Ispec Main logic is 

executed. 

Pre-Screen Logic 

A section of user-specified Ispec logic that is executed before the screen layout is 

displayed on the terminal. 

Primary Database Options screen 

The screen in LINC Generate for setting basic options and parameters for a LINC System. 

The screen displayed whenever a new LINC Specification is being created. 

Product Menu Utility 

Product Menu is a menu driven utility to access object packaging features. See Object 

Packaging for details of the functions that can be performed with Product Menu. 

Profile 

(1) An index to a specified selection of records. (2) A method of providing access to just 

those records that are required to perform a specific function. (3) A functional view of the 

database. 

Profile Data 

A data item that is physically stored in a Profile as well as in its associated Ispec. See also 


Glossary-14 v

Glossary 

Profile Ordinate 

The data item by which a Profile accesses individual records. A Profile can have several 

Profile Ordinates. See also Profile. 

Q 

query class 

See access class. 

Query Compiler 

For LINC Ad Hoc Inquiry, the part of LINC Ad Hoc Inquiry that validates an entered query 

and transforms it to a standard internal code and format. See also Query transformation. 

Query Front End 

For LINC Ad Hoc Inquiry, the part of LINC Ad Hoc Inquiry that allows a query to be entered. 

Query Optimizer 

The part of LINC Ad Hoc Inquiry that selects the most efficient way to access the LINC 

Database for a query. 

Query Output Handler 

The part of LINC Ad Hoc Inquiry that provides facilities to manipulate query output. 

Query Processor 

The part of LINC Ad Hoc Inquiry that interprets the query code and runs the query against 

the LINC Database. 

Query Processor report 

For LINC Ad Hoc Inquiry, the program that performs the functions of the Query Processor. 

This program is a LINC Report. 

query transformation 

For LINC Ad Hoc Inquiry, the process performed by the Query Compiler to convert a 

validated query into a standard internal form. 

queued query 

For LINC Ad Hoc Inquiry, a query waiting (for resources) to begin execution. 

v Glossary-15

Glossary 

R 

relation name 

For LINC Ad Hoc Inquiry, an SQL term equivalent to a Component, the Event file, or an 

Event Profile. Also called a table . 

relative day number 

A date expressed as the number of days since January 1 of the base year (which is 

accessible through the System Data item GLB.BASE). The relative day number of January 

1 of the base year is zero. See also base year. 

Report 

See LINC Report. 

Report Frame 

(1) Layout that contains display text and data items, and some associated logic that is part 

of a LINC Report. (2) The logic is executed (often to define the data items in the layout) 

and then the layout is included in the Report output. (3) Report Frames are accessed as 

single units from the logic of Report Frame or from Main logic of the Report. 

Report Initiation Program (RIP) 

An MCP based LINC utility that enables you to execute a line printer Report or terminal 

printer Report in batch mode. 

Report Output Control System (ROC) 

See LINC Report Output Control System. 

resource locking 

A facility of LINC Generate that prevents access to parts of a LINC Specification by more 

than one user at a time. 

ROC 

See LINC Report Output Control System. 

ROC Background Run 

For OS 2200 LINC Systems, a background run that identifies Report output requests and 

spools the output to the required print queue. There is one ROC Background Run for each 

LINC Deployment. 

row 

For LINC Ad Hoc Inquiry, an SQL term equivalent to a Component record or an Event 

record. 

Run Time Environment 

See LINC Deployment. 

Glossary-16 v

S 

Screen Build mode 

A Painter facility that is used to specify a new Ispec screen layout. 

Glossary 

search expression 

For LINC Ad Hoc Inquiry, a logical expression used in a search list to define records to be 

included in query output. 

search list 

For LINC Ad Hoc Inquiry, the part of a query that determines whether records will be 

included in the output. 

security access 

For LINC Ad Hoc Inquiry, full access to all queries. 

security class 

For LINC Ad Hoc Inquiry, a type of user access to queries. See access class. 

select list 

For LINC Ad Hoc Inquiry, the part of a query that defines the data items to be included in 

the output. 

Setup Data item 

A data item used in memory only for data manipulation by an Ispec or LINC Report. See 

also Global Setup Data item, Group Setup Data item. 

Shadow Report 

Part of a LINC Report used to produce additional output separate from that produced by 

the primary functions of the Report. 

Sleeping Report 

A Report that, by the use of the SLEEP; LINC Logic command, stops executing for a 

predetermined number of seconds or until reactivated by your LINC System. 

SOLAR 

For OS 2200 LINC Systems, a product used to install LINC Software. 

sort expression 

For LINC Ad Hoc Inquiry, a logical expression used in a sort list to define output sort order. 

sort list 

spooler 

For LINC Ad Hoc Inquiry, the part of a query that defines the order of the output. 

See Terminal Printer Spooler. 

v Glossary-17

Glossary 

SQL format query 

AnSQLqueryenteredinfreeformatinLINCAdHocInquiry.Contrast with menu format 

query. 

Standard Component 

A Component type that requires a single Ordinate. See also Component. 

Standard Report 

A specific type of Report that uses the LINC Report Output Control System, and whose 

output is written to the database. Subsequent use of the output is determined by the user. 

See Report Output Control System. Contrast with Direct Report. 

station 

structure 

(1) General term in LINC for method used to identify users. (2) For LINC Systems based on 

the UNIX operating system, station equates to user name, while for OS 2200 based LINC 

Systems, station equates to userid. 

(1) In LINC Generate, part of a LINC Specification that can be selected (for example, for 

printing, copying, or extraction). (2) For LINC Ad Hoc Inquiry, part of a LINC Database 

that can be the subject of a query. 

structure list 

For LINC Ad Hoc Inquiry, the part of a query that defines the structures to be included. 

One of the following: 

$ Component 

$ Event Profile 

$ All Events 

Supervisor 

A facility of LINC Generate enabling administration-level functions. 

System Data item 

(1) Data item that is automatically part of your LINC Specification. (2) Used for accessing 

or setting parameter or control-type data in LINC logic. (3) Some System Data Items are 

stored automatically in your LINC Database (for example, MAINT). 

Glossary-18 v

T 

table 

Glossary 

For LINC Ad Hoc Inquiry, an SQL term equivalent to a Component, the Event file, or an 

Event Profile. Also called relation name. 

Table Component 

A Component type that is used to store low-volume, frequently accessed data, such as code 

tables. See also Component. 

Tablespace 

Discrete part of an ORACLE SID or Griffin Universe. Tablespaces in the same ORACLE 

SID or Griffin Universe can be stored on different physical devices. 

Teach Screen 

A user-written screen display of information about an Ispec being used within a LINC 

System, intended to provide online help for users at run time. 

Terminal Printer Spooler (TPS) 

An MCP based LINC Utility that enables users to manipulate the output of a LINC Report 

to terminal printers. 

TPS 

Trace 

See Terminal Printer Spooler. 

(1) A facility to monitor the logic of an Ispec or Report in your LINC System. (2) Enabled in 

LINC Generate. (3) Contrast with LINC Interactive Test Environment. 

Translation Screen 

A copy of an Ispec screen that is modified to create a secondary language version. 

U 

Update program 

A generated program that contains the necessary logic for performing Ispec operations in a 

MCP based LINC System. 

Usage Input 

An Ispec attribute that enables a data item to be entered or displayed on the screen, 

accessed by logic, but not stored in the database. 

Usage Input Ispec 

An Event or Memo Component that is not output to the database, and where Data items 

default to Usage Input. (Individual data items can be set to Usage Inquiry.) 

v Glossary-19

Glossary 

Usage Input-Output 

An Ispec attribute that enables a data item to be entered or displayed on the screen, 

accessed by logic, and stored in the database. 

Usage Input-Output Ispec 

Ispec that is both Usage Input and Usage Output. 

Usage Inquiry 

An Ispec attribute that enables a data item displayed on the screen, but not to be entered 

on the screen, nor written to the database. 

Usage Output 

An Ispec attribute that enables a data item to be written to the database and accessed by 

logic, but not entered or displayed on the screen. 

Usage Output Ispec 

An Ispec that is written to the database, but does not have a screen display. 

V 

Validation EIF 

Validation EIFs are a special type of EIF which provide support for newly validated 

versions of LINC support software such as ORACLE, Griffin, COBOL, and Tuxedo. 

value expression 

For LINC Ad Hoc Inquiry, a logical expression used in an SQL format query to define a 

value, and made up of data items, literals, operators, and functions. 

value logic 

Logic associated with a Dictionary item that determines acceptable values for that item. 

version control 

A method for identifying different versions of a LINC System by version number, 

description, and generation date. 

Glossary-20 v

Index 

A 

ACCEPT command 

use in logic, converted, 5-12 

accesscodes 

generated System, 4-5 

ACR field 

CASE Extract, 5-3 

Action field 


Allowedcore field 

new feature, 1-10 


field in CASE Load, 4-5, 4-8, 4-11 

arrays 

in CASE Extract, 5-11 

LDA differences, E-6 

asterisk 


ATTRIBUTE command 

control of Report output, 1-11 

Audit records 

created during CASE Load, 4-7, 4-9, 4-12 

Automatic Entries 

changes to Report usercode, 1-9 


limits on, B-22 

use of connection libraries, 1-8 

B 

batch mode 

LINC Systems based on the UNIX operating 

system running for, 4-16 

MCP Based LINC Systems running for, 4-15 

OS 2200 Based LINC Systems running for, 

4-15 

batch parameter file 

CASE Load, 4-16 

BEGIN.EDIT command 



BLINK 


blocksize 

avoid reorganization, 1-8 

change in calculation of, 1-8 

BRIGHT 


C 

CASE Data Extract Request screen, 1-6, 5-1 

CASE Extract 

arrays in, 5-11 

checking LCIF file, 5-7 

completing a partial, 5-5 

data attributes in, 5-11 

data items in, 5-11 

Dictionary items in, 5-6 

Global Logics in, 5-6 

Global Setup Data items, 5-10 

Ispecs in, 5-6 

Keywords in, 5-11 

LINC Specifications in, 5-1 

LINC syntax conversion in, 5-10 

logic changes, 5-12 

Profiles in, 5-6 

reducing the size of files, 5-7 

Reports in, 5-6 

resetting previous run of, 5-4 

screen layouts in, 5-11 

selecting structures, 5-2, 5-5, 5-6 

Setup Data items in, 5-11 

CASE Load 

batch parameter file, 4-16 

creating Audit records, 4-7, 4-9, 4-12 

description of LCIF files, 4-2 

description of the process, 4-19 

Dictionary items in, 4-23, 4-24 

extracting and loading LCIF files, 4-25 

Generate Set considerations, 4-2 

loading Kanji LCIF files, 4-2 

v Index-1

Index 

partial load process, 4-21, 4-22 

reserved word checking, 4-21 

screen layout handling, 4-21 

CASE Load screen, 1-6 

CCsversion 

migration issues for, 2-4 

CEX (see CASE Extract), 5-1 

change, patch, and audit control 


Change Identification 

host/LDA exchange, 1-6 



change identifiers 


Checker 

check for overlapping moves, 1-6 

Choice field 


CLEAR 


CLEAR.WHEN 


CLOSEDOWN 


COBOL 

limits, B-25 

code 

limits on generated, B-25 

compatibility 

LDA and LINC Generate, 5-7 

compilation 

UNIX features, D-2 

compilation errors 

due to reserved words, A-3 

COMPUTE.FROM command 


configure 

rebuilding Profiles using, 1-13 

restriction lifted on BNA Generates, 1-9 

restriction lifted on Generate Sets, 1-7 

Confirm generates with install? field 


constants 


COPY.FROM Ispec 


COPY.FROM Ispecs 


D 

data arrays 


data attributes 



database 

access to, LDA differences, E-14 

limits on size of, B-24 

logical, LDA differences, E-2 

maximum record lengths in, B-11 

reorganization of in LDA, E-20 

Database Management Utility 


Database Update allowed field 


data invocation 


data items 



lengths of, for LDA, E-6 


DATE.CONVERT command 

enhanced handling of dates, 1-4 

dates 

debugging for (:DDT), 1-5 

enhanced handling of, 1-4 

new century conversions, 1-2 

DC sets GLB.CENTURY field 


debug 

date and time (:DDT), 1-5 

enhancements (:DBG), 1-12 


DEBUG traces 


DECIMALS 


Default Pitch field 


Delete existing Specification 


Designer Workbench 

see PowerClient, 2-11 

DETERMINE commands 

limits for, B-17 

Dictionary 

CASE Load and, 4-5, 4-6, 4-8, 4-9, 4-11 

enhanced enforcement, 1-3 

Index-2 v


maintenance, LDA differences, E-6 

Dictionary items 


in CASE Load, 4-23, 4-24 

differences 

between host and LDA, E-1 

OS 2200 and MCP LINC Systems, C-1 

UNIXandMCPLINCSystems,D-1 



Display item 


Display items 


DMS II 

features for, 1-10, 1-11 

DMU 


dynamically changing recovery method 


E 

Edit logic 


editor 


END.EDIT command 



Enforce db items only field 


Enforce dict field 


equals sign 


Equipment type field 


errors, multiple 


Events 

problems with in CASE Load, 4-20 

examiner files 

compatibility, 1-11 

external Automatic Entries 





Extract files 

size of, 5-7, B-18 


Extract path field 


extract rules 

LCIF file, 4-25 

F 

finding reserved words, A-4 

FTP 

MCP based, 5-8 

Function key support 

LDA Run Timedifferences, E-20 

G 

Index 



Generate Sets 

CASE Load and, 4-2 

restriction lifted on use in Transfer and 

Configure, 1-7 

restriction lifted on use in BNA Generates, 

1-9 

generation 

confirming installation after, 1-12 

improved performance of, 1-3 

LDA differences, E-2, E-11 


migrated LINC System, 2-12 

GLB.CENTURY 

enhanced handling of dates, 1-4 

GLB.DC-CC 


GLB.STATION 


GLB.STATUS command 


GLB.TASK 


GLB.USERCODE 

changes for Reports, 1-9 

GLI 



Global Dictionary 

CASE Load and, 4-5, 4-8, 4-11 

v Index-3

Index 

Global Logics 

CASE Extract of, 5-6 

differences from host, E-19 

ispec limits, B-5 


nesting of, B-6 


Global Setup Data items 


initializing Group items, 1-5 



limits on, B-7, B-17 

Griffin 


UNIX limits, B-10 

UNIX restrictions on Profile names, A-3 

Group Setup Data items 

initializing, 1-5 

UNIX features of, D-2 

H 

highlighting attributes 


Host 

Updating CCsversion for MCP, 2-4 

host LINC 

differences from LDA, E-1 

host types 

reserved words for, A-4 

HUB 


compatibility with previous releases, 1-9 

diagnostics for, 1-9 




HVTIP 

program limits with, B-2 

I 

INITIALIZE command 


inquiry-only users 

extended access for, 1-2 

installation 

over existing installation, 2-5 

after generation, confirming, 1-12 

installing 

using SOLAR, 1-12 

integrity 


Ispec 

COPY.FROM, LDA differences, E-15 

Ispecs 


COPY.FROM, E-5 

limits on, B-9, B-11, B-12 

options for, LDA differences, E-5 

Repeat.From, E-5 

types of, for LDA, E-5 

K 

Kanji 

data in Ad Hoc queries, 1-11 

LCIF files, loading of, 4-2 

keyins 

replaced with console commands, 1-14 

Keywords 




L 

languages 

related limits on, B-23 

LCIF file 

arrays in, 5-11 


checking, 5-7 

data attributes in, 5-11 

data items in, 5-11 

description of, 4-2 

extract and load rules, 4-25 

Global Setup Data items, 5-10 

issues in extracting, 5-7 

Keywords in, 5-11 

LINC syntax conversion in, 5-10 

load process, 4-19 

logic changes, 5-12 

patch and change information, 1-6 

preparing to load Kanji , 4-2 

Profiles in, 5-10 

relationships in, 5-7 

Index-4 v

screen layouts in, 5-11 

Setup Data items in, 5-11 

transferring to LDA, 5-9 

unloading, 5-1 



LCOPY 

compatibility with LINC releases, 2-2 


loading LINC Specifications, 2-2 

migration, 2-5 

LDA 

CASE Load interface to, 4-1 

changes to host in support of, 1-6 

compatibility with LINC Generate, 5-7 

differences from LINC, E-1 

extracting for, 5-1 


LDA Run Time 

differences from LINC Deployment, E-20 

lengths (LINC limits), B-1 

limits 

COBOL, B-25 

in LINC Generate and LINC Deployment, 

B-1 

system software, B-24 


differences from LDA, E-1 



LINC Checker 

check for overlapping moves, 1-6 

LINC Deployment 

differences from LDA Run Time, E-20 

LINC Environment 

maintaining, 1-16 


Allowedcore field, 1-10 

Checker enhancement, 1-6 

compatibility with LDA, 5-7 

Confirm generates with install? field, 1-12 

date handling, 1-4 

Dictionary enforcement in, 1-3 

Enforce db items only field, 1-4 

Enforce dict field, 1-3 

extracting and loading LCIF files, 4-25 

generation performance, 1-3 

inquiry-only access for, 1-2 


MAPPER file header , 1-4 

OS 2200 features, C-3 

Index 

Report usercodes for, 1-9 


restriction lifted on Transfer and Configure, 

1-7 

structure selection in, 1-4 

unloading a LINC Specification for LDA, 4-1 

LINC Modules 


LINC Release 16.3/16R3 

:STO enhancement, 1-15 

ATTRIBUTE command, 1-11 

avoiding unplanned reorganizations, 1-10 

confirming installation after generation, 

1-12 

connection libraries for HUB, 1-8 

date handling, 1-4 

debugging dates (:DDT), 1-5 

debugging enhancements (:DDT), 1-12 

Dictionary enforcement, 1-3 

DMS II features, 1-10, 1-11 

dynamically changing recovery method, 

1-12 

efficiency of storage, 1-13 

five digit mix numbers, handling, 1-11 

general new features, 1-1 

generation performance, 1-3 

GLB.TASK, 1-13 

immediate effect of LSM changes, 1-12 

INITIALIZE command, 1-5 

initializing with MCB before USERPRT, 1-14 

inquiry only user, 1-2 

for LINC Systems based on the UNIX 

operating system, 1-15 

MAPPER file header , 1-4 

for MCP based LINC Systems, 1-7 

migrating to, 2-1 

MOVE command, 1-6 

new century date conversions, 1-2 

new features, 1-1 

Object Packaging, 1-16 

operator keyins, 1-14 

ORACLE disk usage improvements, 1-15 

for OS 2200 based LINC Systems, 1-12 

RDB capabilities, 1-7 

rebuilding Profiles, 1-7, 1-13 

remapping and relinking all reports, 1-14 

Report usercodes, 1-9 


restriction lifted on Transfer and Configure, 

1-7 

SA$ storage area improvement, 1-13 

v Index-5

Index 

SDF format tapes supported, 1-13 

SENDLIST.STATIC command, 1-5 

sort memory, 1-10 

structure selection in LINC Generate , 1-4 

transferring LINC systems, 1-15 

using mixed Kanji data in Ad Hoc queries, 

1-11 



LINC Reports 

UNIX restrictions on names, A-4 

LINC security level field 


LINC Security Module (LSM) 

immediate effect of changes, 1-12 

LINC Specifications 

CASE Extract of, 5-1, 5-3 

description of CASE Load process, 4-19 

generating after migration, 2-12 

loading from LDA, 4-1 

loading using LCOPY, 2-2 

retaining in installation, 2-5 

before unloading for LDA, 5-1 

unloading from LINC Generate for LDA, 4-1, 

5-1 

LINC System 

:STO and runsys changes, 1-15 

debugging (:DBG), 1-12 

debugging dates (:DDT), 1-5 

generating after CASE Load, 4-14 

terminating, 1-15 

LINC System commands 

:DBG, 1-12 

:DDT, 1-5 

:STO, 1-15 




LINC Systems based on the UNIX operating 

system 

additional reserved word considerations, 

A-3 

compilation features, D-2 

Extract file features, D-3 

features of, D-1 

Global Logic features, D-1 

Griffin features, D-4 

Group Setup Data item features, D-2 

highlighting attributes, D-3 

integrity, D-5 

logic features, D-5 

ORACLE features, D-4 

packs for, D-2 

Profile features, D-2 

Report features, D-3 


ROC features, D-3 

stations use of username, D-2 

structure of, D-1 

System Data item features, D-6 

translation features, D-4 

username used for identification, D-2 

video output for Reports, D-3 

LINC System Transfer 


LINC Utilities 


literals 


loading 

LCIF file, 4-25 

locks 

on resources, LDA differences, E-4 

log files 


logic 

ATTRIBUTE command, 1-11 

CASE Extract changes, 5-12 

DATE.CONVERT command, 1-4 

GLB.CENTURY, 1-4 

GLB.DC-CC, 1-4 


INITIALIZE command, 1-5 


limits in Ispecs, B-12 

limits on database commands, B-12, B-17 

line limit in Global Logics, B-5 

line limit in Reports, B-17 

MOVE command, 1-6 


SENDLIST.STATIC command, 1-5 

status of, LDA differences, E-11 


validation of, LDA differences, E-11 

logical databases 


long names 


LOOK.UP commands 

limits for, B-17 

LRU 


Index-6 v

LSM 

immediate effect of changes, 1-12 


M 

Macro Global Logics 


MAPALLREPS, SGS parameter, 1-14 

MAPPER 

increased file header , 1-4 

MCB 

initializing with, before USERPRT, 1-14 

MCP 

avoiding unplanned reorganizations, 1-10 

changes to report usercodes, 1-9 

controlling output using ATTRIBUTE 

command, 1-11 

DMS II features, 1-10, 1-11 

handling five digit mix numbers, 1-11 

HUB Connection Libraries, 1-8 


RDB Capabilities, 1-7 

rebuilding profiles with DMU, 1-7 



specifying sort memory, 1-10 

Updating CCsversion, 2-4 

using mixed Kanji data in Ad Hoc queries, 

1-11 

MCP LINC Systems 


migration, 3-1 

CCsversion and, 2-4 

first generation after, 2-12 

installing over existing installation, 2-5 

LINC Release 16.3/16R3, 2-1 

before LINC II Release 16.1/16R1, 2-2 

procedure, 2-4 

using LCOPY, 2-5 

Windows NT, 2-5 

mix numbers 

five digit, handling, 1-11 

MODELTRIM 

MCP based, 5-8 

OS 2200 based, 5-8 

UNIX, 5-8 

Modules 


Monthly volume field 


MOVE command 

checking for overlapping moves, 1-6 

N 

new features 

see LINC Release 16.3/16R3, 1-1 

see MCP, 1-1 

see OS 2200, 1-1 

see UNIX, 1-1 

NOF 


numeric items 

increased efficiency of storage, 1-13 

Numeric precision, 3-2 

O 

Index 

Object Packaging 

LINC objects and executables, 1-16 

Offline 


OLTP 


On LINC pack field 


operator keyins 


ORACLE 

disk usage improvements under UNIX, 1-15 


UNIX limits, B-10 

UNIX restrictions on Profile names, A-3 

Ordinates 

lengths of, B-4 

or on Pack ids field 


OS 2200 

confirming installation after generation, 

1-12 

console commands replace operator keyins, 

1-14 

debugging enhancements (:DDT), 1-12 

dynamically changing recovery method, 

1-12 


increased numeric item storage efficiency, 

1-13 

v Index-7

Index 


installing using SOLAR, 1-12 


new system data item GLB.TASK, 1-13 

rebuilding Profiles from Ispec tables, 1-13 

remapping and relinking all reports, 1-14 

SA$ storage area improvement, 1-13 

SDF format tapes supported, 1-13 

OS 2200 LINC Systems 

features of, C-1 

LINC Generate features, C-3 

LINC System command features, C-2 

logic features, C-1 

Reports features, C-3 


System Data items features, C-3 

utilities, features of, C-3 

output 

control using ATTRIBUTE command, 1-11 



Output file name field 


overlapping fields (Painter) 


Override LINC Dictionary Item Text and 

Conditions 


P 

packs 


painter 

overlapping fields in, E-5 

Partial CASE Extract screen, 5-5 

partial extract, completing, 5-5 

Partial load 


Partial spec field 


patch extraction and application 


Patch Identification 

host/LDA exchange, 1-6 

patch Identifiers 


Patch number 


PowerClient 

enhanced SENDLIST.STATIC command, 1-5 

migrating LINC Systems using, 2-11 

non-use of, 2-11 

support for, 2-11 

Printer name 

field in CASE Load, 4-12 


CASE Extract of, 5-6, 5-10 



ORACLE and Griffin restrictions, A-4 

rebuilding from Ispec tables, 1-7, 1-13 


UNIX restrictions on names, A-3 

Purge Allowed field 


R 

RDB, extended capability, 1-7 

RECALL command 


recovery 

dynamically changing method of, 1-12 


relationships 

in LCIF file, 5-7 

reorganization 

avoiding, 1-8 



unplanned, avoiding, 1-10 

Repeat.From Ispecs 


report 

tracing, E-20 

Reports 


controlling output using ATTRIBUTE 

command, 1-11 




limits on, B-16, B-17, B-18 

in LINC Generate, usercodes for, 1-9 

options for, LDA differences, E-5 


remapping and relinking, 1-14 

tracing not implemented in LDA, E-3 


Index-8 v

video output for in UNIX, D-3 

Report to 

field in CASE Load, 4-6, 4-12 

report tracing 


reserved words 

checking for LCOPY, A-2 

checking for LDA, A-2 

checking for LINC Generate, A-2 

checking in CASE Load, 4-21 

listing, A-4 

maintaining, A-2 

types of, A-1 

UNIX considerations, A-3, D-3 

reserved words list utility, A-4 

RESET 


Reset previous run field 


resource locks 


restrictions (LINC limits), B-1 

REVERSE 


ROC 



ROC.MODE command 


RP/TP Printer name 

field in CASE Load, 4-7 

runsys 


S 

SA$ storage area, efficiency improvement, 1-13 

screen layouts 


handling in CASE Load, 4-21 

SDF format tapes, support for, 1-13 

security 

batch CASE Load, 4-15 



SENDLIST.STATIC command 

enhancements, 1-5 

Setup Data items 

CASE extract of, 5-11 

initializing Group items, 1-5 

Index 




size (LINC limits), B-1 

SMU 

changing system, database, and window, 1-7 

SOLAR 

installing with, 1-12 

sorting order, B-25 

sort memory 

specifying, 1-10 



STARTUP 


Station name 


stations 

UNIX use of username, D-2 

storage 

increased efficiency of, 1-13 

SA$ area, 1-13 

Structure 

enhanced selection in LINC Generate, 1-4 

of LINC Systems based on the UNIX 

operating system, D-1 

selecting with CASE Extract, 5-5 

supervisor functions 


System binary numerics field 


System Data items 




System Management Utility 

changing system, database, and window, 1-7 

system software 

limits of, B-24 

T 

tape 

SDF format supported, 1-13 

target hosts 


Teach screens 


TODAY System Data item 


v Index-9

Index 

trace view files 


transfer 

restriction lifted BNA Generates, 1-9 


Transferring 

LINC systems as object code, 1-15 

translation 

impact by new feature, 1-3 



transmitting fields 


Type checking rules 


U 

UNIX 

:STO enhancement, 1-15 


Object Packaging, 1-16 

ORACLE disk usage improvements, 1-15 

transferring LINC systems as object code, 

1-15 

unplanned reorganizations 

avoiding, 1-10 

Updates allowed field 


usercodes 


for Reports in LINC Generate, 1-9 

USER interface 


USERPRT 

initializing with MCP, before, 1-14 

utilities 

limits for LCOPY, B-22 

limits on LINC Utilities, B-22 


V 

validation 


Version Control 


Video capable field 


video output for Reports in UNIX, D-3 

W 

Windows NT 

LINC Deployment for, 2-5 

:DBG LINC System command, 1-12 

:DDT LINC System command, 1-5 

:SLA 


Index-10 v

Tape 

Fold Here 

Airmail 

Unisys Australia Pty Ltd 

115-117 Wicks Rd 

North Ryde, NSW 2113 

Australia 

Cut along dashed line 

Do Not Staple 

Please Fold and Fasten 

Attention: ACUS Product Information 

Correct Airmail 

Postage Required 

Tape

Addition Deletion 

Revision Error 

Publication title 

Document number 

Comments: 

Name 

Title 

Address 

City 

Help Us To Help You 

Unisys Corporation is interested in your comments and suggestions regarding this manual. We will 

use them to improve the quality of your Product Information. Please check type of suggestion: 

Company 

Date 

Telephone number 

( ) 

State ZIP code

*-*

Features of LINC Generate - Public Support Login - Unisys

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?