INTEGRATED INFORMATION SUPPORT UNCLSSIFED …Mr. Myron Hurlbut of Industrial Automation Systems...

MD-0192 ON INTEGRATED INFORMATION SUPPORT SYSTEM (1155) VOLUME 6 i/INETNORK TRANSACTION.. (U) GENERAL ELECTRIC CoSCNECTAkDY NY PRODUCTION RESOURCES CONSU.

UNCLSSIFED GREENBERG ET AL. 01 NOY 85 OM-629142900 FIG 12/5 M

smmhhmhhEmhEEEimhohhEEmhhEEI

iii~~~ IL 3 32

*125 1 .

MICROCOPY RESOLUTION TEST CHARTNATIONAL BUREAU OF STANDARDS- 1963-A

AD-A182 058 il LE CO'

AFAL-TR-86-4006Volume VIPart 3

INTEGRATED INFORMATIONSUPPORT SYSTEM (I188)Volume VI - Network Transaction Manager Subsy.-'S tPart 3 - WTH Operator's Manual

General Electric CompanyProduction Resources ConsultingOne River RoadSchenectady. New York 12345

Final Report for Period 22 September 1980 - 31 July 1985

November 1985

Approved for public rele&se; distribution is unlimited.

DTICPREPARED FOR: ELECTE

MATER IALS LABORATORY JL0 2W0AIR FORCE WRIGHT AERONAUTICAL LABORATORIESAIR FORCE SYSTEMS COMMANDWRIWIT-PATTERSON AFB, OR 45433-6533

.87

Unclassifiled

h4Cum'. C" OCLOe Of ?a u 1AE November 1985

a S**?SICuit CAS'*CRE~SPORT DOCUMENTATION PACE '-40 NA16 411S37411isvl WASKIIS

36 81ERIT utv &&SSPCATmOa AuTwOmaTY 3 eeu1Su ,6RTOftw.AABi0TW Of A&POR?

211 09 g" If IA? 101400111%6 AAD400G 0CON# DyL Approved for public release;distribution Is unimituled.

d. IRUWN @6ambi2*?I# ASPORT kulMSEmiJ S. MO1rnIY@B8taO DAG&NIZA&OY4 REPORT mINW RA641

AFVAL-T-86-4005 Vol VI. *part 3

a ONAul Of Pssseamm"Iao ORAOA ION9 W office SYMO1106 Is. INAW 00 WOfate'Af @RGA&AI0t

Geneal lecricComanyAVAL/NaTC

66. A99S11SS fWfP. Some me ZiP cow), T. ADDRESS left. #ae am sip Cowu

A River UeAdsabesecteiy, WT 15345 WAPS. ON 45433-6533

b6 %&Mt Of WUWOSSSf4P~tESOfkNQ Office SYMSOL S PROCU*REMEW? ISITAWMSI 69aftv f.ICAII@sf SAMSI a*RGAwaftilA@S11

Nateriala 2mbotatoryAir Force System Commnd.8 US uuLVAfL TC 7336111-80-C-91 55

Is A*SRIS8 OCI. Soi* we ZIP COO), is SOVORE of 0 DING "Os

P@RAM I ROACY VASIL OAL USI'01

gigit-F&atersou An., Ohio 4S433 60 4110 01-010.00

______________________________ I__Tsai A0ir 7500 62 01

(goo Reverse) ______

1I& PGRIO.AL £UTPI@RBGreenberg. Barry, Strobl. Nary Jae and Cross, Judy

13N, TVPE Of 0SS§RT 136 ToME COVERED WI DATE ON REPORT ~ IS P5 COy'.??$Sa1 Vie-secal Arert a2 tep% 1950 - 51 July 155 65 Ioember 66

W SPPi, eMe TAUYS OTAT WIN The computer sof tware ontained berein are %beoretioal And/or631references that In no vay reflect Air roroei-owned or -developedzCAu Projeict Priority 621conputer sof tware.

g~.COSOOgg ~ II SW&A CI' TS AS viCenme es ao of mon aw eiosaft ft So~t uumha

is LUrsAc? OCemAI enWm Veusepffw an ABft ft SW Awin53Pio

,,,This technical manual provides detailed instructions forrunning IISS. This Includes instructions for bringing up andshutting down the(N*M. a description of NTH error codes. andInstructions for, maintaining XTM tables. - I~~-,.,

toGoS k *SST5IOWA VAIAS 1IW @9 OfUSTRACT a &SITRtac? t5Eokiv C&A"SPISATI59.

%ftC6*gASOP10.Ugt"eYUS 0 SAME as WT 0 TCWa t Unclassified

DO FORM 1473.8 AP 1111"Ot of'S I9 tAt To a OSSOe2.SY __________

SE~~~um'?vD TonsiI6Y5 9 5 P&G~a

11. Title

Integrated Information Support System (IISS)Vol VI - Network Transaction Manager Subsystem-Part 3 - NTM Operator's Nanual

Aeession For

DTIC ?ADUnannounoed 0Justifloatl

A ailability CodesAvall 8MM/ot

l~t Spool8list Spoal

-'1

4i

ON 620142000

1 November 1985

PREFACE

This operator's manual covers the work performed under AirForce Contract F33615-80-C-5155 (ICAM Project 6201). Thiscontract is sponsored by the Materials Laboratory. Air ForceSystems Command, Wright-Patterson Air Force Be. Ohio. It wasadministered under the technical direction of Mr. Gerald C.Shumaker, ICAM Program Manager, Manufacturing Teohol oLyDivision, through Project Manager. Mr. David Judson.The PrimContractor was Production Resources Consulting of the eeralElectric Company, Schenectady. Ne York, under the direction ofMr. Allan Rubenstein. The General rlectric Project Manager wasMr. Myron Hurlbut of Industrial Automation Systems Department.Albany, New York.

Certain work aimed at improving Test Ned Technology hasbeen performed by other contracts with Project 6201 performingintegrating functions. This work consisted of ea mts toTest Bed software and establishment and operation of ,*at ledhardware and communications for developers amd other .ors.Documentation relating to the Test Ded fron all of t-eecontractors and projects have been integrated under Project l01for publication and treatment as an integrated set of documentsThe particular contributors to each document are noted on theReport Documentation Page (DD1473). A listing and descriptionof the entire project documentation system amd how they arerelated is contained in document FTM620100001. Project Overview

The subcontractors and their contributing activities wereas follows:

TASK 4.2

Subcontractors Role

Boeing Military Aircraft ReviewerCompany (BMAC)

D. Appleton Company Responsible for IDEF support,(DACOM) state-of-the-art literature

search

General Dynamics/ Responsible for factory viewFt. Worth function and information

mode 1s

iti

ON 6201420001 November 1985

Subcontractors Role

Illinois Institute of Responsible for factory viewTechnology funot ion research (IITRI)

and information models ofsmall and modium-aise business

North American Rockwell Reviewer

Northrop Corporation Responsible for factory vievfunction and informationmodels

Pritsker and Associates Responsible for IDEF2 support

SofTech Responsible for IDEFO support

TASKS 4.3 - 4.9 (TEST BED)

Subcontractors Role

Boeing Military Aircraft Responsible for consultation onCompany (BMAC) applications of the technology

and on IBM computer technology.

Computer Technology Assisted in the areas ofAssociates (CTA) communications systems, system

design and integrationmethodology, and design of theNetwork Transaction Manager.

Control Data Corporation Responsible for the Common Data(CDC) Model (CDM) implementation and

part of the CDM design (sharedwith DACOM).

D. Appleton Company Responsible for the overall CDM(DACOX) Subystem design integration and

test plan, as well as part ofthe design of the CDM (sharedwith CDC). DACO alsodeveloped the IntegrationMethodology and did the schemamappings for the ApplicationSubsystems.

iv

0N 6201420001 November 1985

Subcontractors Role

Digital Equipment Consulting and support of theCorporation (DEC) performance testing and on DEC

software and computer systemsoperation.

McDonnell Douglas Responsible for the support andAutomation Company enhancements to the Network(HcAuto) Transaction Manager Subsystem

during 1984/1985 period.

On-Line Software Responsible for programming theInternational (OSI) Communications Subsystem on the

IBM and for consulting on theIBM.

Rath and Strong Systems Responsible for assistance inProducts (RSSP) (In 1985 the implementation and use ofbecame McCormack if Dodge) the MRP II package (PIOS) that

they supplied.

SofTech. Inc. Responsible for the design andimplementation of the NetworkTransaction Manager (NT) in1981/1984 period.

Software Performance Responsible for directing theEngineering (SPE) work on performance evaluation

and analysis.

Structural Dynamics Responsible for the UserResearch Corporation Interface and Virtual Terminal(SDRC) Interface Subsystems.

Subcontractors and other prime contractors under otherprojects who have contributed to Test Bed Technology. theircontributing activities and responsible projects are as follows:

Subcontractors Role

General Dynamics/ Responsible forFt. Worth factory view

v

ON 6201420001 November 1985

Contractors ICAN Project Contributing Activities

Boeing Military 1701, 2201, Enhancements for IBMAircraft Company 2202 node use. Technology(BMAC) Transfer to Integrated

Sheet Metal Center(IS#C)

Control Data 1502, 1701 IISS enhancements toCorporation (CDC) Common Data Model

Processor (CDMP)

D. Appleton Company 1502 IISS enhancements to(DACOM) Integration Methodology

General Electric 1502 Operation of the TestBed and communicationsequipment.

Hughes Aircraft 1701 Test Bed enhancementsCompany (HAC)

Structural Dynamics 1502, 1701, IISS enhancements toResearch Corporation 1703 User Interface/Virtual(SDRC) Terminal Interface

(UI/VTI)

Systran 1502 Test Bed enhancements.Operation of Test Bed.

Vi

vi~

ON 8201420001 November 1985

TABLE OF CONTENTS

Page

SECTION 1.0 RUNNING THE ZISS................................ 1-11.1 Location of Runtime Modules................... 1-11.2 Sysgen Parameters............................. 1-11.3 IISS Startup.................................. 1-1

SECTION 2.0 IISS OPERATOR COMMANDS......................... 2-12.1 Introduction.................................. 2-12.2 Shutdown APC.................................. 2-12.3 Start APC..................................... 2-22.4 Shutdown Comm Link........................... 2-22.5 Start Comm Link............................... 2-32.6 Display IISS Status.......................... 2-32.7 Display Active APs........................... 2-32.8 Enable SIGERR Messages....................... 2-42.9 Disable SIGEER Messages...................... 2-42.10 Select Logging Features...................... 2-52.11 Start a New Log File......................... 2-8

SECTION 3.0 SHUTTING DOWN THE IISS......................... 3-1

SECTION 4.0 ERROR CODES...........................4-14.1 MPU Processing Error Cds..........4-14.2 AP Interface Error Codes..................... 4-24.3 Resource Unavailable Error Codes.............. 4-34.4 Table Error Codes............................ 4-34.5 Monitor AP Error Codes....................... 4-4

SECTION 5.0 NTM TABLE MAINTENANCE.......................... 5-15.1 Overview..................................... 5-15.2 Table Descriptions........................... 5-35.3 Monitor AP Internal Table.....................5-115.4 When to Modify a Table....................... 5-115.5 Table Values................................. 5-15

SECTION 6.0 TROUBLESHOOTING SUGGESTIONS.................... 6-1

APPENDIX A NTM LOG UTILITY................................ A-1

APPENDIX B INSTALL ETH UTILITY............................ B-i

APPENDIX C ERRLOG UTILITY................................. C-1

Vii

ON 620142000

1 November 1985

LIST OF SYMBOLS, ABBREVIATIONS. ACRONYMS

AP Application ProcessAPC Application Process ClusterAPI Application Process InterfaceCDRP Common Data Model Request ProcessorCOmm Communications HandlerCPCI Computer Program Configuration ItemDBMS Data Base Management SystemDML Data Manipulation LanguageICAN Integrated Computer Aided ManufacturingIDSS Integrated Decision Support SystemIISS Integrated Information Support SystemIPC Inter Process CommunicationLAN Local Area NetworkICMIM Manufacturing Control Material ManagementMDL Message Definition LanguageMM Message ManagerNO Maintain OperabilityMPU Message Processing UnitNRP Materials Requirements PlanningMSG MessageNTH Netvork Transaction ManagerOS Operating SystemPM Process ManagerQA Quality AssuranceSS System SpecificationUI User InterfaceVAX Trademark of Digital Equipment Corporation: 32

bit minicomputerVMS Trademark of Digital Equipment Corporation: The

VAX OS

ix

.pL. - - -

ON 6201420001 November 1985

SECTION 1

RUNNING THE IISS

1.1 Location of Runtime Modules

In order to run IISS, the NTM executable modules MONITR,NTMRVNPU, NTCDKNPU, NTCOVMPU, NTUIVNPU, and NTTIVNPU must beresident in the directory in which IISS will be run. All of thedata files (for NTM tables, queues, and sysgen parameters) mustalso be in this directory. All executable modules of AP's to berun in the IISS environment must be in directories known to theNTM.

A directory is known to the NTN via an entry in theDirectory Table. This entry contains the two character directoryID (as used in the AP Naming Convention) and the actualdirectory name (not to exceed twelve characters including theperiod).

Finally, the executable module MPUGEN must reside in thedirectory in which the IISS will be run. This allows theoperator to modify the sysgen parameters and run without havingto move files.

1.2 Sys~en Parameters

Prior to running the IISS, and "Instance" must be assignedto the NTM. This Instance ID allows multiple IISS environmentsto run simultaneously. On the VAX, the separate IISS instancesmust run in separate VAX Groups (where a VAX User IdentificationCode (UIC) - (group id, member id]). To assign an instance ID,EPUGEN is run. The MPUGEN menu includes a choice for modifyingthe current IISS Instance.

1.3 IISS Startup

The IISS environment on each host within the IISS system isstarted individually under control of the local host operatingsystem. Once the IISS operator has logged on to the local hostunder the appropriate system directory, the invocation of acommand file will cause the local operating system to load andexecute the monitor AP (Monitor AP is the NTH system componentresponsible for coordinating IISS start up). On the VAX, thecommand file is "IISS" and is executed as follows:

1-1

'^

OM 620142000

1 November 1985

@IISS (return)* * * * *CLEANUP**S**

* S * 8 * BEGINNING IISS START UP * 8 8 8 0

MRV START UP SUCCESSFUL.CDM START UP SUCCESSFUL.UIV START UP SUCCESSFUL.COV START UP SUCCESSFUL.TIV START UP SUCCESSFUL.

' * * * * IISS START UP COMPLETE * 8 * 8 8

888 INTEGRATED INFORMATION SUPPORT SYSTEM *888 NETWORK TRANSACTION MANAGER 888

ENTER OPERATOR COMMAND (OR HELP)

COMM LINK VI IS ACTIVE.

In the above example, CLEANUP is the pre-start up fileinitialization phase in which message logs and queues are"cleaned up" and NTM files are assigned. File Delete Errorsduring cleanup will occur. This may not indicate an error; it ispossible that the particular file was not created during theprevious execution. These error messages may usually beignored.

Once IISS start up has begun. start up status messages aredisplayed to the IISS operator console. These messages indicatewhich IISS components have been successfully initiated and whereerrors have occurred in start up processing. In the aboveexample, all local APC's (MRV, CDX, UIV, COV, TIV) have startedsuccessfully as has the VAX-IBM comm link (VI). If an erroroccurs during the start up of an APC, an error message would bedisplayed. If a Component APC (MRx, CDX, UIx, COx. where x isthe host identifier) fails, the IISS start up would fail and theMonitor AP terminate. The following is an example of such anoccurrence:

MRV START UP SUCCESSFULCDM START UP FAILED: FAIL CODE: 30001TIMEOUT ON WAIT FOR MPU TABLE STATUS REQUESTERROR IN MODULE STRTUP ERROR CODE: 30020COMPONENT APC FAILED AT START UP

1-2

OM 6201420001 November 1985

(return to host'os command level)

If a non-component APC fails, start up continues; the IISScan run without the non-component APC's being active. Thefollowing is an example of this situation:

MRV START UP SUCCESSFUL.CDM START UP SUCCESSFUL.UIV START UP SUCCESSFUL.COV START UP SUCCESSFUL.TlV START UP FAILED: FAIL CODE: MTRO1TIMEOUT ON WAIT FOR TABLE STATUS REQUEST

* S S * * IISS START UP COMPLETE * * * *

COMM LINK VI IS ACTIVE.

The IISS Central Node (VAX) can operate in the IISSenvironment without any Remote Node being active. If, duringIISS start up, any or all of the comm link start up requestsfail, start up processing will continue and normal IISSprocessing will be available to the local host.

MRV START UP SUCCESSFUL.CDM START UP SUCCESSFUL.UIV START UP SUCCESSFUL.COV START UP SUCCESSFUL.TIV START UP SUCCESSFUL.

* * * * * IISS START UP COMPLETE * S * *

VI LINK START FAILED: FAIL CODE 30016

The above situation is currently not applicable to a RemoteNode. The current implementation of the NTM requires RemoteNodes to have an active link to the Central Node to run in theIISS environment. If the above example were on a Remote Node,it would look as follows (Note: the comm link to the Central

" Note is started immediately after the Monitor APC is initiated):

MRI START UP SUCCESSFUL.IV LINK START FAILED; FAIL CODE: 30016ERROR IN MODULE LKTOCN ERROR CODE: 30016COMM LINK FAILED AT START UP

1-3

ON 6201420001 November 1985

SECTION 2

IISS OPERATOR COMMANDS

2.1 Introduction

The NTM currently supports 12 operator commands. They areas follows:

1. Shutdown IISS (SD)2. Shutdown APC (SC)3. Start APC (ST)4. Shutdown Comm Link (LS)5. Start Con Link (SL)6. Cancel IISS Shutdown (CN)7. Display IISS Status (DS)8. Display Active AP's (DA)9. Enable a SIGERR Messages (SE)10. Disable SIGERR Messages (SO)11. Select Logging Features (LG)12. Start New Log File (SN)

"HELP" will display the list of operator commands. Theprocessing of these commands is fairly straightforward."Shutdown IISS" is more complex and will be covered in the

section of this manual on shutting down the IISS (Section 3).Except for the commands "CN" and "DS". the operator is promptedfor additional information - either an APC name or a Link ID.This data is verified and the command is executed. Between thetime the operator enters the requested command data and the timeat which the command processing is complete, the operatorconsole is disabled for further input. Therefore, there may beno overlapping of operator commands. The results of the commandwill be displayed at the console.

2.2 Shutdown APC

This command causes an APC anywhere in the IISS environmentto be shutdown. The operator is prompted for the same of theAPC and the command status is displayed to the operator. Onlynon-component APC's may be shutdown via operator command.

ENTER OPERATOR COMMAND (OR HELP)SC (return)

ENTER APC NAMETIV (return)

2-1

ON 6201420001 November 1985

TIV HAS TERMINATED

Other possible status returns for this oommand are:

- APC NOT IN APC STATUS TABLE- APC IS INACTIVE- NO RESPONSE FROM APC: ASSUMED TERMINATED- INVALID COMMAND FOR COMPONENT APC

2.3 Start APC

This command enables the IlSS operator to start an APC.Currently only non-component APC's on the local host maybe started via operator command. As in the Shutdown APCcommand, the operator is prompted for the name of the APC.

ENTER OPERATOR COMMAND (OR HELP),ST (return)ENTER APC NAME,T1V(return)TIV START UP SUCCESSFUL.

Other possible status returns for this command are:

- APC NOT IN APC STATUS TABLE- APC IS ALREADY ACTIVE- APC START UP FAILED: FAIL CODE: MTRxx

2.4 Shutdown Comm Link

This command is invoked to shutdown the communicationslink to a remote host. The operator is prompted for theid of the link to be shutdown.

ENTER OPERATOR COMMAND (OR HELP),LS(return)ENTER LINK ID)VH(return)COMM LINK VH HAS TERMINATED.


- LINK-ID NOT IN LINK STATUS TABLE- LINK-ID IS INACTIVE- NO RESPONSE FROM LINK ID VH: ASSUMED TERMINATED

2-2

'" .... ,, ' , ' "" W 'q' ', ', V, , " ' ,' j , 1W ,

ON 6201420001 November 1985

2.5 Start Comm Link

This command is invoked to start the communications linkto a remote host. The operator is prompted for the Id ofthe link to be started.

ENTER OPERATOR COMMAND (OR HELP), SL(return)ENTER LINK ID

,VH(return)CONN LINK VH IS ACTIVE


- LINK-ID NOT IN LINK STATUS TABLE- LINK-ID IS ALREADY ACTIVE- LINK-ID LINK START UP FAILED: FAIL CODE KTRxx

2.6 Display IISS Status

This command displays the current status of all IISScomponents.

ENTER OPERATOR COMMAND (OR HELP),DS(return)

HOST VAX IS ACTIVEHOST HL6 IS INACTIVEHOST IBM IS INACTIVE

APC KMR IS ACTIVEAPC UIV IS ACTIVEAPC COV IS ACTIVEAPC CDM IS ACTIVEAPC TDV IS ACTIVEAPC CON IS INACTIVE

LINK VH IS ACTIVELINK VI IS INACTIVELINK IN IS INACTIVE

2.7 Display Active AP's

This command enables the IISS operator to set a list of

2-3

ON 6201420001 November 1985

the active AP's on a particular APC. The operator isprompted for the name of the APC who's active AP's are tobe displayed.

ENTER OPERATOR COMMAND (OR HELP),DA(return)ENTER APC NAMETIV(return)

THE ACTIVE AP'S ON APC ARE AS FOLLOWS:

AP NAME: ap-nameABORT CHARACTERISTICS: ap-abort-characteristicORIGINAL SOURCE: ap-original-source

(repeated for each active ap on the APC)


- APC NOT IN APC STATUS TABLE- APC IS INACTIVE- NO RESPONSE FROM APC: ASSUMED TERMINATED- NO ACTIVE AP'S ON APC

2.8 Enable SIGERR Messages

This command sets the condition that all SIGERR messagesthat arrive at MONITR will be displayed on the Operator'sconsole.

ENTER OPERATOR COMMAND (OR HELP),SE (return),(new prompt indicates SIGERR Messages are enabled)

2.9 Disable SIGERR Messages

This command prevents SIGERR messages from being displayedat the operator's console. As most SIGERR messages arenotifications of internal AP problems, the operator maychoose this option to restrict console displays to NTMerrors only. This mode is the default one. When the IISSstarts up. the displaying of SIGERR messages at theoperator's console is disabled.

ENTER OPERATOR COMMAND (OR HELP))SO (return)

2-4

OM 6201420001 November 1985

,(new prompt indicates that SIGERR messages have been

disab led)

2.10 Select Logging Features (LG)

This command starts a dialog with the operator to selectIISS logging features. At IISS startup, complete loggingis enabled; all IISS messages will be logged at all APCs.The IISS messages are logged in the file NTMLOG.DAT.


,LG (return)

SELECT LOGGING FUNCTION COMMAND

SELECT ONE FROM THE FOLLOWING FUNCTIONS.

1. DISABLE ALL MESSAGE LOGGING.2. ENABLE LOGGING OF ALL MESSAGES.3. ENABLE SELECTIVE LOGGING:

(CHOICES WILL FOLLOW)4. QUITENTER CHOICE:)

If choice 1 is selected:,1 (return)

LOGGING HAS BEEN DISABLED.)

will appear. All message logging is now disabled.

If choice 2 is selected:,2 (return)

Logging of all messages is enabled.

will appear. All IISS messages will now be logged. (the

IIS8 startup default)

If choice 3 is selected:

The first question to appear is

2-5

ON 8201420001 November 1985

DO YOU WISH TO DISABLE ANY MESSAGE PRIORITIES?(1: YES 2: NO)ENTER RESPONSE (112):

If 1 Is selected, the next choice that appears Is:

DISABLE NOT (H) OR COLD (C) MESSAGES?RESPONSES: 1: NOT 2: COLD)ENTER CHOICE (1/2):

The operators choice will disable the requested priority.If, for example, the operator enters an Invalid choice, heis asked to repeat the entry. Three tries are givenbefore the selective logging program aborts and returnscontrol to the operators normal monitoring sequence.

The next choice that appears If 03 was selected from theoriginal menu is

DO YOU WISH TO DISABLE ANY MESSAGE CATEGORIES?(1: YES 2: NO)ENTER RESPONSE (1/2):

If 1 is selected, the existing categories will be displayedone by one for the operator to select the categories that hewishes to disable. The following Is an example dialog for thisfeature.

DISABLE CATEGORY: A?(1: YES 2: NO)ENTER RESPONSE (1/2):

DISABLE CATEGORY: B?(1: YES 2: NO)ENTER RESPONSE (1/2):

DISABLE CATEGORY: C'?(0: YES 2: NO)ENTER RESPONSE (1/2):

DISABLE CATEGORY: D?

2-6

ON 6201420001 November 1985

(1: YES 2: NO)ENTER RESPONSE (1/2):,1

DISABLE CATEGORY: E?(1: YES 2: NO)ENTER RESPONSE (1/2):)1,

DISABLE CATEGORY: F?(1: YES 2: NO)ENTER RESPONSE (1/2):)1

DISABLE CATEGORY: G?(1: YES 2: NO)ENTER RESPONSE (1/2):)1

DISABLE CATEGORY: H?(1: YES 2: NO)ENTER RESPONSE (1/2):)1

DISABLE CATEGORY: I?(1: YES 2: NO)ENTER RESPONSE (1/2):,1I

DISABLE CATEGORY: J?(1: YES 2: NO)ENTER RESPONSE (1/2):

The last selective logging choice allows the operator todisable logging at particular APCs. The choices and a sampledialog follow:

DO YOU WISH TO MODIFY LOGGING BY PARTICULAR APCS?(1: YES 2: NO)ENTER RESPONSE: (1/2)3,1

SOURCE/DESTINATION LOGGING CHOICES:

I. LOG AT MESSAGE SOURCE APCS ONLY.2. LOG AT BOTH SOURCE AND DESTINATION APCS.

2-7

ON 6201420001 November 1985

3. LOG AT ALL APCS WHERE LOGGING IS ENABLED.ENTER RESPONSE (1/2/3):, 3

DO YOU WISH TO DISABLE ANT APCS?(1: YE8 2: NO)ENTER RESPONSE (1/2):

DISABLE APC: NRV?(1: YES 2: NO)ENTER RESPONSE (1/2):. IDISABLE APC: UIV?(1: YES 2: NO)ENTER RESPONSE (1/2):, I

DISABLE APC: TIV?(1: YES 2: NO)ENTER RESPONSE (1/2):, 2

DISABLE APC: CON?(1: YES 2: NO)ENTER RESPONSE (1/2):, 2

DISABLE APC: CDM?(1: YES 2: NO)ENTER RESPONSE (1/2):, 2

SELECT LOGGING FUNCTION COMPLETE.

2.11 Start a New Log File (SN)

ENTER OPERATOR COMMAND (OR HELP)SN (return)

A new LOGFILE has been started

On the VAX, a new version of the logfile, NTNLOG.DAT willbe started. This allows the operator to isolate the logs forspecific tests or times.

2-8

ON 6201420001 November 1985

SECTION 3

SHUTTING DOWN THE IISS

The operator command "Shutdown IISS" is invoked when theentire 1ISS system is to be shutdown. IISS shutdown isaccomplished in four phases as follows:

Phase 1 Notify users that IISS shutdown is pendingPhase 2 Request the shutdown of non-component APC's

and remote hosts.Phase 3 Request the shutdown of network

communicationsPhase 4 Shutdown component APC's

When the shutdown command is entered, the operator isprompted for a "time until shutdown." The time value (inminutes) entered by the operator will determine the elapsed timeuntil shutdown processing (phase 2) actually begins. Phase 1will be executed only if time until shutdown is one minute ormore. Otherwise, shutdown will proceed immediately to phase 2,thereby denying active AP's the time to shut down gracefully.During Phase 1, IISS users are notified that a system shutdownis pending and they should prepare to close their session.After shutdown has been requested, only operator commands"Display IlSS Status, "Display Active AP's", and "CancelShutdown" will be accepted. It is only during phase 1 ofshutdown that the operator may choose to cancel the shutdownrequest. If the operator requests the "Cancel Shutdown"command, IISS users are notified that the shutdown has beencancelled and normal IISS processing is resumed. After theelapsed time until shutdown has expired, shutdown processingbegins with the shutdown of all active non-component APC's andactive remote hosts. All components not responding to theshutdown request within a certain time interval will be assumedterminated. When all non-component APC's and remote hostsshutdown in phase 2 have been accounted for. phase 3 is entered.During this phase network communications are terminated. henall active comm links have been shutdown, phase 4 of shutdownbegins and all component APC's are shutdown. Finally, when allother NTM components have terminated, Monitor AP concludesshutdown processing and ends execution.

The following is an example of the IISS shutdown request:


3-1

ON 6201420001 November 1985

SD(return)ENTER MINUTES ('X' TO EXIT) UNTIL SHUTDOWN

i 1return)SHUTDOWN WILL BEGIN IN 1 MINUTE

(one minute later)BEGINNING IISS SHUTDOWN*88APC TIV HAS SHUTDOWN*"COMM LINK Vii HAS SHUTDOWN*

S*SAPC UIV HAS SHUTDOWN*****APC CDK HAD SHUTDOWN****APC OOV HAS SHUTDOWN*****~APC MRV HAS SHUTDOWN***

~IISS SHUTDOWN COMPLETE***

Control is returned to the host operating system.

3-2

OM 6201420001 November 1985

SECTION 4

ERROR CODES

4.1 NPU Processinf Error Codes (31XXX)

MPU processing codes are those errors which are detected byan NPU during its normal processing activities. Upon theoccurrence of an MPU processing error, the following errormessage is displayed to the IISS operator console:

MPU PROCESSING ERROR: SOURCE: MPU-NAMEERROR CODE: CODE FOR ERROR OCCURRENCEERROR INFO: FURTHER CLARIFICATION OF THE ERROR

The "source" of the MPU processing is the name of the MPUthat detected the error condition. The "error info" is datarelevant to the error condition. As an example, on a 31001error (Mailbox Write) the name of the mailbox where the erroroccurred is given. Table names, file names, and (host) systemreturn codes are other examples of information supplied in anMPU processing error message. In most cases, it will benecessary to call the IISS system programmer to investigate thecause of the problem.

The MPU processing error codes are as follows:

31001 MAILBOX WRITE ERROR31002 MAILBOX CREATE ERROR31003 NO READ ON MAILBOX31004 MAILBOX DISCONNECT ERROR31005 EVENT WAIT ERROR31006 SET TIMER ERROR31007 TABLE MAPPING ERROR (VAX)31008 JOB PROCESS INFORMATION ERROR (VAX)31009 PROCESS START ERROR31010 PROCESS ABORT ERROR31016 TABLE READ ERROR31017 TABLE WRITE ERROR31018 CDM ACCESS ERROR31019 MESSAGE ROUTING ERROR31020 OS CALL ERROR31021 TIMEOUT ERROR31022 COBOL CALL ERROR31023 EXCEPTION CONDITION31024 TABLE ENTRY NOT FOUND

4-1

OM 6201420001 November 1985

31025 TABLE ENTRY NOT DELETED31026 INVALID SEARCH FIELD31027 CANCEL TIMEOUT ERROR31028 IPC ERROR31029 FILE RE-WRITE ERROR31030 FILE INDEX ERROR31031 QUEUE TABLE ERROR31033 INVALID FUNCTION CODE31034 SIBLING NOT FOUND31011 PROCESS NOT FOUND31100 FILE READ ERROR31200 FILE WRITE ERROR31300 CLOSE FILE ERROR31400 OPEN FILE ERROR31500 FILE START ERROR31600 FILE DELETE ERROR

4.2 AP Interface Error Codes (32XXX)

AP interface errors are those errors occuring in the APinterface (to the NTM) and detected by the MPU during messageprocessing. All errors of this type involve invalid messageheader field values. For example, upon the occurrence of an APinterface error where an invalid message category is given inthe header, the following message will be displayed to the IISSoperator console:

AP INTERFACE ERROR; SOURCE: mpu-nameERROR CODE: 32001ERROR INFO: errant-ap-name

The "source" of the message refers to the MPU that detectedthe error and the "ERROR INFO" indicates the name of theapplication process sending the message where the error hasoccurred. These errors are caused by the AP of AP Interfaceproviding invalid data n the message header. The applicationdesigner should check to insure that proper "Data Lengtho,"Message Type", and "Destination AP Name" arguments are passedto the AP Interface. Otherwise, it will be necessary for theIISS system programmer to investigate the errant AP Interface.

The AP interface error codes are as follows:

32001 INVALID MESSAGE CATEGORY32002 INVALID HEADER FORMAT32003 INVALID HEADER LENGTH32004 INVALID HEADER BINARY/NATIVE FLAG

4-2

ON 6201420001 November 1985

32005 INVALID MESSAGE TYPE32006 INVALID MESSAGE SOURCE APMAME32007 INVALID MESSAGE SOURCE AP INSTANCE32008 INVALID MESSAGE SOURCE APC NAME32009 INVALID HEADER PROCESSING CODE32010 INVALID EADER CONTINUATION INDICATOR32011 INVALID DATA LENGTH32012 INVALID MESSAGE PRIORITY

4.3 Resource Unavailable Error Codes (33XXX)

A "RESOURCE UNAVAILABLE ERROR" occurs either when anapplication process requests an IISS system resource that iscurrently unavailable or when a table-full is encountered whentrying to write an entry to an NTM table. In either case, thefollowing message is displayed to the IISS operator console:

RESOURCE UNAVAILABLE MESSAGE FROM: mpu-nameERROR CODE: 33001RESOURCE: unavailable-resource-name

The "SOURCE" refers to the MPU where the resourceunavailable condition was detected. "RESOURCE" is the name ofthe requested resource, such as a table name or a destination APof APC name.

There is currently only one "RESOURCE AVAILABLE" error codewhich covers both cases.

33001 TABLE FULLRESOURCE UNAVAILABLE

The "RESOURCE" portion of the message will indicate the

type of resource in question.

4.4 Table Error Codes (35XXX)

Table error codes provide the return status from the tableaccess routines. The return of one of these cbdes does notnecessarily imply that an error has occured. The MPU willinterpret the returns in the context of the call and will informMonitor only where an error condition is deemed to exist. As anexample, the END-OF-TABLE return is given at the end of thetable routines READ-ALL function. In the case where the MPU ispolling the table (such as when checking for timed-out messagepairs) this is not considered to be an error. However, when theMPU's records show the existence of an entry, a return of

4-3

OH 6201420001 November 1985

END-OF-TABLE before the entry is found does indicate an errorcondition.

There are also occurrences of table error conditions thatare of interest to the AP's. The MPU will send an error messageto the AP on these occurrences. In most cases, these conditionswill occur while the AP is waiting for a return from an APIService. The services are therefore able to interpret the errormessage and return the appropriate status code. In those caseswhere control has been returned to the AP, the MPU uses theSIGERR message convention to inform the AP of the erroroccurrence. The AP must of course be in test mode in order toreceive these messages.

The table error/status codes are:

00000 SUCCESSFUL RETURN31024 ENTRY NOT FOUND (on a READ-SEARCH access)35002 END OF TABLE (on a READ-ALL access)33001 TABLE FULL (on a WRITE-NEW access)

4.5 Monitor AP Error Codes (30XXX)

Monitor AP error codes are associated with errors detectedby the Monitor AP during its normal processing. Most errorsdetected by the Monitor are at system start up. These errorsmay cause the Monitor to terminate depending on where the erroroccurred. Errors may also occur during shutdown or operatorcommand processing. When an error is detected, the error codeand a descriptive message are displayed at the operator'sconsole. Errors pertaining to entries not found In tables(30010-30013) are probably indications of inconsistenciesbetween tables. Timeout errors (30001, 30002, 30015) imply thata process the Monitor AP expects a message from is notresponding. In most cases it will be necessary to call the IISSsystem programmer to investigate the problem.

The following is a list of all currently defined monitorerror codes:

30001 TIMEOUT ON WAIT FOR MPU TABLE STATUS REQUEST30002 TIMEOUT ON WAIT FOR MPU START UP STATUS30005 INVALID EVENT RECEIVED30010 ENTRY NOT FOUND IN APC STATUS TABLE30011 ENTRY NOT FOUND IN LINK STATUS TABLE30012 ENTRY NOT FOUND IN LINK STATUS TABLE30013 ENTRY NOT FOUND IN HOST-LINK-TABLE

4-4

ON 6201420001 November 1985

30015 LINK START TIMEOUT30016 LINK FAILED AT START UP30017 COMM AP START-UP FAILED30020 COMPONENT APC FAILED AT START UP30025 NO RESPONSE FROM CENTRAL NODE (VAX)30030 ERROR IN GET TERMINAL ID

4-5

ON 6201420001 November 1985

SECTION 5

NTH TABLE MAINTENANCE

5.1 Overview

This section describes the procedures for maintenance ofthe NTH tables. The NTM uses the tables described in thissection to maintain system information and current status. Someof the NTH tables are global to all MPU components on a hostwhile some are local to each MPU. It is anticipated that in thefuture these tables will be kept and configured in the CDK(Common Data Model) and will be the responsibility of the CDA(Common Data Administrator). For the time being, however, whena change is made to the IISS which affects the systemconfiguration (for example, the addition of a new AP), certaintables must be manually updated to reflect these changes.

The tables which are to be maintained by the IISS system

operator are as follows:

0 Authority Check Table (ACT)

Provides indication of whether or notmessage access to an AP requiresauthorization.

* AP Cluster Status Table (APC)

Provides both the host location within theIISS and the current operational status ofan application process cluster (APC)

0 AP Information Table (API)

Provides the name of the APC on which anapplication resides in the IISS

* AP Characteristics Table (APT)

Provides the processing characteristics ofall application processes in the IISSenvironment.

5-1

1

011 6201420001 November 1985

* Message Category Table (CAT)

Provides information pertaining to specific11TH message processing based on messagecategory.

* Host Status Table (HST)

Provides the current operational status of ahost machine on the 1188.

* Link Status Table (LST)

Provides the current operational status of acommunication link between two hosts on the1158.

0 Directory Table (DIR)

Provides directory Identifiers, their fulldirectory names, and the length (in bytes)of the full directory name. At present thisname is restricted to 12 bytes including theperiod.

It should be noted that there are additional 11TM tables butthey are dynamic in nature and do not require dataInitialization.* Because this document Is concerned only withthose tables requiring modification due to system configurationchanges, a discussion of these dynamic tables Is omitted. Allof the N1TH tables are fully described in the N1TH DevelopmentSpecification In Section 3.5.

Given a change to the IISS system configuration, one ormore of the above tables will need to be updated. Themodification of any of these tables is a simple andstraightforward procedure involving editing a table

* In the previous edition of this document the AP OperatingInformation table (APO) was identified as a static table.Due to it's nature, it has been reconfigured as a dynamictable and Is therefore, no longer of concern here.

5-2

LLI

ON 6201420001 November 1985

initialization file to make the necessary changes. These tableintt files are maintained in the NTN system directory on eachhost in the IISS system. The file names are of the format"xxxTBL" where Oxxxo is the three character table identifier.

The specific table initialization data file names are asfollows:

VAX HL6 IBM

HSTTBL.DAT HSTTBL.DAPCTBL.DAT APCTBL.DLSTTBL.DAT LSTTBL.DAPTTBL.DAT APTTBL.DAPITBL.DAT APITBL.DACTTBL.DAT ACTTBL.DCATTBL.DAT CATTBL.D

The above table initiation files contain data which appearsas a string of characters. Each record in the file representsone table entry. Therefore, to add a new entry to a table, onehas only to add another entry to the table initiation file.Similarly, to delete or modify a table entry, the specificrecord in the initiation file should be deleted or modified. Itis critical that the alignment of data in these records remainintact: any errors introduced during the editing process willcause problems at system run time. For this reason, great careshould be taken when modifying any table initialization file.When editing a file, check to make sure the new or modifiedentry is in line with all of the other file entries.

5.2 Table Descriptions

In the following section, the structure of above tables andan example of an initialization data record for each will bedescribed. This should be used as a guide when updating any ofthe NTM tables. For further information regarding these tablesand a description of individual fields, see the "IISS Test BedNetwork Transaction Manager Development Specification." A listof legal table values for each data item is given in Section 4.5of this document.

5-3

ON 6201420001 November 1985

ACT - AUTHORITY CHECK TABLE

FIELD NAME SIZE Tp

DESTINATION AP NAME 8 ALPHANUMERIC

ACCESS FLAG 1 ALPHANUMERIC

TABLE INITIALIZATION FILE ENTRY (ACTTBL)

TSAP1MPUI

I II I

I ....-- ACCESS FLAG

, DESTINATION AP NAME

NOTE: The authority check is based on the "generic' AP name.The access restrictions are directory independent.

APC - AP CLUSTER STATUS TABLE

FIELD NAME SIZE TYPE

AP CLUSTER NAME 3 ALPHANUMERICAP CLUSTER STATUS 1 NUMERICAP CLUSTER LOGICAL HOST 3 ALPHANUMERIC

TABLE INITIALIZATION FILE ENTRY

CDM5VAX

I-------AP CLUSTER LOGICALI I HOSTi I

-------- AP CLUSTER STATUS

, AP CLUSTER NAME

5-4

ON 6201420001 November 1985

NOTE: The value assigned to ustatus" wili in fact deterninewhether the APC Is initiated at startup.

5-5

ON 6201420001 November 1985

API - AP INFORMATION TABLE


AP NAME 10 ALPHANUMERICAP CLUSTER NAME 3 ALPHANUMERIC

QUEUE SERVER TYPE 1 ALPHANUMERIC

TABLE INITIALIZATION FILE ENTRY (APITBL)

NTTSAP1MPUT1V1- - - QUEUE SERVER

II I--, TYPEI I

.. AP CLUSTERNAME

------------------- AP NAME

NOTE: The API table is directory dependent. As there may bedifferent versions of an AP residing in differentdirectories, those versions may also be assigned todifferent APC's.

5-6

ON 8201420001 November 1985

APT -AP CHARACTERISTICS TABLE

MAKE SIZE TYPE- - -- - -- -

AP NAME a ALPHANUMERICMAX. NUMBER OF QUEUEDMESSAGES 2 NUMERICMAX. INSTANCES 2 NUMERICNUMBER OF PARENTSPER INSTANCE 2 NUMERICINITIATION NEEDS 1 NUMERICON ABORT 1 NUMERICNUMBER OF MAILBOXES 1 NUMERICON SHUTDOWN 1 NUMERICON RECOVERY 1 NUMERICON CHILD NORMAL TERM. 1 NUMERICON CHILD AENORM TERM. 1 NUMERICON CHILD SHUTDOWN 1 NUMERICTIMEOUT HANDLING 1 NUMERICAP PRIORITY 1 NUMERIC

5-7

ON 6201420001 November 1985

TABLE INITIALIZATION FILE ENTRY (APTTBL)

--------------------------- AP NAME

------------------------- MAX NUMBER OF QUEUEDI I MESSAGES

I ---------------- MAX INSTANCES

I II-------------- NUMBER OF PARENTSI I I IPER INSTANCE

TSAP1NPU0101010320000010

1111111I -AP PRIORITYINITIATION NEEDS <------------1111111 I

1111111 -)- TIMEOUT HANDLINGON ABORT t ---------111111I

1111 --- ON CHILD11111SHUTDOWN

NUMBER OF MAILBOXES 4 --------- l1111Ill-----ON CHILD ABNORM.III TERM.

ON SHUTDOWN-,--------------III---------ON CHILD NORM. TERM.

ON RECOVERY-(--------------

NOTE: The APT table is directory independent. It is assumed thata given AP will have a single set of characteristics regardless ofit's directory location or the number of existing versions. Thevalues In this table drive the NTM's processing of an AP. It iscritical that they are defined correctly.

5-8

ON 6201420001 November 1985

CAT - MESSAGE CATEGORY TABLE


MESSAGE CATEGORY 1 ALPHAAUTHORIZATIONREQUIREMENT 1 NUMERICPAIRING REQUIREMENT 1 NUMERICGUARANTEED DELIVERY 1 NUMERICMESSAGE PRIORITY 1 NUMERICLOG REQUIREMENT 1 NUMERICSTATISTICS COLLECTION FLAG 1 NUMERIC

TABLE INITIALIZATION FILE ENTRY (CATTBL)

---------------------------~ MESSAGE CATEGORY

------------- AUTHORIZATIONI I REQUIREMENT

I ---------- > PAIRING REQUIREMENT

---------------------------- GUARANTEED DELIVERY

AlOlOll

ii--- STATISTICS COLLECTION FLAG

---------------------------------------------------------LO EURMN

-------------------------------------------------------MSAEPIRT

5-9

ON 6201420001 November 1985

liST - HOST STATUS TABLE


LOGICAL HOST NAME 3 ALPHANUMERICHOST STATUS 1 NUMERICPHYSICAL HOST NAME 3 ALPHANUMERIC

TABLE INITIALIZATION FILE ENTRY (HSTTBL)

VAXO VAX

I I --- PHYSICAL HOST NAME

-------- HOST STATUS

--------------------~ LOGICAL HOST NAME

LST - LINK CLUSTER STATUS TABLE


LINK ID 2 ALPHALINK STATUS 1NUMERIC

TABLE INITIALIZATION FILE ENTRY

VIHO

I I---LINK STATUS

--- -- --- -- --- -- --- -- ---------------------------------LI K I

--- ---------------------------------------------------------

5-10

ON 6201420001 November 1985

DIR - DIRECTORY TABLE


DIRECTORY PREFIX 2 ALPHANUMERICDIRECTORY NAME 20 ALPHANUMERICDIRECTORY NAME LENGTH 2 ALPHANUMERIC

TABLE INITIALIZATION FILE ENTRY (DIRTBL)

NT[CROS.NTNTESR] 12

I I

- -I DIRECTORYI NAME LENGTH

I I

- DIRECTORY NAME

------------ DIRECTORY PREFIX

NOTE: All directory prefixes used by AP's in the IISS

must be defined in this table.

----------------------------------------------------------

5.3 Monitor AP Internal Table

The monitor AP has a special internal table, called theHost-Link Information Table (liLT), which provides the monitorwith information regarding remote IISS hosts, the comm linksused to communicate with these remote hosts, and the remotemonitor APs. This table is maintained as a sysgen parameter.

5.4 When to Modify a Table

Host Status Table.

The Host Status Table is modified when a new host is addedto the IISS configuration. The host status entry shouldbe initialized to "0" (inactive).

AP Cluster Status Table.

The AP Cluster Status Table is modified under two

5-11

ON 6201420001 November 1985

circumstances: (1) when a new APC Is added to the IISSconfiguration, or (2) when the Initial APC status is to bemodified. The APC status differs from the host or linkstatus In that there Is more than one initial statuspossible; a value of "5n Is assigned If the APC Is to beinitiated during IISS start up; a value of '2" Is assignedIf It Is not to be Initiated at start up.

Link Status Table.

The Link Status Table is modified when a new host, andtherefore new coma links, are to be added to the systemconfiguration. The link status entry should beinitialized to "0" (inactive).

AP Characteristics Table.

The AP Characteristic Table must be modified when an AP isadded or removed from the system configuration or when acharacteristic of an AP changes. The characteristics ofan application process are specified by the applicationdesigner based on the list of characteristics supported bythe 11TM. These values must be supplied at the time thenew AP is introduced to the IISS environment.

A? Information Table.

This table is modified when a new application process isadded to the system configuration. The systemadministrator determines, based on the database supportingthe application, which AP cluster the new AP is to resideon. If an application process is moved from one APC toanother, the API table must be modified to reflect thischange. The AP's chaining support requirement (QueueServer Type Value) is supplied by the AP developer.

Authority Check Table.

A new entry is made to the authority check table when anew application process is added to the system or when theauthority restriction of an AP Is changed. Theapplication designer determines whether or not messagessent to the new AP require authorization.

Message Category Table.

Modification of the Message Category Table is necessary

5-12

ON 6201420001 November 1985

only when a new message category is created or when theprocessing requirements implied by the message categoryare changed.

Directory Table.

Modification of the Directory Table is required when a newdirectory is added to the IISS configuration.

Host-Like Information Table.

When a new host is introduced into the IISS environment, anew entry must be made in this table. This isaccomplished by adding REC-N (where N is the next numberavailable) to the include file BASYSG.INC. The specificvalues of the new entry will be stored in this file. Inaddition, the value for "INIT-LINK-COUNT" must be updatedto reflect the actual number of links that must beestablished at startup. The new record and volumes areread into the sysgen data file by running MPUGEN to createa default file.

Below is a description of the fields of the Host-LinkInformation Table:

HLT - HOST-LINK INFORMATION TABLE (INTERNAL TO THEMONITOR AP)


COMM LINK ID 2 ALPHANUMERICCOMM AP NAME 10 ALPHANUMERICREMOTE MOST NAME 3 ALPHANUMERICREMOTE MONITOR AP NAME 10 ALPHANUMERICREMOTE MONITOR APC NAME 3 ALPHANUMERICNODE TYPE 1 NUMERIC "

5-13

ON 6201420001 November 1985

V ICOCONY ICONIBMNTMONITIMPUNRIO

I I I------ ,NODE TYPE

I I IREMOTE MONITOR APCI I I INAME

--I--- REMOTE MONITOR AP NAME

I I---------------- REMOTE HOST NAME

I------------------------ COMM AP NMNE

--- --- --- --- --- --- ) COMM LINK ID

5-14

ONf 6201420001 November 1985

5.5 Table Values

The following is a list of legal values for the tablefields.

Access Flag (ACT)

0 - Restricted Access (requires authorization)I - Open Access

AP Cluster Status (APC)

I - Active2 - Unavailable (will not be started during

startup)3 - Shutting Down4 - In Start Up5 - Start APC at IISS Start Up

AP Priority (APT)

0 - Default AP Priority (all present all I185 AP'swill be assigned the same priority)

Authorization Requirement (CAT)

0 - Message Does Not Require Authorization1 - Message Requires Authorization

Guaranteed Delivery (CAT)

0 - No Guaranteed DeliveryI - Guaranteed Delivery Services Required on

Me ssage

Host Status (HST)

0 - InactiveI - Active2 -In Start Up3 - In Shutdown

Initiation Needs (APT)

0 - No RestrictionI - Requires AP Init Message2 - Start From Terminal (UI Only)

5-15

ON 6201420001 November 1985

Link Status (LST)

0 - Inactive1 - Active2 - Initiated (Waiting Response)3 - Comm AP is active but link to remote host is

not

Log Requirement (CAT)

0 - Message is not to be Logged1 - Message is to be Logged

Message Priority (CAT)

0 - Low PriorityI - High Priority

Mode Type (HLT)

0 - IISS Remote Node1 - IISS Central Node

Number of Mailboxes (APT)

0 - AP Does Not Require Mailboxes1 - AP Supports a Cold and an ACK Mailbox only2 - AP Supports Cold, ACK, and Hot Mailboxes

On Abort (APT)

1 - Run to Completion2 - Send Abort Message to AP3 - Abnormally Terminate AP

On Child Abnormal Termination (APT)

0 - No Message to AP1 - Message to AP Required2 - Terminate Parent AP

On Child Normal Termination (APT)


5-16

ON 6201420001 November 1985

On Child Shutdown (APT)


On Recovery (APT)

0 - AP Has No Recovery Logic1 - AP Has Internal Recovery Logic

On Shutdown (APT)

0 - AP Has No Shutdown LogicI - AP Has Logic To Gracefully Shut Itself Down

Pairing Requirement (CAT)

0 - Message Not Paired1 - Message Paired

Queue Server Type (API)

0 - No Chaining Support Required1 - Child AP Chaining Support Required2 - Message Chaining Support Required

Statistics Collection Flag (CAT)

0 - No Statistics Collected On MessageI - Statistics Collected On Message

Timeout Handling (APT)

0 - Paired Messages Not HandledI - Cancel Message Pair On Timeout2 - Abort AP On Timeout3 - Do Not Cancel Pair (Renew Timeout Period)

5-17

111,1 1(105J(

ON 6201420001 November 1985

SECTION 6

TROUBLESHOOTING SUGGESTIONS

There may be times when something completely unexpectedoccurs or something expected doesn't occur. This sectionaddresses what these situations might look like and what to dowhen they are detected. These problems tend to be host specificand therefore will be discussed as such.

VAX EXAMPLES:

1. If the IISS is started while various components (MPU's)within the sane group are still executing, the followingmay be observed:

@IISS

** 8 8 ** CLEANUP*** S* S * * * BEGINNING IISS START UP5 * * * *

%COB-F-INVDECDAT, invalid decimal data$

To correct this situation, the operator must stop allcurrently running MPU's in the group using the "STOPProcess Name" command under VMS and re-enter the IISScommand procedure.

2. If. during normal IISS operation, the operator consoledoes not respond and the system appears to be hung up, theoperator may abort the IISS process by entering a "CTRL Y"character. Once at the host operating system commandlevel, all MPU's must be stopped via the "STOP" commandunder VMS.

3. It is possible that after "* * * * BEGINNING IISS START UP

* * * *" is displayed to the console, the host operating

system command level prompt is returned with no indicationas to what happened to the IISS. The problem here mayinvolve terminal device assignment conflicts. Theoperator should log off of the system, log back on and tryagain. If the problem persists, call the IISS systemprogrammer.

6-1

OH 6201420001 November 1985

APPENDIX A

NTH LOG UTILITY

Description - The NTH log utility is a tool which provides thefollowing functions:

1. Selection of NTH log records based upon any combination ofthe following fields:

A. DateB. TimeC. Destination Application Program NameD. Destination Application Program Cluster NameE. Source Application Program NameF. Source Application Program Cluster NameG. Message TypeH. Message Category

2. Online display of selected T log records.

3. File creation of selected 11TM log records.

4. File creation of selected 1TH log records formatted peronline display option.

Processing Options -

1. Selection Criteria

A. Date - To select on the date field, a beginning andending date must be entered per the followingformat:

DD-KHM-YYYY where - 'DD' represents the day- 'MHH' represents the month- 'YYYY' represents the year

Example - 01-MAR-1985

Date Field Options:

1. Enter date per required format.

2. Leave the date field blank to default to the

A-1

j"

ON 6201420001 November 1985

current date.

3. Enter one or more asterisks to use thefollowing defaults:

O1-JAN-O001 - FOR BEGINNING DATE31-DEC-9999 - FOR ENDING DATE

B. Time - To select on the time field, a beginning andending time must be entered using the followingformat:

HH:MM:SS.ss where - 'HH represents hours'MM' represents minutes'SS' represents seconds'ss' represents

hundreths of asecond

Time Field Options:

1. Enter time per required format.

2. Leave the time field blank to use thefollowing defaults:

00:00:00.00 - FOR BEGINNING TIME23:59:59.59 - FOR ENDING TIME

3. Enter a partial time and use the defaultvalue so the remaining positions of the timefield (i.e., hours, hours and minutes, orhours, minutes, and seconds only).

Example - 09: DEFAULTS TO09:00:00 WHEN ENTERED FOR THE

BEGINNING TIMEAND 09:59:59 WHEN ENTERED FOR THE

ENDING TIME

C. Destination Application Program NameDestination Application Program Name Field Options:

1. Enter a 10-character destination application programname.

2. Leave the destination application program name field

A-2

ON 6201420001 November 1985

blank to use the following default: 'KTNTNONITV'.

D. Destination Application Program Cluster NameDestination Application Program Cluster Name FieldOptions:

1. Enter a 3-character destination application programcluster name.

2. Leave the destination application program clustername field blank to use the following default:'NRV'.

E. Source Application Program NameSource Application Program Name Field Options:

1. Enter a 10-character source application programname.

2. Leave the source application program name blank touse the following default: 'NTNTHONITV'.

F. Source Application Program Cluster NameSource Application Program Cluster Name Field Options:

1. Enter a 3-character source application programcluster name.

2. Leave the source application program cluster nameblank to use the following default: 'RV ° .

G. Message Type - Enter a 2-character message type- A default message type is not available- A blank message type will be ignored and

treated as though message type was notselected.

H. Message Category - Enter a 1-character message category- A default message category is not

available- A blank message category will be

ignored and treated as though messagecategory was not selected.

2. Online Display Option

When the "online display" option is selected, each NTH log

A-3

ON 6201420001 November 1985

record which satisfies the selection criteria will bedisplayed on the terminal. Each displayed record consistsof two or three screens. The first screen displays the NTMlog header information (positions 1-127), while the secondand third screens display the NTM log data information(positions 128-2042). The third screen will only appearwhen the NTM log record being displayed contains more than960 characters of data. After each screen is displayed, thefollowing options are available:

A. You may continue to the next sequential screen bypressing the carriage return.

B. You may select to display the first screen (NTM logheader information) for the next selected NT logrecord.

C. You may terminate displaying of selected NT log

records.

3. File Creation of Selected NTH Log Records

When the *create an NT! log file" option is selected, eachNTM log record which satisfies the selection criteria willbe written as raw data to the user-specified file name orwhen a file name is not specified, the following defaultfile name will be created in the current user's directory:NTMUTIL.DAT

4. File Creation of Selected NT Log Records Formatted perOnline Display Option

When this option is selected, each NTM log record whichsatisfies the selection criteria will be written in theformat of the display option screens to the user-specifiedfile name or when a file name is not specified, thefollowing default file name will be created in the currentuser's directory: NTNRPT.DAT

Miscellaneous Notes:

1. The input NTM log may be a fixed or variable length filewith a record length not exceeding 2042 characters. When aninput NTM log file is not specified, the following defaultfile name will be used and accessed in the current user'sdirectory: NTMLOG.DAT

A-4

!

ON 8201420001 November 1985

2. Upper and lover case characters are acceptable a input.When a lover case character is entered in a selection field,the character will be converted to the equivalent upper casecharacter and used as such for all further displays and fileselection.

3. Any termination of the program after having selected thecreation of an output file vill result in the creation ofthe requested file.

A-5

ON 6201420001 November 1985

EXAMPLE ONE

Reformats all NTMLOG.DAT records.

No interactive display of selected records.

Creates formatted output file NTIRPT.DAT.

A-6

-v a a!

OH 6201420001 November 1985

RUN NTMUTIL

**' NTH LOG ANALYSIS UTILITY STARTED ***

PLEASE ENTER THE NAME OF THE NTH LOG FILE TO BE ANALYZED:NTM LOG FILE TO BE ANALYZED DEFAULTS TO: NTMLOG.DAT

&w

WOULD YOU LIKE TO CREATE A FILE CONTAINING THE SELECTEDNTH LOG RECORDS? (YIN): NO

WOULD YOU LIKE TO CREATE A FILE CONTAINING THE SELECTEDNTH LOG RECORDS IN THE ONLINE DISPLAY FORMAT? (YIN): YES

PLEASE ENTER THE FILE NAME:DEFAULT FILE NAME: NTMRPT.DAT

WOULD YOU LIKE TO SELECT ON DATE? (Y/N): N

WOULD YOU LIKE TO SELECT A DESTINATION AP NAME? (Y/N): no

WOULD YOU LIKE TO SELECT A DESTINATION APC NAME? (Y/N): n

WOULD YOU LIKE TO SELECT A SOURCE AP NAME? (YIN):

WOULD YOU LIKE TO SELECT A SOURCE APC NAME? (Y/N):

WOULD YOU LIKE TO SELECT A MESSAGE CATEGORY? (Y/N):

NO SELECTION CRITERIA HAS BEEN ESTABLISHEDALL RECORDS WILL BE SELECTED

WOULD YOU LIKE TO CONTINUE PROCESSING SELECTED CRITERIA? (Y/N): Y

WOULD YOU LIKE TO HAVE THE NTH LOG DISPLAYED? (Y/N): Y

PROCESSING IS COMPLETE

NUMBER OF RECORDS READ - 000000548NUMBER OF MATCHES FOUND - 000000548

THE FOLLOWING FILE HAS BEEN CREATED CONTAINING 000025208 RECORDS -

NTMRPT.DAT

WOULD YOU LIKE TO RUN THE NTH LOG UTILITY AGAIN? (Y/N): N

$

A-7

OM 6201420001 November 1985

EXAMPLE TWO

Selects records from NTM14MAY.DAT having a destination

APC name of "NRV" and time stamp in the range of

12:00:00 - 12:34:59.

Selected records are displayed online.

Output files NTMLOG.DAT and RPT14MAY.DAT are created.

A-8

ON 6201420001 November 1985

RUN NTMUTIL

*** NTM LOG ANALYSIS UTILITY STARTED *

PLESE ENTER THE NAME OF THE NTM LOG FILE TO BE ANALYZED:NTM14MAY.DAT

WOULD YOU LIKE TO CREATE A FILE CONTAINING THE SELECTEDNTM LOG RECORDS? (Y/N): Y

PLEASE ENTER THE OUTPUT NTM LOG FILE NAME: NEWLOG.DAT

WOULD YOU LIKE TO CREATE A FILE CONTAINING THE SELECTEDNTM LOG RECORDS IN THE ONLINE DISPLAY FORMAT? (YIN): Y

PLESE ENTER THE FILE NAME: RPT14MAY.DAT

WOULD YOU LIKE TO SELECT ON DATE? (YIN): Y

PLEASE ENTER THE FILE NAME: RPT14MAY.DAT

WOULD YOU LIKE TO SELECT ON DATE? (Y/N): Y

ENTER BEGINNING DATE (DD-MMM-YYYY): *BEGINNING DATE DEFAULTS TO : O1-JAN-0001

ENTER ENDING DATE (DD-MMM-YYYY): *ENDING DATE DEFAULTS TO : 31-DEC-9999

WOULD YOU LIKE TO SELECT ON TIME? (Y/N): YENTER BEGINNING TIME (HH:MM:SS): 12

BEGINNING TIME DEFAULTS TO: 12:00:00ENTER ENDING TIME (HH:MM:SS): 12:34

ENDING TIME DEFAULTS TO: 12:34:59

WOULD YOU LIKE TO SELECT A DESTINATION AP NAME? (YIN):

WOULD YOU LIKE TO SELECT A DESTINATION APC NAME? (YIN): YENTER DESTINATION APC NAME (MAX - 3 CHAR):

DESTINATION APC NAME DEFAULTS TO : MRVWOULD YOU LIKE TO SELECT A SOURCE AP NAME? (Y/N):

WOULD YOU LIKE TO SELECT A SOURCE APC NAME? (YIN):

WOULD YOU LIKE TO SELECT A MESSAGE TYPE? (Y/N):

WOULD YOU LIKE TO SELECT A MESSAGE CATEGORY? (YN):

A-9

ON 6201420001 November 1985

SELECTING ON THE FOLLOWING CRITERIA:

DATE RANGE: 01-JAN-0001 THRU 31-DEC-9999TIME RANGE: 12:00:00.00 THRU 12:34:59.59DESTINATION APC NAME: MRV

WOULD YOU LIKE TO CONTINUE PROCESSING SELECTED CRITERIA (Y/N):

WOULD YOU LIKE TO HAVE THE NTM LOG DISPLAYED? (Y/N): Y

A-10

ON 6201420001 November 1985

SELECTED NTM LOG RECORD 00001 PAGE 000001

DATE : 14-MAY-1985 MESSAGE SERIAL NUMBER : 0004525TIME : 12:32:47.33 PROCESSING CODE : ILOG APC : MRV MESSAGE CATEGORY : ELOG STATUS : TSOOO AP PRIORITY : 0HEADER FORMAT : A INTEGRITY CHECK FLAG : 0HEADER LENGTH : 092 LOG REQUIREMENT : 1DATA LENGTH : 0017 STATISTICS COLLECTION

FLAG : 1BINARY/NATIVE FLAG : N TEST FLAG : 0MESSAGE PRIORITY : 0 DELAY TRIGGER FLAG : 0MESSAGE TYPE : TS DELAY TIME TRIGGER :DEST AP NAME : NTNTMONITV DELAY TRIGGER CONDITON:DEST INSTANCE : 00 ORIGINAL SOURCE :NTNTMONITVOOMRVDEST APC NAME : MRV LOGICAL CHANNEL ID : 001SRC AP NAME : NTNTMRVMPU CONTINUATION INDICATOR: 0SRC INSTANCE : 00SRC APC NAME : KRV

YES - NO - PRESS ENTER -

FOR NEXT RECORD TO STOP DISPLAYING TO CONTINUE


12345 67890 12345 67890 12345 67890 12345 67890 12345 67890TSOOO

END OF DATA

YES - NO - PRESS ENTER -FOR NEXT RECORD TO STOP DISPLAYING TO CONTINUE

A-11

If 1511111 1 1 "'1111..11.1,p

ON 6201420001 November 1985


DATE : 14-MAY-1985 MESSAGE SERIAL NUMBER : 0004526TIME : 12:32:48.21 PROCESSING CODE : ILOG APC : MRV MESSAGE CATEGORY : ELOG STATUS : LVOOO AP PRIORITY : 0HEADER FORMAT : A INTEGRITY CHECK FLAG : 0HEADER LENGTH : 092 LOG REQUIREMENT : 1DATA LENGTH : 0017 STATISTICS COLLECTION

FLAG : IBINARY/NATIVE FLAG : N TEST FLAG : 0MESSAGE PRIORITY : 0 DELAY TRIGGER FLAG : 0MESSAGE TYPE : LV DELAY TIME TRIGGERBEST AP NAME : NTNTMONITV DELAY TRIGGER

CONDITIONBEST INSTANCE : 00 ORIGINAL SOURCE:NTNTMONITVOOMRVBEST APC NAME : MRV LOGICAL CHANNEL ID : 001SRC AP NAME : NTNTMRVMPU CONTINUATION INDICATOR: 0SRC INSTANCE : 00SRC APC NAME : MRV

YES - NO - PRESS ENTER -

FOR NEXT RECORD TO STOP DISPLAYING TO CONTINUE: Y


DATE : 14-MAY-1985 MESSAGE SERIAL NUMBER : 0004527TIME : 12:32:48.66 PROCESSING CODE : ILOG APC : MRV MESSAGE CATEGORY : GLOG STATUS : 0000 AP PRIORITYHEADER FORMAT : A INTEGRITY CHECK FLAGHEADER LENGTH : 092 LOG REQUIREMENTDATA LENGTH : 0000 STATISTICS COLLECTION

FLAGBINARY/NATIVE FLAG : N TEST FLAGMESSAGE PRIORITY : 1 DELAY TRIGGER FLAGMESSAGE TYPE : AL DELAY TIME TRIGGER

FLAGDEST AP NAME : NTNTMRVMPU DELAY TRIGGER

CONDITIONDEST INSTANCE ORIGINAL SOURCE:NTNTMONITVOOMRVDEST APC NAME : MRV LOGICAL CHANNEL ID : MRVSRC AP NAME : NTNTMONITV CONTINUATION INDICATOR: 0SRC INSTANCE : 00SRC APC NAME : MRVYES - NO - PRESS ENTER-FOR NEXT RECORD TO STOP DISPLAYING TO CONTINUE: NO

A-12

ON 6201420001 November 1985




NEWLOG.DAT

THE FOLLOWING FILE HAS BEEN CREATED CONTAINING 000001242 RECORDS -RPT14MAY.DAT

WOULD YOU LIKE TO RUN THE NTM LOG UTILITY AGAIN? (Y/N): N

$

A-13

''Ita~im

OM 6201420001 November 1985

EXAMPLE THREE

Select message type "AL" records having a date in the

range of 22-FEB-1985 thru 31-DEC-9999 and a time range

of 14:00:00 - 14:35:59.

Selected records are written to NTMUTIL.DAT and formatted

on file NTMRPT.DAT.

A-14

O 6201420001 November 1985

RUN NTMUTIL

**' 11TH LOG ANALYSIS UTILITY STARTED t

PLEASE ENTER THE NAME OF THE NTM LOG FILE TO BE ANALYZED:NTMLOG.DAT;1

WOULD YOU LIKE TO CREATE A FILE CONTAINING THE SELECTEDNTM LOG RECORDS? (YIN): Y

PLEASE ENTER THE UTPUT NTM LOG FILE NAME:DEFAULT OUTPUT NTM LOG FILE NAME: NTMUTIL.DAT

WOULD YOU LIKE TO CREATE A FILE CONTAINING THE SELECTEDNTM LOG RECORDS IN THE ONLINE DISPLAY FORMAT? (Y/N): T

PLEASE ENTER THE FILE NAME:DEFAULT FILE NAME: NTMRPT.DAT

WOULD YOU LIKE TO SELECT ON DATE? (Y/N): YENTER BEGINNING DATE (DD-MMM-YYYY): 22-FWE-1985

INVALID BEGINNING MONTH - FWE

ENTER BEGINNING DATE (DD-MMM-YYYY): 22-FEB-1985ENTER ENDING DATE (DD-MMM-YYYY): 22-FEB-198U

INVALID ENDING DATE - 22-FEB-198U

ENTER ENDING DATE (DD-MMM-YYYY): *ENDING DATE DEFAULTS TO : 31-DEC-9999

WOULD YOU LIKE TO SELECT ON TIME? (Y/N): YENTER BEGINNING TIME (HH:MM:SS): AA

INVALID BEGINNING TIME - AA

ENTER BEGINNING TIME (HH:MM:SS): 14:BEGINNING TIME DEFAULTS TO: 14:00:00

ENTER ENDING TIME (HH:MM:SS): 14:35ENDING TIME DEFAULTS TO: 14:35:59

WOULD YOU LIKE TO SELECT A DESTINATION AP NAME? (Y/N):

WOULD YOU LIKE TO SELECT A DESTINATION APC NAME? (Y/N):

WOULD YOU LIKE TO SELECT A SOURCE AP NAME? (Y/N):

A-15

O 6201420001 November 1985

WOULD YOU LIKE TO SELECT A SOURCE APC NAME? (YIN):

WOULD YOU LIKE TO SELECT A MESSAGE TYPE? (YIN):

ENTER MESSAGE TYPE (MAX - 2 CHAR): AL

WOULD YOU LIKE TO SELECT A MESSAGE CATEGORY? (YIN):

SELECTING ON THE FOLLOWING CRITERIA:

DATE RANGE: 22-FEB-1985 THRU 31-DEC-9999TIME RANGE: 14:00:00 THRU 14:35:59MESSAGE TYPE: AL

WOULD YOU LIKE TO HAVE THE NTH LOG DISPLAYED? (YIN):




NTMUTIL.DAT


NTMRPT. DAT

WOULD YOU LIKE TO RUN THE NTM LOG UTILITY AGAIN? (YIN): N

A-16

ON 6201420001 November 1985

APPENDIX B

INSTALL NT TABLE UTILITY

Purpose

This utility enables necessary tables to be added or deletedwith minimum effort as requirements dictate.

Initial Choices

1. HOST 1. ADD

2. APC 2. CHANGE

3. AP 3. DELETE

4. DIRECTORY 4. VIEW

5. EXIT

ADD

When adding a host or APC (Cluster), the program does notverify that the 3-character logical name chosen Is unique, onlythat it does not contain imbedded blanks. When adding a new APor directory name, the program will check to insure that thename is unique and does not contain imbedded blanks.

CHANGE

Portions of the change function are present butinoperative. When this function is added, these edit featuresshould be included:

HOST TABLE - Logical host name remains unique.Physical host name is valid.

APC TABLE - Cluster name remains unique.Logical host name is unique and valid(matches entry IS host table).

AP TABLES - Parameters within the APTTBL are valid.

DIRECTORY - Prefix or disk is valid.Name is unique and has no imbedded blanks.

B- 1

OM 6201420001 November 1985

DELETE

When deleting a host, all associated clusters and APs arealso deleted. When deleting a cluster, all associated APs aredeleted. When deleting an AP, all entries in the ACTTBL,APITBL, and APTTBL are also deleted. When deleting a directoryentry, each entry is deleted individually.

ADD, CHANGE, DELETE, or VIEW

With all functions comments and prompts are present tolead the user through the necessary program steps.

VIEW

This function displays the current tables on the screen inan easily readable format. For the view AP function, the usermust select one of four choices:

1. ACT - Authority Table

2. API - AP Information

3. APT - Characteristics

4. AUT - Authority Table

B-2

ON 6201420001 November 1985

APPENDIX C

ERRLOG UTILITYSI

Purpose

This utility provides a tool to list and format the ERRLOGfile, which makes it somewhat easier to analyse. Date and timecan be entered to analyze. Date and time can be entered toanalyze specific ERRLOG entries.

Program Prompts

FILE MAKE TO BE ANALYZED? DEFAULT - ERRLOG.DAT

OUTPUT FILE TO BE CREATED? YES/NO IF YES A FILENAME WILL BEREQUESTED.

SELECTION CRITERIA? DATE/TIME IF ERRLOG FOR A SPECIFICTIME RANGE IS DESIRED IT CANBE ENTERED AT THIS TIME.

DESTINATION APPLICATION NAME? IF THE REPLY IS 'Y' ENTER 10YES/NO CHARACTER DESTINATION

APPLICATION NAME. DEFAULTIS NTNTMONITV.

DESTINATION CLUSTER NAME? IF THE REPLY IS 'Y' ENTER A 3CHARACTER APPLICATION CLUSTERNAME. DEFAULT IS 'MRV'.

SOURCE APPLICATION NAME? YES/NO IF THE REPLY IS 'Y' ENTER A10 CHARACTER SOURCEAPPLICATION PROGRAM NAME.DEFAULT IS 'NTNTMONITV'.

SOURCE APPLICATION PROGRAM IF THE REPLY IS 'Y' ENTER ACLUSTER NAME? 3 CHARACTER SOURCE PROGRAM

APPLICATION CLUSTER NAME.DEFAULT IS 'MRV'.

WOULD YOU LIKE TO CONTINUE? IF THE REPLY IS 'Y' PROGRAMCONTINUES.

'N' PROGRAMTERMINATES.

C-1

ON 6201420001 November 1985

IS THE ERRLOG TO BE DISPLAYED? IF THE REPLY IS 'Y' FORMATTEDOUTPUTAPPEARS ONTERMINAL.

'N' NO TERMINALOUTPUT.

U.S.CLoveynrlttent Printing OJffice; 1 987 -/48-061 /6oq08 C-2

D~r/ c

INTEGRATED INFORMATION SUPPORT UNCLSSIFED …Mr. Myron Hurlbut of Industrial Automation Systems...

Documents

Transcript of INTEGRATED INFORMATION SUPPORT UNCLSSIFED …Mr. Myron Hurlbut of Industrial Automation Systems...