ICEM_Notes_and_Installation_Instructions ICEM Notes And Installation Instructions
User Manual: ICEM_Notes_and_Installation_Instructions
Open the PDF directly: View PDF .
Page Count: 1542
Download | |
Open PDF In Browser | View PDF |
CON T R 0 L .• 1> DAT A C.O R P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 03/11/88 3B021 2043520012 102263 PAGE 1 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) SHIP TO SOLD TO ***************** * PACKING COPY * ***************** COMPUTER PERIPHERALS INC. ATTN: CHARLIE MARTOCELLO 2621 VAN BUREN AVE. NORRISTOWN, PA 19403 COMPUTER PERIPHERALS INC. ATTN: CHARLIE MARTOCELLO 2621 VAN BUREN AVE. NORRISTOWN, PA 19403 CUSTOMER P.O. TRANSMIT NO SALES REP DEPT ACCOUNT SWEENEY SELLING OFFICE INSTALLING OFFICE SYSTEM TYPE SYSTEM SERIAL FXX FXX CY830 00618 PRODUCT NUMBER RELEASE LEVEL H830P-010 678 DIVISION CODE PHAFAC 0090/ PRODUCT NAME VER PROD QTY TIELINE/NP NOS 2 252 1 COMPONENT NUMBER COMPONENT NAME P16004 15190762AE 15190132AD TIELINE/NP*N2-678 252 600 TIELINE/NP IHB IH TIELINE OP GUIDE OP PROJECT NUMBER FACILITY CODE VER COMP TY COMP UNIT TYPE MN QTY PRICE EXTND EXTND CP BACKPRICE QTY AV ORDER 0.00 0.00 0.00 1 1 1 ORDER PROCESSING CHARGE 0.00 3 PRODUCT CHARGE 0.00 M M 1 1 1 0.00 0.00 0.00 TOTAL ORDER PROCESSING CHARGE 0.00 3 TOTAL PRODUCT CHARGE 0.00 1 TOTAL ORDER CHARGE 0.00 S L L U.S. DOLLARS MISCELLANEOUS CONTENTS: . FREIGHT SHIPPED FROM SMD 1227-7240 ROUTING- SURFACE AIR CONTROL DATA CORPORATION SOFTWARE MANUFACTURING AND DIST. 4201 N. LEXINGTON AVE. ARDEN HILLS, MINNESOTA 55126-6198 VIA NUMBER OF PIECES PACKED BY GROSS WEIGHT FREIGHT COST BILL OF LADING -_.. _---_........ __.- _- _._ _ - - - - - - - - - - - - - - - - _ . _ - _ . _ - - ---_._ .... .......... ... ................. _-_. __._.... _ - - - - - - - - - _..._._-----_ ..- .... ' '''1 " ." '" CON T R 0 L DAT A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 03/11/88 3B021 2043520012 102263 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) 001 - 600 . -----_. __ ._ ......_._.. _ . _ - - - - - - PAGE 2 .... CON T R 0 L :1'" ... DATE ASSEMBLY NO 03/11/88 ~B020 DAT A COR P 0 RAT ION CORPORATE FILE NUMBER SCMA 2043520008 102262A PAGE SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) SHIP TO SOLD TO 1 ***************** COpy * * PACKING ***************** COMPUTER PERIPHERAL INC. ATTN: CHARLIE MARTOCELLO 2621 VAN BUREN AVE. NORRISTOWN, PA 19403 CUSTOMER P.O. TRANSMIT COMPUTER PERIPHERAL INC. ATTN: CHARLIE MARTOCELLO 2621 VAN BUREN AVE. NORRISTOWN, PA 19403 NO DEPT SALES REP ACCOUNT MCSWEENEY SELLING OFFICE INSTALLING OFFICE PRODUCT NUMBER RELEASE LEVEL 53591952C 688 SYSTEM TYPE SYSTEM SERIAL CY830 618 DIVISION CODE PHAFAC 0150/ PRODUCT NAME VER PROD QTY 825/830/830A FK 008 1 COMPONENT NUMBER COMPONENT NAME 60456530R 60457180AH 60469390L 12361091AP 12361110AR 12361113AK 12361116AP 19267182AP 19267186AL 21989638AL 21989639AP 53140094AT 20298600 20298605 20298670 MSL15X REF MAN CIP USER'S HDBK MSL15X MI REF MAN MSL151 EXEC PL MSL151 CATALOG MF LCN-NAD DOC CMSE COMMON PL MSL151 II DIAG PL EXCH PROG LIST MSL15X COMN MS PL MSL15X MI PL MALET DOCUMENT PL 825 FCA CHART 830 FCA CHART 834/7255 FCA CHT VER COMP TY COMP UNIT TYPE MN QTY PRICE IH IH IH FICH FICH FICH FICH FICH FICH FICH FICH FICH FCO FCO FCO P M P M M M M M M M M M PROJECT NUMBER FACILITY CODE 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 EXTND EXTND CP BACKPRICE QTY AV ORDER 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 L S S S S S S S S S S S S SHIPPED FROM FREIGHT SMD 1227-7240 ROUTING- SURFACE AIR CONTROL DATA CORPORATION SOFTWARE MANUFACTURING AND DIST. 4201 N. LEXINGTON AVE. ARDEN HILLS, MINNESOTA 55126-6198 VIA NUMBER OF PIECES PACKED BY GROSS WEIGHT FREIGHT COST F.LADING ! L L CON T R 0 L DAT A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER 03/11/88 3B020 2043520008 SCMA PAGE 2 102262A SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) PRODUCT NUMBER RELEASE LEVEL 53591952C 688 PRODUCT NAME VER PROD QTY 825/830/830A FK 008 1 COMPONENT NUMBER COMPONENT NAME VER COMP TY COMP UNIT TYPE MN QTY PRICE 22110266 22697034 53595810 53595895 67185379 SMD800371 53368864N 698 FCA CHART 7990 MASSTOR FCA 836/7255 FCA CHT CDCNET FCA CHART 639/7221 FCA CHT CIP SRB W/MSL CIP825-830A W/MSL 008 FCO FCO FCO FCO FCO SSD PE A EXTND EXTND CP BACKPRICE QTY AV ORDER S S S S S S l' S 0.00 0.00 0.00 0.00 0.00 0.00 0.00 1 1 1 1 1 2 ORDER PROCESSING CHARGE 0.00 23 PRODUCT CHARGE 0.00 1 1 1 1 1 2 1 0.00 0.00 0.00 0.00 0.00 0.00 0.00 TOTAL ORDER PROCESSING CHARGE 0.00 23 TOTAL PRODUCT CHARGE 0.00 1 TOTAL ORDER CHARGE 0.00 U.S. DOLLARS MISCELLANEOUS CONTENTS: 001 - 2400 ---_ ... _...._--------_....._"".__._--"... _...._.. _.._"-_ .._._-- ....-..- ............. _... _..... , .... ... "_._.'-' .. .. _."-,,, .. _, ........... .. _.-_._._---------_."-,, .._"_ .. _ - - - - - "' , ,, '\' , CON T R 0 L .. 1 DAT A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 02/11/88 3B022 2043520008 102264 PAGE SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) SHIP TO SOLD TO 1 ***************** * PACKING COPY * ***************** COMPUTER PERIPHERALS INC. ATTN: CHARLIE MARTOCELLO 2621 VAN BUREN AVE. NORRISTOWN, PA 19403 COMPUTER PERIPHERALS INC. ATTN: CHARLIE MARTOCELLO 2621 VAN BUREN AVE. NORRISTOWN, PA 19403 CUSTOMER P.O. TRANSMIT DEPT SALES REP NO ACCOUNT MCSWEENEY SELLING OFFICE INSTALLING OFFICE EXX EXX PRODUCT NUMBER RELEASE LEVEL H830-160 688 SYSTEM TYPE SYSTEM SERIAL CY830 00618 DIVISION CODE PROJECT NUMBER FACILITY CODE PHAFAC 0150/ PRODUCT NAME VER PROD QTY UNIPLOT 3 LIB&EXE 3.2 1 COMPONENT NUMBER COMPONENT NAME VER COMP TY COMP UNIT TYPE MN QTY PRICE REL83C SMD131742 UV32R10 UNIPLOT SRB RIO 600 RIO MEMO EXTND EXTND CP BACKPRICE QTY AV ORDER 0.00 0.00 1 1 ORDER PROCESSING CHARGE 0.00 2 PRODUCT CHARGE 0.00 H830-162 UNI TEK 4XXX DD 688 1 1 3.2 0.00 0.00 1 0.00 0.00 1 1 ORDER PROCESSING CHARGE 0.00 2 PRODUCT CHARGE 0.00 REL84C SMD131578 TEK1087 TEKTRONIX DD UG FREIGHT RIO 600 MEMO S S 1 1 0.00 0.00 S S SHIPPED FROM SMD 1227-7240 ROUTING- SURFACE AIR CONTROL DATA CORPORATION SOFTWARE MANUFACTURING AND DIST. 4201 N. LEXINGTON AVE. ARDEN HILLS, MINNESOTA 55126-6198 VIA NUMBER OF PIECES PACKED BY GROSS WEIGHT FREIGHT COST BILL OF LADING • CON T R 0 L I DA T A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 0~llJ./88 3B022 2043520008 102264 PAGE 2 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) PRODUCT NUMBER RELEASE LEVEL H830-163 688 PRODUCT NAME VER PROD QTY BENSON 92/93XX DD 3.2 1 COMPONENT NUMBER COMPONENT NAME VER COMP TY COMP UNIT TYPE MN QTY PRICE REL86C MISCI087 RIO 600 0.00 1 ORDER PROCESSING CHARGE 0.00 1 PRODUCT CHARGE 0.00 TOTAL ORDER PROCESSING CHARGE 0.00 5 TOTAL PRODUCT CHARGE 0.00 3 TOTAL ORDER CHARGE MISCELLANEOUS CONTENTS: 003 1 0.00 EXTND EXTND CP BACKPRICE QTY AV ORDER 600 _ -----"... _.__ .. .. _" ..• _ - - - - - - - - - 0.00 S U.S. DOLLARS ....... &J c::\ CONTR,.OL DATA \:::J r:!J CORPOf\ATlON SOFTWARE AVAILABILITY BULLETIN Distribution List For CDC CYBER 180/170/70L/6000 SAB No. 664 July 26, 1988 lCEM lGES TRANSLATOR UNDER NOS 2 (Level 688B Release) A. ABSTRACT lCEM lGES Translator Version 2.23 has been updated under NOS 2.6.1 level 700. This release includes 180, A and E series systems. Depending upon the will apply (Refer to tables 2 and 3 for appropriate to release level 688B and verified to execute support for the 6000, CDC CYBER 70, 17X, 170, hardware mainframe, different product mnnbers product numbers.) B. DESCRIPTION OF RELEASE lCEM lGES Translator Version 2.23 is a product that allows you to read graphic and non-graphic data in a format that conforms with the Initial Graphic Exchange Specification (IGES) Version 2.0 and Version 3.0 and write that data in lGES Version 2.0 format. The lGES standard is published by the United States Government's National Bureau of Standards. The IGES standard allows three possible data formats - binary, compressed ASCII and ASCII. The lGES Version 2.23 product supports the ASCII version. The software product is composed of two major programs with auxiliary programs and procedures, to support various user choice options. The Version 2.23 input program reads an IGES standard file, which has been converted from ASCII to 6/12 format, and outputs an IPARTD file suitable for lCEM DDN V!. 65. The Version 2.23 output program reads an lCEM DDN V!. 65 IPARTD file and outputs an IGES standard fi1 e in 6/12 format sui table for conversion to ASCII. Auxil iary programs and/ or procedures convert the IGES Standard Files from ASCII to 6/12 or from 6/12 to ASCII. The user has little direct control over the processing other than choosing the option as the programs are intended for batch operation. ,C) lCEM lGES Translator V2.23 has been verified to run with lCEM DDN V1.65. C. PUBLICATIONS There are no new or updated publications pertaining to this release. D. ORDERING INFORMATION These update materials are now available. These update materials will. be sent existing licensed domestic customers with Support Service. International reference the separately enclosed ordering instructions for details on how updates. Licensed software products and update materials are available only have entered into a contractual agreement with Control Data for the use of these automatically to customers should to order these to customers who products. Customers not currently licensed for these update products, who place new orders through their sales representative at this time, and who wish to receive level 688B as their initial delivery, should specify the desired level in their order. New software orders must be covered by a license agreement which lists each product explicitly. ··0 Distribution List For CDC CYBER 180/170/70L/6000 SAB No. 664 Page 2 TABLE 1. Product Namet SUMMARY LEVEL 688B Nominal Release Level Identifiertt Level of Lates t Available Media PSRs at Level New Features :---------------------------------------------------------------------------------------------------------------: : ICEM IGES TRANSLATOR 688B 688B 688 No :---------------------------------------------------------------------------------------------------------------: tRefer to Tables 2 and 3 for applicable product numbers. Contact your Control Data sales representative to ensure correct product number for appropriate mainframe. The product listed in this table is BINARY only. ttThis column indicates the latest release at which code and/or documentation changes have been made for each product shown. c" o "0 J Distribution List For CDC CYBER 180/170/70L/6000 SAB No. 664 Page 3 TABLE 2. CDC CYBER 170-700, 170-800, AND 180-800 SERIES MAINFRAMES MAINFRAME 720 730 740 : 176 :: 760 :-4XX :: 810 : 815 :: 810A: 750 825 .. 830 835 830A: 840 : 845 840A: 850 : 855 850A: 860 : 865 860A: 870A: 875 : 990 :990E :995E :------------------------------------------------------------------------------------------------------------------: PRODUCT NUMBER :D720 :D730 :D740 :D750 :D760 :D770 ::D810 :D815 :D825 :D830 :D835 :D840 :D845 :D850 :D855 :D860 :D865 :D875 :D990 :H720 :H730 :H740 :H750 :H760 :H770 ::H810 :H815 :H825 :H830 :H835 :H840 :H845 :H850 :H855 :H860 :H865 :H875 :H990 PRODUCT NAME :---------------------------------------------------------------------------------------------------------------------------------------------------------: :-122 :-122 :-122 :-122 :-122 :-122 ::-122 :-122 :-122 :-122 :-122 :-122 :-122 :-122 :-122 :-122 :-122 :-122 :-122 lCEM IGES TRANSLATOR :---------------------------------------------------------------------------------------------------------------------------------------------------------: TABLE 3. CDC 6000, CYBER 70 AND 17X SERIES MAINFRAMES MAINFRAME 6000 CY70 171 172 173 PRODUCT NAME D521 H521 D521 H521 D521 H521 lCEM lGES TRANSLATOR -560 174 175 -100 175 -200 175 -300 -xx 176 D521 H521 D521 H521 D521 H521 :---------------------------------------------------------------: PRODUCT NUMBER D521 D521 H521 : H521 :------------------------------------------------------------------------------------------------------------------: -560 -560 -560 -560 -560 -560 -560 Ci CONTROL DATA CORPORATION ARDEN HILLS PROGR. DIV SW MANUFACTURING & DIST. FIELD AVAILABILITY SUMMARY FOR APPLICATIONS UNDER NOS 2 19-CONFIGURATION MANAGEMENT-88 NO. REV. DATE PAGE 77987679 078 07/11/88 1 OF 6 j PRODUCT DESCRIPTION SYSTEM SOFTWARE - Release Dates (Note NOS 2 - Operating System COMPATIBLE RELEASE LEVELS (by columns) AND ASSOCIATED VERSIONS 1) NOS 2 - Produc t Set NOS 2 - Networks Products APPLICATIONS UNDER NOS 2 (Note 2) 5870 LASER PRINTER APPLICATION: HOST FORMS DESCRIPTION LANGUAGE (HFDL) ELECTRONIC PRINTER IMAGE CONSTRUCTION (EPIC) XEROX INTEGRATED COMPOSITION SOF'lWARE (XICS) ADAMS ANSYS APEX IV APT-IV ASPEC CAIl10ULD 2D CAIMOULD 3D CALC OMP HCBS DEVICE DRIVER (PS) CDC 721 POST PROCESSOR (TIGS) CDC-CVIF CDCNET PACER CDCNET SUPPORT TOOLS CHROMATICS 1599 PP (TIGS) CONCURRENT VERSION RECORD MANAGER (PS) CONNECT DISTRIBUTED APPLICATION DEVELOPER TOOLKIT CONTOURING SYSTEM (PS) CONTROL DATA CONNECT FOR IBM PC CONTROL DATA CONNECT FOR MACINTOSH CUTDATA CYBIL (170 CODE GENERATOR) 04/87 678 V2.5.2 670 670 09/87 688 V2.5.3 688 688 647 647 V2.1C V2.1C 647 647 V3.0 V3.0 647 647 V5.0 V5.0 630A 630A VI.O VI.O 664 664 V4.2B V4.2B 580 580 VI.O VI. 0 617A 617A V2.2 V2.2 642 642 V8M7 V8M7 647A 647A VI.O VI.O 647A 647A V1.0 Vl.O 664 688 V5.04 V5.04 617 617 VI. 4. 2 VI. 4.2 596A 596A V1.1 VI. 1 688 --V4.4 --670 670 V2.1 V2.1 617 617 VI. 4. 2 VI. 4. 2 647 --V2.4.3 --688 688 VI.2 VI. 2 664 664 V4.07 V4.07 688 688 VI.3 V1.3 664 664 VI. 1 VI. 1 647A 647A V3.0 V3.0 617B 617B V2.1 V2.1 Ij 04/88 700 V2.6.1 688 688 ------------- 630A VI.O 664 V4.2B 580 VI.O 617A V2.2 642 V8M7 647A VI.O 647A VI.O 688 V5.04 617 V1.4.2 596A V1.1 ----- 670 V2.1 617 Vl.4.2 ----- 688 VI.2 664 V4.07 ----- 700 V2.0 647A V3.0 617B V2.1 THIS DOCUMENT SUMMARIZES AVAILABILITY INFORMATION ANNOUNCED IN SOF'lWARE AVAILABILITY BULLETINS (SABs) • IT IS NOT A STANDALONE ANNOUNCEMENT .DOCUMENT. PLEASE REFERENCE THE NOTES ON THE LAST PAGE OF THIS FIELD AVAILABILITY SUMMARY. o 9347H - 0327H/0328H _.... __ .____ .u. __ .. _ _ _ _ _ _ _ _ __ - - - - - - - - _ .. _ - -.._ - - - - - _ . __ _.__. _ - -.. CONTROL DATA CORPORATION ARDEN HILLS PROGR. DIV SW MANUFACTURING & DIST. FIELD AVAILABILITY SUMMARY FOR APPLICATIONS UNDER NOS 2 19-CONFIGURATION MANAGEMENT-88 PRODUCT DESCRIPTION SYSTEM SOFTWARE - Release Dates (Note 1) NOS 2 - Operating System NOS 2 - Product Set NOS 2 - Networks Products APPLICATIONS UNDER NOS 2 (Note 2) CYBIL (P-CODE GENERATOR) DI-3000 EXTENDED (PS) DI-TEXTPRO (PS) DRAM DUCT EDEN COMMON ACCESS SUPPORT SUBSYSTEM EDEN GATEWAY SUBSYSTEM EDEN STUDENT REGISTRATION SUBSYSTEM EDEN BURSAR SUBSYSTEM EDEN STUDENT AID MANAGEMENT SUBSYSTEM EDEN ALUMNI SUBSYSTEM GPSS V GRAFMAKER (PS) GTICES/STRUDL GTTABLE HASCO HEWLETT-PACKARD 7221 PLOTTER (PS) HEWLETT-PACKARD 7470A PLOTTER (PS) HEWLETT-PACKARD 7550A PLOTTER (PS) HOTSPOT (PS) IBM PERSONAL COMPUTER DEVICE DRIVER (PS) ICEM ADVANCED DESIGN UPGRADE ICEM BEND ICEM CAM-POST NO. REV. DATE PAGE 77987679 078 07/11/88 2 OF 6 COMPATIBLE RELEASE LEVELS (by columns) AND ASSOCIATED VERSIONS 04/87 678 V2.5.2 670 670 09/87 688 V2.5.3 688 688 04/88 700 V2.6.1 688 688 617B V2.1 664 V5.04 617B V2.1 688 V5.05 688 V1.01 664 VI. 1 647A V4.2 617B V2.1 688 V5.0S 688 V1.01 664 VI. 1 647A V4.2 ----- 664 VI. 1 647A V4.2 678 VI.1 678 V1.1 678 VI.1 678 VI.l 678 VI.1 678 VI.1 642 VI.4 664 V4.03 617 V85.05 562 V81.02 664 Vl.l 664 V5.04 664 V5.04 664 V5.04 596 642 VI. 4 664 V4.03 617 V85.05 562 V81.02 664 VI. 1 688 V5.04 688 V5.04 688 V5.04 596 642 V1.4 664 V4.03 617 V85. OS 562 V81.02 664 VI. 1 688 V5.04 688 V5.04 688 V5.04 --- ----- 664 V5.04 678B Vl.64 664 VI.2 678 V9.30 688 V5.04 688A Vl.65 664 VI. 2 678 V9.30 688 V5.04 688A VI. 65 664 VI.2 678 V9.30 --- --------------- ----------- ------------------------- THIS DOCUMENT SUMMARIZES AVAILABILITY INFORMATION ANNOUNCED IN SOFTWARE AVAILABILITY (SABs). IT IS NOT A STANDALONE ANNOUNCEMENT DOCUMENT. PLEASE REFERENCE THE NOTES ON OF THIS FIELD AVAILABILITY SUMMARY. BULLETINS T PAGE I\. ~, ( "--- ' 9347H - 0327H/0328H CONTROL DATA CORPORATION ARDEN HILLS PROGR. DIV SW MANUFACTURING & DIST. FIELD AVAILABILITY SUMMARY FOR APPLICATIONS UNDER NOS 2 19-CONFIGURATION MANAGEMENT-88 PRODUCT DESCRIPTION SYSTElf SOFTWARE - Release Dates (Note 1) NOS 2 - Operating System NOS 2 - Product Set NOS 2 - Networks Products APPLICATIONS UNDER NOS 2 (Note 2) ICEM CAM-PUNCH ICEM DATA MIGRATION UTILITY ICEM DESIGN/DRAFTING ICEM DESIGN/DRAFTING/ADVANCED DESIGN/ NUMERICAL CONTROL PACKAGE ICEM DESIGN/DRAFTING/ADVANCED DESIGN PACKAGE ICEM ENGINEERING DATA LIBRARY ICEM FACILITIES ICEM HYDRAULICS ICEM IGES TRANSLATOR ICEM KINEMATICS ICEM NUMERICAL CONTROL UPGRADE ICEM PLASTIMOULD ICEM SCHEMATICS ICEM SOLID ANALYS IS ICEM SOLID MODELER IMSL VlO INFORMATION ANALYSIS SUPPORT TOOL (PS) INFORMATION MANAGEMENT FAC 2 INFORMATION PROCESSING FAMILY IPF/CDCS LINK LINCAGES METAFILE (Stand-alone) TRANSLATOR (PS) 77987679 078 07/11 /88 3 OF 6 CCMPATIBLE RELEASE LEVELS (by columns) AND ASSOCIATED VERSIONS 04/87 678 V2.5.2 670 670 09/87 688 V2.5.3 688 688 04/88 700 V2.6.l 688 688 647A V2.0 688 --- V2.0.0 678B 688A Vl.64 Vl.65 688A 678B Vl.64 Vl.65 678B 688A Vl.64 Vl.65 678 688 VI. 2. 6 Vl.2.7 678 678 Vl.4l Vl.4l 664 664 Vl.3 Vl.3 688B 678 V2.2l V2.23 664 664 Vl.O Vl.O 678B 688A Vl.64 Vl.65 664 664 VI.l VI.l 642A 642A Vl.15 Vl.15 664 664 Vl.13 Vl.13 664 664 Vl.13 Vl.13 647A V2.0 688 V2.0.0 688A Vl.65 688A Vl.65 688A Vl.65 688A Vl.2.7 678 Vl.4l 664 Vl.3 688B V2.23 664 VI.O 688A Vl.65 664 Vl.l 642A Vl.15 664 Vl.13 664 Vl.13 647A V2.0 --- ----- ICEM TEKROUTE NO. REV. DATE PAGE 678 VlO.O 670 VI.2 ----- 647 V2.6 642 VI.O 664 VI. 2 664 V5.02 --- --- 678 VlO.O 670 VI. 2 ----- 678 VlO.O 670 Vl.2 ----- --- --- 647 V2.6 642 Vl.O 664 VI. 2 688B V5.03 647 V2.6 ----- 664 VI. 2 688B V5.03 THIS DOCUMENT SUMMARIZES AVAILABILITY INFORMATION ANNOUNCED IN SOFTWARE AVAILABILITY (SABs) • IT IS NOT A STANDALONE ANNOUNCEMENT DOCUMENT. PLEASE REFERENCE THE OF THIS FIELD AVAILABILITY SUMMARY. o 9347H - 0327H/0328H . _ - - - - - - - - - - _ . _ - - _.. __ __..- _ ..._._--_._._...... . ... .. _-----_. _ CONTROL DATA CORPORATION ARDEN HILLS· PROGR. DIV SW MANUFACTURING & DIST. FIELD AVAILABILITY SUMMARY FOR APPLICATIONS UNDER NOS 2 19-CONFIGURATION MANAGEMENT-88 PRODUCT DESCRIPTION SYSTEM SOFTWARE - Release Dates (Note 1) NOS 2 - Operating System NOS 2 - Product Set NOS 2 - Networks Products APPLICATIONS UNDER NOS 2 (Note 2) METAFILE SYSTEM (PS) MIDAS-BASE PACK MIDAS-DESIGN VERIFICATION MIDAS DESIGNER WORKSTATION-BASE MIDAS DESIGNER WORKSTATION-VLSI6260 MIDAS DESIGNER WORKSTATION-VLSI6261 MIDAS-GATE ARRAY LAYOUT MIDAS LAYOUT WORKSTATION-APOLLO MIDAS LAYOUT WORKSTATION-ORCATECH MIDAS-TEST GENERATION MIDAS-VLSI6260 TECHNOLOGY LIBRARY MIDAS-VLSI6261 TECHNOLOGY LIBRARY MOLDCOOL II MOLDFLOR('TION SOFTWARE AVAILABILITY BULLETIN Distribution List For CDC CYBER 180/170 /70L/6000 SAB No. 588 January 20, 1988 lCEM lGES TRANSlATOR UNDER NOS 2 (Level 688 Release) A. ABSTRACT lCEM lGES Translator Version 2.22 has been updated to release level 688. This release includes support for the 6000, CDC CYBER 70, 17X, 170, 180, A and E series systems. Depending upon the hardware mainframe, different product numbers will apply (Refer to tables 3 and 4 for appropriate product numbers~) This product is now available. B. DES CRIPTION OF RELEASE lCEM lGES Translator Version 2.22 is a product that allows you to read graphic and non-graphic data in a fonnat that confonns with the Initial Graphic Exchange Specification (IGES) Version 2.0 and Version 3.0 and write that data in lGES Version 2.0 format. The lGES standard is publ ished by the United States Government's National Bureau of Standards. The IGES standard allows three possible data formats - binary, compressed ASCII and ASCII. The lGES Versi on 2.22 product supports the ASCII version. The software product is composed of two major programs with auxiliary programs and procedures, to support various user choice options. The Version 2.22 input program reads an IGES standard file, which has been converted from ASCII to 6/12 format, and outputs an IPARTD file suitable for lCEM DDN VI. 64. The Version 2.22 output program reads an lCEM DDN VI. 64 IPARTD file and outputs an lGES standard file in 6/12 format suitable for conversion to ASCII. Auxiliary programs and/or procedures convert the IGES Standard Files from ASCII to 6/12 or from 6/12 to ASCII. The us er has little direct control over the processing other than choosing the option as the programs are intended for batch operation. o Version 2.22 now reads both lGES 2.0 and 3.0 formats. PSR corrective code has been added. lCEM lGES Translator V2.22 has been verified to run with lCEM DDN V1.64. C. PUBLICATIONS There are no new or updated publications pertaining to this release. D. ORDERING INFORMATION These update materials are now available. These update materials will be sent existing licensed domestic customers with Support Service. International reference the separately enclosed ordering instructions for details on how updates. Licensed software products and update materials are available only have entered into a contractual agreement with Control Data for the use of these automatically to customers should to order these to customers who products. Customers not currently licensed for these upda.te products, who place new orders through their sales representative at this time, and who wish ·to receive level 688 as their initial delivery, should specify the desired level in their order. New software orders must be covered by a license agreement which lists each product explicitly. o - - - - - - - - - _....._....._._.•.. - Distribution List For CDC CYBER 180/170 /70L/6000 SAB No. 588 Page 2 TABLE 2. Product Namet ,' ........., SUMMARY LEVEL 688 Nominal Release Level Identifiertt Level of Latest Available Media PSRs at Level New Features :---------------------------------------------------------------------------------------------------------------: : ICEM IGES TRANSIATOR 688 688 688 Yes :------------------------~----------------------------- ---------------------------------------------------------: tRefer to Tables 3 and 4 for applicable product numbers. Contact your Control Data sales representative to ensure correct product number for appropriate mainframe. The product listed in this table is BINARY only. ttThis column indicates the latest release at which code and/or documentation changes have been made for each product shown. o o ARDEN HILLS PROGR. DIV SW MANUFACTURING & DIST. CONTROL DATA CORPORATION FIELD AVAILABILITY SUMMARY NO. REV. DATE PAGE FOR APPLICATIONS UNDER NOS 2 19-CONFIGURATION MANAGEMENT-88 COMPATIBLE RELEASE LEVELS (by columns) AND ASSOCIATED VERSIONS PRODUCT DESCRIPTION SYSTEM SOFTWARE - Release Dates (Note 1) NOS 2 - Operating System NOS 2 - Product Set NOS 2 - Networks Products APPLICATIONS UNDER NOS 2 (Note 2) 5870 LASER PRINTER APPLICATION: HOST FORMS DESCRIPTION LANGUAGE (HFDL) ELECTRONIC PRINTER IMAGE CONSTRUCTION (EPIC) XEROX INTEGRATED COMPOSITION SOFTWARE (XICS) ADAMS ANSYS APEX IV APT-IV ASPEC o CADMOULD 20 CADMOULD 3D CDC 721 POST PROCESSOR (TIGS) CDC-CVIF CDCNET PACER CDCNET SUPPORT TOOLS CHROMATICS 1599 PP (TIGS) CONNECT DISTRIBUTED APPLICATION DEVELOPER TOOLKIT CONTROL DATA CONNECT FOR IBM PC CONTROL DATA CONNECT FOR MACINTOSH CUTDATA CYBIL (170 CODE GENERATOR) CYBIL (P-CODE GENERATOR) DRAM DUCT o 09/86 664 V2.S.1 650 664 12/86 670 V2.S.1 670 670 04/87 678 V2.S.2 670 670 09/87 688 V2.S.3 688 688 647 647 647 647 V2.1C V2.1C V2.1C V2.1C 647 647 647 647 V3.0 V3.0 V3.0 V3.0 647 647 647 647 V5.0 V5.0 V5.0 V5.0 630A 630A 630A 630A VI.O V1.0 V1.0 V1.0 664 664 664 664 V4.2B V4.2B V4.2B V4.2B 580 580 580 580 V1.0 V1.0 V1.0 V1.0 617A 617A 617A 617A V2.2 V2.2 V2.2 V2.2 642 642 642 642 V8M7 V8M7 V8M7 V8M7 647A 647A . 647A 647A V1.0 V1.0 V1.0 VI.O 647A 647A 647A 647A V1.0 V1.0 V1.0 VI.O 617 617 617 617 VI.4.2 VI.4.2 VI. 4. 2 V1.4.2 596A S96A 596A 596A V1.1 VI.1 VI.1 VI.1 688 ------V4.4 ------664 670 670 670 V2.1 V2.1 V2.1 V2.1 617 617 617 617 VI.4.2 V1.4.2 V1.4.2 V1.4.2 . 647 --647 --VI.O V1.0 ----688 688 688 688 V1.3 V1.3 V1.3 V1.3 664 664 664 664 V1.1 V1.1 V1.1 VI.1 647A 647A 647A 647A V3.0 V3.0 V3.0 V3.0 617B 617B 617B 617B V2.1 V2.1 V2.1 V2.1 617B 617B 617B 617B V2.1 V2.1 V2.1 V2.1 664 664 664 664 V1.1 V1.1 V1.1 VI.1 647A 647A 647A 647A V4.2 V4.2 V4.2 V4.2 THIS DOCUMENT SUMMARIZES AVAILABILITY INFORMATION ANNOUNCED IN SOFTWARE (SAB s ) • IT IS NOT A STANDALONE ANNOUNCEMENT DOCUMENT. PLEASE REFERENCE THE OF THIS FIELD AVAILABILITY SUMMARY. 9347H - 0327H/0328H 77987679 069 12/21/87 1 OF 5 ARDEN HILLS PROGR. DIV SW MANUFACTURING & DIST. CONTROL DATA CORPORATION ~ FIELD AVAILABILITY SUMMARY NO. REV. DATE PAGE FOR APPLICATIONS UNDER NOS 2 19-CONFIGURATION MANAGEMENT-88 NOS 2 - Product Set NOS 2 - Networks Products APPLICATIONS UNDER NOS 2 (Note 2) EDEN COMMON ACCESS SUPPORT SUBSYSTEM EDEN GATEWAY SUBSYSTEM EDEN STUDENT REGISTRATION SUBSYSTEM EDEN BURSAR SUBSYSTEM EDEN STUDENT AID MANAGEMENT SUBSYSTEM EDEN ALUMNI SUBSYSTEM GPSS V GTICES/STRUDL GTTABLE HASCO H/I, NICOLET, ZETA, BENSON PP (UNI) ICEM ADVANCED DESIGN UPGRADE ICEM BEND ICEM CAM-POST ICEM CAM-PUNCH ICEM DESIGN/DRAFTING ICEM DESIGN/DRAFTING/ADVANCED DESIGN/ NUMERICAL CONTROL PACKAGE ICEM DESIGN/DRAFTING/ADVANCED DESIGN PACKAGE ICEM ENGINEERING DATA LIBRARY ICEM FACILITIES ICEM HYDRAULICS ICEM IGES TRANSLATOR ICEM KINEMATICS ICEM NUMERICAL CONTROL UPGRADE \ 09/86 664 V2.S.l 6S0 664 12/86 670 V2.S.1 670 670 04/87 678 V2.S.2 670 670 678 647 --Vl.O Vl.l -647 678 --Vl.O Vl.1 ---647 678 --Vl.O Vl.l -647 678 --Vl.O Vl.l 647 678 .. VI.O Vl.1 647 678 --. -VI.O VI.l 642 642 642 Vl.4 VI.4 Vl.4 617 617 617 V8S.0S V8S.0S V8S.0S S62 S62 S62 V8l.02 V8l.02 V8l.02 664 664 664 Vl.l Vl.l Vl.l 647 647 647 V3.2 V3.2 V3.2 664 664 678B Vl.62 Vl.62 Vl.64 664 664 664 V1.2 VI.2 V1.2 647A 647A 678 V9.2l V9.30 V9.2l 647A 647A 647A V2.0 V2.0 V2.0 664 664 678B yl.62 Vl.62 V1.64 664 664 678B VI.62 Vl.62 Vl.64 664 664 678B V1.62 Vl.62 V1.64 642A 664 678 VI. 2. 3 VI. 2. S VI. 2. 6 664 664 678 V1.4 Vl.4 VI.41 664 664 664 V1.3 V1.3 Vl.3 664 664 678 V2.2 V2.2 V2.21 664 664 664 VI.O Vl.0 Vl.O 664 664 678B Vl.62 Vl.62 VI.64 ---_- 09/87 688 V2.S.3 688 688 -----.. ---. -------.----.. 642 Vl.4 617 V8S.0S S62 V8l.02 664 VI.I 647 V3.2 678B V1.64 664 V1.2 678 V9.30 647A V2.0 678B Vl.64 678B Vl.64 678B VI. 64 678 Vl.2.6 678 VI.41 664 Vl.3 688 V2.22 664 Vl.O 678B Vl.64 THIS DOCUMENT SUMMARIZES AVAILABILITY INFORMATION ANNOUNCED IN SOFTWARE AVAILABILITY BULLETINS (SABs). IT IS NOT A STANDALONE ANNOUNCEMENT DOCUMENT. PLEASE REFERENCE THE NOTES -2AGE OF THIS FIELD AVAILABILITY SUMMARY. t9\ \ \ ,.I!j-:j\>-<- ~\GUR4~ '(9 9347H - 0327H/0328H ,'. ..__ .. , COMPATIBLE RELEASE LEVELS (by columns) AND ASSOCIATED VERSIONS PRODUCT DESCRIPTION SYSTEM SOFTWARE - Release Dates (Note 1) NOS 2 - Operating System I' 77987679 069 12/21/87 2 OF S ~ ~ \DEC ~1987" rio ~ »"" /. -. I~"!SE~~'" ."'/? ~ .,.\'y I __ TY\~ 0 0' o o o Distribution List For CDC CYBER 180/170 /70L/6000 SAB No. 588 Page 3 TABLE 3. CDC CYBER 170-700, 170-800, AND 180-800 SERIES MAINFRAMES ----------------------------------------------------------------------------------------------------------------------------------------------------------MAINFRAME 720 730 740 : 176 :: 760 :-4XX :: 810 : 815 :: 810A: 750 825 .. 830 835 830A: 840 : 845 840A: 850 : 855 850A: 860 : 865 860A: 870A: 875 990 990E 995E :------------------------------------------------------------------------------------------------------------------: PRODUcr NUMBER :0720 :D730 :D740 :D750 :D760 :D770 ::0810 :0815 :0825 :0830 :0835 :0840 :0845 :0850 :0855 :0860 :0865 :0875 :D990 :H720 :H730 :H740 :H750 :H760 :H770 : :H810 :H815 :H825 :H830 :H835 :H840 :H845 :H850 :H855 :H860 :H865 :H875 :H990 PRODUcr NAME ---------------------------------------------------------------------------------------------------------------------------------------------------------: lCEM IGES TRANSLATOR :-122 :-122 :-122 :-122 :-122 :-122 ::-122 :-122 :-122 :-122 :-122 :-122 :-122 :-122 :-122 :-122 :-122 :-122 :-122 :---------------------------------------------------------------------------------------------------------------------------------------------------------: TABlE 4. CDC 6000, CYBER 70 AND 17X SERIES MAINFRAMES MAINFRAME 6000 CY70 171 172 173 0521 H521 0521 H521 D521 H521 174 175 -100 175 -200 175 -300 176 -xx :---------------------------------------------------------------: PRODUcr NAME PRODUcr NUMBER D521 D521 H521 : H521 D521 H521 D521 H521 D521 H521 :------------------------------------------------------------------------------------------------------------------: ICEM IGES TRANSLATOR ~ ~ '. -560 -560 -560 -560 -560 -560 -560 -560 c -0 ARDEN HILLS PROGR. DIV SW MANUFACTURING & DIST. CONTROL DATA CORPORATION FIELD AVAILABILITY SUMMARY NO. REV. DATE PAGE FOR APPLICATIONS UNDER NOS 2 19-CONFIGURATION MANAGEMENT-88 COMPATIBLE RELEASE LEVELS (by columns) AND ASSOCIATED VERSIONS PRODUCT DESCRIPTION SYSTEH SOFTWARE - Release Dates (Note 1 ) NOS 2 - Operdting System NOS 2 - Product Set NOS 2 - Networks Products APPLICATIONS UNDER NOS 2 (Note 2) ICEH PLASTIMOULD ICEM SCHEMATICS ICEM SOLID ANALYSIS ICEM SOLID HODELER I CEH TEKROUTE IMSL VI0 INFORMATION MANAGEMENT FAC 2 INFORMATION PROCESSING FAMILY o IPF/CDCS LINK LINCAGES MIDAS-BASE PACK MIDAS-DESIGN VERIFICATION MIDAS DESIGNER WORKSTATION-BASE MIDAS DESIGNER WORKSTATION-VLSI6260 MIDAS DESIGNER WORKSTATION-VLSI6261 HIDAS-GATE ARRAY LAYOUT MIDAS LAYOUT WORKSTATION-APOLLO MIDAS LAYOUT WORKSTATION-ORCATECH MIDAS-TEST GENERATION MIDAS-VLSI6260 TECHNOLOGY LIBRARY MIDAS-VLSI6261 TECHNOLOGY LIBRARY MOLDCOOL II 77987679 069 12/21/87 3 OF 5 09/86 664 V2.S.1 6S0 664 12/86 670 V2.S.1 670 670 04/87 678 V2.S.2 670 670 09/87 688 V2.S.3 688 688 664 VI.l 642A VI.IS 664 VI.l3 664 VI.l3 664 VI.l 642A VI.IS 664 VI.13 664 V!. 13 664 VI.I 642A VI.IS 664 Vl.13 664 Vl.13 664 VI.I 642A VI.IS 664 VI.13 664 Vl.l3 642 V9.2 596 V2.0 647 V2.6 642 Vl.0 664 Vl.2 642 V9.2 678 VI0.0 678 VI0.0 647 V2.6 642 Vl.O 664 V!. 2 647 V2.6 642 Vl.0 664 V1.2 647 V2.6 642 Vl.O 664 V1.2 ----- ------------------------- -------------------- 647A V2.0 ----- ----- --------------------------- ------------------- 647A V2.0 ---- ----- ------- ... _- ----------- ------- ----------- ----------- 647A V2.0 ----- ----- --------- --- ----- ------------- ----- --------------- 647A V2.0 THIS DOCUMENT SUMMARIZES AVAILABILITY INFORMATION ANNOUNCED IN SOFTWARE AVAILABILITY (SABs ) • IT IS NOT A STANDALONE ANNOUNCEMENT DOCUMENT. PLEASE REFERENCE THE NOTES ON OF THIS FIELD AVAILABILITY SUMMARY. BULLETINS r-PAGE \ o \ 9347H - 0327H/0328H '\ ARDEN HILLS PROGR. DIV SW MANUFACTURING & DIST. CONTROL DATA CORPORATION FIELD AVAILABILITY SUMMARY NO. REV. DATE PAGE FOR APPLICATIONS UNDER NOS 2 19-CONFIGURATION MANAGEMENT-88 COMPATIBLE RELEASE LEVELS (by columns) AND ASSOCIATED VERSIONS PRODUCT DESCRIPTION SYSTEM SOFTWARE - Release Dates (Note 1) NOS 2 - Operating System NOS 2 - Product Set NOS 2 - Networks Products APPLICATIONS UNDER NOS 2 (Note 2) MOLDFLOW 1 WORKSTATION MOLDFLOW 2-9 LOCAL WORKSTATIONS MOLDFLOW 10 OR MORE LOCAL WORKSTATIONS OR MIX OF LOCAL AND REMOTE WORKSTATIONS MOLDSTAR NETWORK JOB ENTRY FACILITY NOS CHART NOS CONTEXT NOS DEFINE NOS GRAPH NOS TOOLS PDS/MAGEN PERT TIME PLATO COURSEWARE DEVELOPMENT AND DELIVERY SYSTEM (PCD2) PLATO LESSON DELIVERY AND AUTHORING 1 PLATO PUBLISHED COURSEWARE CATEGORY I, II & III PLATO PUBLISHED COURSEWARE CATEGORY I, PLATO PUBLISHED COURSEWARE CATEGORY II PLATO PUBLISHED COURSEWARE CATEGORY III PLATO PUBLISHED COURSEWARE CATEGORY IV SIMSCRIPT lI.5 TEKTRONIX 401X PP (TIGS) TEKTRONIX 411X PP (TIGS) 77987679 069 12/21/87 4 OF 5 09/86 664 V2.S.1 650 664 12/86 670 V2.5.1 670 670 664 V4.0 664 V4.0 664 V4.0 664 V3.0 664 V2.S.1 617B V2.1 596 V2.2 617B V2.1 617B V2.1 664 V2.1 596 V14B 642 V2.2 664C R39.1 664C R39.1 678A R39.1 678A R39.1 678A R39.1 678A R39.1 678A R39.1 647 V5.1 617 Vl.4.2 617 Vl.4.2 664 V4.0 664 V4.0 664 V4.0 664 V3.0 ----- 617B V2.1 596 V2.2 617B V2.1 617B V2.1 670 V2.1 596 V14B 642 V2.2 670C R40.l 670C R40.l 678A R39.1 678A R39.1 678A R39.1 678A R39.1 678A R39.1 647 V5.1 617 Vl.4.2 617 Vl.4.2 04/87 678 V2.5.2 670 670 09/87 688 V2.5.3 688 688 664 664 V4.0 V4.0 664 664 V4.0 V4.0 664 664 V4.0 V4.0 664 664 V3.0 V3.0 678 --V2.5.2 --617B 617B V2.1 V2.1 596 --V2.2 --617B 617B V2.1 V2.1 617B 617B V2.1 V2.1 670 670 V2.1 V2.1 596 596 V14B V14B 642 642 V2.2 V2.2 678B 688A R40.1 ,R40.1 678B 688A R40.1 R40.l 678A R39.1 --678A --R39.1 --678A --R39.1 --678A --R39.1 --678A --R39.1 --647 647 V5.1 V5.1 617 617 Vl.4.2 Vl.4.2 617 617 Vl.4.2 Vl.4.2 --- THIS DOCUMENT SUMMARIZES AVAILABILITY INFORMATION ANNOUNCED IN SOFTWARE AVAILABILITY BULLETINS (SABs). IT IS NOT A STANDALONE ANNOUNCEMENT DOCUMENT. PLEASE REFERENCE THE NOTES ON THE FIELD AVAILABILITY SUMMARY. 9347H - 0327H/0328H c -0 ARDEN HILLS PROGR. DIV SW MANUFACTURING & DIST. CONTROL DATA CORPORATION FIELD AVAILABILITY SUMMARY NO. REV. DATE PAGE FOR APPLICATIONS UNDER NOS 2 19-CONFIGURATION MANAGEMENT-B8 COMPATIBLE RELEASE LEVELS (by columns) AND ASSOCIATED VERSIONS PRODUCT DESCRIPTION SYSTEM SOFTWARE - Release Dates (Note NOS 2 - Operating System NOS 2 - Product iet NOS 2 - Networks Products APPLICATIONS UNDER NOS 2 (Note 2) TIELINE/NP TIGS 1 TOTAL EXTENDED 2 TOTAL UNIVERSAL 2 UNIPLOT V3 LIBRARY + EXECUTIVE UNIPLOT CALCOMP 907 DEVICE DRIVER o UNIPLOT HEWLETT-PACKARD (HPGL) DEVICE DRIVER UNIPLOT KMW DEVICE DRIVER UNIPLOT TEKTRONIX 40XX/41XX/4510 DEVICE DRIVER UNISTRUC 77987679 069 12/21/87 S OF S 1) 09/86 664 V2.S.1 650 664 12/86 670 V2.S.1 670 670 04/87 678 V2.S.2 670 670 09/87 688 V2.S.3 688 688 664 V2.5.1 617 V1.4.2 ----- 678 V2.S.2 617 V1.4.2 630 V2.1C 617 V2.1C 647 V3.2 647 V3.2 664 V3.2 ----- ----- 617 V2.1C 647 V3.2 647 V3.2 664 V3.2 ----- 647 V3.2 S96A Version ISAug84 617 V1.4.2 630 V2.1C 617 V2.1C 688 V3.2 688 V3.2 688 V3.2 688 ----V3.2 ----688 647 647 V3.2 V3.2 V3.2 S96A S96A S96A Version Version Version ISAug84 ISAup;84 ISAup;84 617 V1.4.2 630 V2.1C 617 V2.1C 647 V3.2 647 V3.2 664 V3.2 THIS DOCUMENT SUMMARIZES AVAILABILITY INFORMATION ANNOUNCED IN SOFTWARE AVAILABILITY BULLETINS (SABs). IT IS NOT A STANDALONE ANNOUNCEMENT DOCUMENT. NOTE 1: For details on the compilers, data management, network, and other products included in System Software, see the NOS 2 SAB for any release level. NOTE 2: Applications are generally released asynchronously from the System Software and from each other. An entry for an application in a column means that the level shown is available and has been announced for use with the level of System Software indicated at the top of the column. NOTE 3: Applicable release level must be specified on the order. Ordering by version number is not compatible with the order processing system and will result "in order delay; (e.g., 678, not Vl.0). Availability not announced. o 9347H - 0327H/0328H .",-- o CONTROL DATA CORPORATION ICEM DDN VERSION 1.60 INSTALLATION INSTRUCTIONS Operating System Level: NOS 2 Level 642A Date: 4/7/86 o DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Control Data Corporation gives the user permission to reproduce this document. SMD131060 CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 642A 1 4/7/86 Index Section I Release Description page 2 Section II Tape Formats and File,s page 3 Section III Installation Instructions ICEM DDN Design/Drafting Package Page 5 ICEM DDN Advanced Design Package page 6 ICEM DDN Numerical Control Package page 7 Section IV ICEM DDN Verification Instructions page 8 Section V Plotter Verification page 8 o APPENDICIES Appendix A Internal Drafting Standards page 10 Appendix B Terminal Set-up Procedures page 12 Appendix C GPL and GTGT Execution page 16 Appendix D Cyber 800 Tuning Guide for ICEM DDN page 17 - - _ . " .. ,.", --"",,",,"', ..........,,, .... "., .. ' . ' ' ' ' ' . ' " CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 642A (~) I. 2 4/7/86 Release Description ICEM DUN is a computer-aided design and computer-aided manufacturing (CAD/CAM) system that runs under the NOS and NAM/IAF communications package. ICEM Design/Drafting The ICEM Design/Drafting file contains overlays for Basic Geometry, ANSI Mechanical Drafting, and Geometric Analysis. For International Drafting Standards, see Appendix A. ICEM Advanced Design The ICEM Advanced Design consists of all the overlays in the ICEM Design/Drafting plus additional overlays for Advanced Design. ICEM Numerical Control The ICEM Numerical Control consists of all overlays in ICEM Design/Drafting and ICEM Advanced Design, plus additional overlays for Numerical Control. ICEM GPL ICEM GPL is a high level computer lang~age designed to provide a user with features of the ICEM DDN product. The features are provided parametrically from within algorithms. The ICEM GPL system the standard programs must first interpreted by ICEM ~ithin consists of two parts: an interpreter located ICEM DDN and a stand-alone compiler. Source GPL be compiled before those programs can be DDN. The ICEM GPL compiler is provided with the purchase of any portion of ICEM DDN (Design/Drafting, Advanced Design, or Numerical Control). Hardware Requirements ICEM DDN requires the minimum hardware configuration for NOS and NAM/IAF. A field length of 162,000 octal is required for execution. The user station is a Tektronix 4014 or 4016 with Extended Graphics, Tektronix 4105, 4107, 4109, 4113, 4114, or 4115, and Control Data Corporation 721. C ) ,o . CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 642A 3 4/7/86 II. Tape Formats and Files All tapes are nine-track made with a density of 1600 cpi (D=PE) • All tapes are ANSI-labeled and in INTERNAL format (LB=KL,F=I) • VSN=REL68 L=ICEMDD VSN=REL68A L=ICEMAD VSN=REL68B L=ICEMNC III 112 113 /14 111 112 113 111 112 /13 /14 It5 116 117 118 Ily INSTALL ICEMDDN DDNSRB DDNVER DDNVIT DDNUTIL OPTIM VERUTIL TAPE 9 INSTALL ICEMAD COPYLDR INSTALL ICEMNC COPYLDR PPFULL VSN=REL68C L=ICEMGPL 111 112 113 114 INSTALL GPL GTGT GOLIB Description of Files (I) Indirect Access File (D) Direct Access File COPYLDR (I) J is a copy utility used in the integration of the Advance Design or Numerical Control overlays into ICEM DDN Design/Drafting. DDNSRB (D ) HARKS GET INCREMENTED TO THE RIGHT (6.1) PARTS WITH THREE AND FOUR D'rGIT SHEET NUMBERS OVERPRINT. (5.10) LDF NOT UPDATED WHEN NESTING TEMPLATE IS MODIFIED. (17.1.13) INTERNAL CORNERS DOESN'T WORK •. (17.9) SEMI FINISHES LATHE FAILS TO FOLLOW BOUNDARY WHILE IN GROOVE. (15.1.7.2) CLOSURE END CONDITION CAN LEAD TO INCORRECT. (MANUAL)DESCRIPTION NON STANDARD AND CONFUSING IN 8.6.15 CHANGE PAGE. (17.4) STEP-OVER IN POCKET LEAVES MATERIAL. (17.2.2) PITCH DOES NOT WORK AS DOCUMENTED. (12.3.6) AT INDICATE PT. FOR RHO -- OP REJECT WONT BACK YOU OUT. (6.5.4) OP.REJECT BOUNCES TOO FAR (5.2.3) WHEN AN ERROR OCCURS, MENUS GET TURNED OFF. (5.2.3.2) 'ERROR MSSAGE ON 721--0UTPUT TOO BIG FOR UTF--OUTSIDE DIALOG (17.11) BAD POINTER IN DISPLAY AND EDIT. (15.2.13) (9.15) FILLET SURFACES CAN NOT BE USED IN THESE MENUS (F.12.1.5.3) CHAIN SELECT (11.9) BAD FILLET ARCS PRODUCED IN AUXILLARY WORK VIEW TRACE FILES FROM ONE TRMINAL DO NOT WORK ON OTHER TYPES UNSUCCESSFUL AT MIRRORING OF A NOTE NO RESCALE WHEN DISPLAYING ENTITIES WITH ATTENTION ON --_.-.__.._....._.- - - - - - - - ' - - - - -- .._- '-'-_ ....-._. _....._--------_ .. - - - - - 75 01/17/86 AD2A587 AD2A589 AD2A596 AD2A597 AD2A599 AD2A602 AD2A603 AD2A612 AD2A614 AD2A616 AD2A626 AD2A627 AD2A628 AD2A629 AD2A63 0 AD2A631 AD2A635 AD2A636 AD2A637 AD2A647 AD2A653 AD2A654 AD2A656 AD2A658 AD2A659 AD2A66 0 AD2A661 AD2A667 . AD2A6743 AD2A6753 AD2A6847 AD2A6907 AD2A6927 AD2A6937 AD2A6947 AD2A6987 AD2A6997 AD2A7047 AD2A7057 AD2A7117 AD2A7127 AD2A7177 AD2A7197 AD2A720 AD2A721 AD2A723 AD2A7267 AD2A7277 AD2A728 AD2A731 AD2A732 AD2A7330 AD2A7340 AD2A7350 -M U S S S S M M C M C C U S M S C S U S S M S S S .S M M M S M S U M M K S S M M S S S S S C M M S S U M M S MODIFY/REPLACE VECTOR, LDF NOT UPDATED CURVED MESH SURFACES THAT ARE DEFINED WITH 30 VARIABLE CURVES ABORT '. . . /. GPL INTOF RETURNS PT OF INTERSECTION BETWEEN PARALLEL LINES RESIZE DOES NOT WORK RIGHT ON DIMENSIONS WITH FRACTIONS MENU CHOICES LIKE 00, 111 AND 88 ARE ACCEPTED RHO AND LOFT CONICS CANNOT BE CONSTRUCTED UNDER PRESENT CODE AN [ TO LEVEL CHANGE REQUEST RETURNS TO ENTITY SELECTION NO HELP MESSAGES IN ANALYSIS AREA TRANSLATION BY REGION FAILS TO MOVE ALL ENTITIES MODIFY DRAFTING ENT. REPLACE STRING 'NO MATCH FOUND' PART MERGE FAILS ON THE PART NAMED GM SHEET 1 VIEW 4 CAME UP ON A DIFFERENT SCREEN LOCATION EACH TIME TEK 4105/7/9 TERMINALS DO NOT DISPLAY ALL LISTS CORRECTLY SURFACES NOT BEING BLANKED WHEN CREATING COMPOSITE SURF DIMENSION USING FRACTION MODAL IN GPL IS OFF-CENTER GPL LINEAR DIMENSIONS HAVE INCORRECT ARROWS AND DIMENSION LINES GET ERROR MESSAGE IN ROUGHING IN LATHE MILLINGVIOLATES CONTAINMENT (PROBABLY AN OLD PROBLEM) TRIM TWO ENDS WITH SPLINE AS BOUNDARY FAILS THE EXIT ARC IS NOT TANGENT TO BOUNDARY IN PROFILE OPERATION 13.6 ROTATION OF A 3-D SPLINE DOES NOT WORK CORRECTLY 12.4.6 STING BEARING DEGREE ENTRY NOT TURNED ON REPAINT INCORRECTLY DISPLAYS CLIPPED ENTITIES F9.9 POINT AT INTERSECTION DOES NOT WORK WITH MACHINING CURVE 6.1.10 IPARTD RETRIEVE LOSES SELECTIVE VIEW BLANK INFO POINTS OUTSIDE OF E-CLIP RANGE MAY BE SELECTED (~I MANUAL DON'T SPECIFY DEFAULT WORK VIEW WHEN DISP.LAYING MULTIPLE VIEWS~ REDUNDANT PARAMETER SPECIFICATION IS NOT HANDLED PROPERLY CURVE MESH SURFACE-CURVE LIMIT UAE ERROR WHEN DELETING ALL WITH A GROUP AND RECTANGULAR ARRAY TEK 4105 DOES. NOT RUN TEST SCRIPT VERY WELL MAJOR DIAMETER CANNOT BE MODIFIED FOR LINE PASS THRU THE ORIGIN PART MERGE DOES NOT CONVERT ENGLISH TO METRIC'UNITS ARROW ON A RADIUS DIMENSION DISPLAYS INCORRECTLY IN SPECIAL CASE LABEL USING SLOPE METHOD POINTS TO THIN AIR ARC THROUGH 3 PTS CREATES LINE WITHOUT WARNING USER VERTICAL LDlMEN DIMENSION LINES AUTO GRAPL GENERAT_ES BAD ENT~TY NAME USER DEFINED SYMBOL LIST AND DISPLAY RETRIEVE NAMED ZOOM FROM DIFFERENT VIEW DOCUMENTATION OF CHANGE PAGE "OVERLAP" DOCUMENTATION OF ZOOM FROM HARD COpy LOWER LEFT AND SCALE MENU 8.6.5 DOESN'T WORK IF SCALE IS ACCEPTED A CHECK CURVE LOCATED AT THE END OF AN ENTITY IS IN LATHE ROUGHING, THE FACING OPTION IGNORES THE VALUE LINES TO STRING CONVERSION RE-ORIENTS GEOMETRY TO CURRENT DEPTH F.8.10.l Z-CLIP VALVES ARE INCORRECTLY DEFAULTED .F.8.l0.1 Z-CLIP REQUIRES VIEW REDEFINITION TO DISPLAY USERS MAY INADVERTANTLY DEFINE PATTERN LIB FILES AS GLOBAL PART FILES DUPLICATE/TRANSLATE AN HLR'D PART MULTIPLE FORMAT VIEWS PLOT COMPLETE MESSAGE DISPLAY WHEN EXIT WITH NO PLOT PROBLEM WITH ] AT END OF VIEW NAME COORDINATES OF A TEMPLATE IN A MERGED PART ARE NOT ALWAYS CORRECT 76 01/17/86 C) 0 0 AD2A7360 AD2A7420 AD2A7430 AD2A7440 AD2A7450 AD2A7460 AD2A7470 AD2A7480 AD2A753 AD2A7540 AD2A7550 AD2A7560 AD2A7570 AD2A7580 AD2A7590 AD2A7600 AD2A7610 AD2A762 AD2A7630 AD2A7640 AD2A765 AD2A7660 AD2A7670 AD2A7680 AD2A7690 AD2A7700 AD2A7710 AD2A7720 AD2A7730· AD2A7740 AD2A7750 AD2A7760 AD2A7770 AD2A7780 AD2A7790 AD2A7800 AD2A7810 AD2A7820 AD2A7830 AD2A7840 AD2A7850 AD2A786 AD2A7870 AD2A7880 AD2A7890 AD2A7900 AD2A7910 AD2A7920 AD2A7930 AD2A7940 AD2A7950 AD2A7960 AD2A7970 AD2A7980 -S S M M M M S M M M M M S M M S S C S S S S S S U S M S· M U U U C S U S M C M M S S S S U S M S C C C M S S TOOL AXIS IS INCORRECT WHEN SURFACE NORMAL IS CHOSEN SURFACE PIERCE POINT FAILS ON A HALF SPHERE IN OFFSET CURVE, OFFSET DISTANCE DATA REQ SHOULD BE SPELLED OUT DBM TABLET HAS REGENERATE ALL SQUARES DEFINED INCORRECTLY DC TABLET HAS MISLEADING LABEL FOR COLOR BY ENTITY TYPE DIFFERENCE IN DISPLAY 2 VIEWS BETWEEN MAIN AND DC OVERLAYS DC TABLET HAS ALIGNMENT SCALE SET TO REF SAME AS UNCHANGED ATTENTION INDICATORS DON'T GO AWAY AFTER DONE WITH FILLET GTGT ISSUE WARNING FOR ASSIGNMENT GTGT WARNING MESSAGE FOR UNNECESSARY SUBSCRIPT GTGT DOESN'T CATCH ALL ATTRIB STATEMENTS THAT ARE VALID GTGT ISSUES UNNECCESSARY WARNING RESTORE RETRIEVE MODAL SETS THE DEFAULT ROTATION AXIS TO X DUAL DIMENSION TEXT BRACKETS ARE MISPLACED ON THE RIGHT SMALL FRACTIONAL TOLERANCES ARE BLANK, SHOULD READ ZERO ARC LENGTH IN BACK VIEW FAULTY ARC LENGTH DIM. DONE ON ARCS OF 180 DEG. ARE INCORRECT UAE IN INCREMENTAL POINTS 20 OFFSET CURVE DREW AN ERRATIC CURVE & CONTINUED NORMALL~ FILLET CREATES ARC IN WRONG QUAD OF INTERSECTION OFFSET CURVES WITH ZERO OFFSET DOES NOT WORK FILLET DOESN'T TRIM EXTEND PROPERLY SMALL FILLET IS CREATED IN WRONG QUADRANT TRIM TWO CURVES TRIMS OFF WRONG END OF ONE CURVE FILLET OF FILLETED ARCS SENDS USER TO DBM THE LARGE· TABLET DIGITIZER DOES NOT WORK CORRECTLY EMBEDDED TEXT GETS ECHOED TWICE [ AND ] AREN'T HANDLED PROPERLY IN ATTRIBUTE REPORTS AUTO MAX/MIN CUTS OFF .ARCS IN RECT ARRAY WHEN AT EDGE GAP IN OFFSET SURFACE CURVE INTERSECTION POINT BETWEEN DRAFT CURVE AND LINE IS INCORRECT SSI WILL NOT FIND AN INTERSECTION CURVE 3D ANALYSIS RESULTS INCORRECT ALL 2D ANALYSIS IS DISPLAYED IN INCHES WHEN IN FT/IN STDS PRINCIPLE AXES ANGLES.ERROR IN 2D ANALYSIS· DATA VERIFY ATTENTION INDICATOR FROM THE-BEGINNING OF STRING REMAINS DISPLAYING TEXT IN 4 STD. VIEWS BLOWS ZOOM SCALE TO INFINITY DRAFTING ENTITIES CHOSEN FROM VIEW8 DISPLAY INDICATORS WRNG DELETING A DIMENSION WITH ISO DRAFTING MODEL SET SPACING OF VERTICAL DIMENSIONS WRONG WHEN PAR LIN DIM FT/INCHES NOT DISPLAYED OR CANNOT BE ENTERED SOME CORRESPONDING KEYS FOR USER DEF SYMBOLS ARE UNUSABLE. DIMENSION TEXT PLACEMENT ERRORS PROBLEM WITH CENTERING DIM TEXT WHEN MODIFY TEXT ORIGIN SPLINE PRINTOUTS HAVE BAD DATA FOR NORMAL AND ALPHA ANGLES WITH SINGLE SELECT FROM GROUP ON CONSTRNT SET SELECTS GROUP ZOOM WITH AUTO MAX/MIN . 9-DRILL. INCORRECT .PULLOUT EEEDRATE WHEN MODIFIED IN GPG 9-CONT. INCORRECT TOOLPATH WHEN ALL GPG VALUES ARE MODIFIED CONTOURING MODIFY GPG- TOOLS IDE COORDS LOST THREADING MODIFY GPG THREAD SIZE/PASSES HAS BAD PROMPT DRIVE LINE PROBLEMS IN LATHE CONTOUR COpy PASS LINE LIMIT CAUSE THE SYSTEM TO BLOW-UP 77 01/17/S6 AD2A7990 AD2ASOOO AD2AS010 AD2AS020 AD2AS030 AD2AS040 AD2AS050 AD2AS060 AD2AS07 AD2ASOS AD2AS09 AD20330 AD20395 AD20433 AD20457 AD20460 AD20527 AD20554 AD20577B AD205S6 AD2063S AD20679 AD20S03 AD20S12 AD20S26 AD20S45 AD20S9S AD20912 AD20961 AD21002 AD21026 AD21033 AD21042 AD21063 AD21064 AD21071 AD21075 AD21076 AD210S6 AD210S7 AD21106 AD21133 AD21152 AD21155 AD21159 AD21165 AD21174 AD211S3 AD21193 AD21196 AD2119S AD21203 AD21206 AD21216 -C 5 5 U 5 U U U U U 5 U U U M 5 M 5 U U M 5 C 5 5 S U 5 S U S U 5 5 S 5 5 5 5 C 5 U U -U M U U 5 U S U U U U TEXT DISPLAY IN DIALOG AREA AND DYNAMIC TOOL DISPLAY GIVE ERROR (,.- .' IN COMMAND MODE, MATRIX COpy FROM FILE AND TOOLPATH FAILS MACROS USING A LITERAL STRING INSIDE OF AN IF STATEMENT 2-SURF.PRO. - 'PAR.DRI.sURF.' SHOULD ALLOW USER TO SELECT U OR V-PATH SYS-AID CALLED IN 3-D ANALYSIS (lS.4.1.1) GPL BULK STATEMENT WILL NOT EXECUTE REOPENING PTR 60R694 - COpy OPTION IN DISPLAY AND EDIT F.15.3.13 COMPOSITE SURFACE RETURNS INCORRECT RESULT F.15.3.13 COMPOSITE SURFACE SELECTION HANGS IN LOOP DIMENSION LEADERS & WITNESS LINES MAY TRANSLATE AS NON-SOLID FONTED LEADERS CREATED IN METRIC MODE W PART UNIT>TO ENGLISH UNIT EXTRA LONG (BAD PNTR) PROBLEMS WITH DELETED USED-IN-DEFINITION ENTITIES. (16.14)DETAIL MAGS APPEAR IN ALL VIEWS RATHER THAN SINGLE (15.2.7)FILLET SURFACE ONLY HALF GENERATED BETWEEN PLANE AND DRAFT SU (10.4/12.11)LINE TANTO 2 ARCS WOULD NOT HIDDEN LINE REMOVE: NO INTRS. (15.2.7)FILLET DID NOT COMPLETE BETWEEN TAB CYL AND RULED SURFACE. (12.3.5)LOFT CONIC THROUGH THREE POINTS INCONSISTENT. *(1.10/6.2.2) PATTERN PROBLEM WITH SELECTIVE BLANKING (17.5) COMPOSITE SURFACES DO NOT MACHINE . (7.9) REGENERATE ALL USING STRING, FILLET, CROSS HATCH GIVES (DIGITIZE) EVENTUALLY LOST THE ABILITY TO DIGITIZE CERTAIN ENTITIES. (lS.2) MULTI-CURVE ANALYTIC AREA IS NOT CONSISTENT. (17)CD/2000 ABORTS DURING PATH OF RULED SURFACE. (5.2.3) VIEW CHANGES IN AUTO GRAPL ON CIRCS WITH YZ ROT OF lS0. * (17.6/7.1) WRONG DIRECTION FOR CLFILE TOOL AXIS VECTOR. *BACKSPACE DO~SN'T ERASE CHARACTER WITH TABLET, ALPHA, 4016,GTA-1. ~I *DRAFTING - DETAIL MAG IS DISPLAYED IN ALL VIEWS, NOT JUST ONE. *NC - LATHE ROUGHING FACE CUT ORIGIN IS AMBIGUOUS. *16.12-BOLT CIRCLE WILL NOT DISPLAY PROPERLY ON A MIRRORED CIRC.ARRAY ~(3.3.3.1)ENTITIEs OUTSIDE OF REGION PICKED FOR DELETION. (7.2)PLOT-UNIPLOT-5"GAP CAUSES PLOT INACCURACIES RELATED TO USE OF *SURFACE PIERCE PT DOES NOT ALWAYS FUNCTION. *GRAIOF INPUT GUTF/TEK 4014 NO ERROR OUTPUT DURING COMPILE. *SYMBOL DEFINE OR REPLACE. *BLANK AND UNB·LANK ENTITIES FROM A MERGED DRAWING. CD-2000 NC LATHE AND MILLING PROBLEMS. *PLATE NESTING DOES NOT WORK. *PROBLEMS DURING ROTATION OF SURFACES. DEGREE SYMBOLS CHANGED TO DASH AFTER MERGE *TRUE INTERSECTION POINT OF TWO LINES F.9.9.4. *PACK 6.1.S PREVIOUS TO IGES IN/OUT. *(16.3) CROSSHATCHING. PART MERGE LOSES EXTENDED GEOMETRY (6.1.7) 6.1.7 PART MERGE LOSES SOME EXTENDED GEOMETRY *CHANGE VIEWS - RIGHT/LEFT DOESN'T SCALE CORRECTLY. (10.4) LINE TANGENT TO 2 ARCS GO TO WRONG SIDE OF ARCS *PROGRAM STOPS ACCEPTING SCREEN POSITIONS. TITLE BLOCK OVERLAY CANNOT USE COMPO~ITE CURVE AS DRIVE OR CHECK CURVE TERMINAL 4115B BAD CUT VECTORS IN LDF. LATHE ROUGH BORE PLACES ROUGH STOCK OFFSET ON WRONG SIDE(1.49X) ~' BAD CLFILE OUTPUT OF AN ABSOLUTE TOOLPATH DATA BLOCK(1.49X) -_. .) VARIOUS PROBLEMS WITH COMPOSITE SURFACES(1.49X) *"PACK PART" CAUSED DISPLAY TO DISAPPEAR WHEN REPAINT OR ZOOM. r',1 o () 78 01/17/86 AD21248 AD21250 AD21251 AD21252 AD21263 AD21291 AD21335 AD21341 AD21347 AD21353 AD21357 AD21359 AD21362 AD21458 AD21472 AD21476 AD21482 AD21486 AD21488 AD21497 AD21499 AD22039 AD22046 AD22052 AD22054 AD22058 AD22060 AD22061 AD22065 AD22074 AD22085 AD22112 AD22115 AD22116 AD22117 AD22121 AD22123 AD22148 AD22155 AD22162 AD22182 AD22183 AD22189 AD22190 AD22193 AD22195 AD22198 AD22202 AD22204 AD22213 AD22220 AD22225 AD22226 AD22227 ·S U U U S S *FLAME CUTTING, MENU F.17.15 - DEFINED CIRCLES. *FLAME CUTTING, MENU F.17.15 - REZERO CUT. *FLAME CUTTING, MENU F.17.15, MARK AND FAST MARK. *ZOOM AUTO MAX/MIN DOES NOT WORK IF AN INFINITE LINE IS PRESENT. CIO MESSAGES ON NOS/BE SYSTEMS INCONSISTENT DEFINITION OF PARAMETER IN POINT ON A CURVE OPTION. *LOSS OF SCALE DURING LAYOUT CONSTRUCTION. (7.10) BULKIN DATA EXECUTION IS 10 TIMES SLOWER IN 1.50 THAN 1.45 BAD MOVE AND FAULTY CIRCLE RECORDS IN CLFILE TRIMMING OF LINES AT ARC NORMAL TO VIEW IS WRONG. VIEW MATRICES ARE NOT CHECKED SUFFICIENTLY. *** TOO MANY "UNNECESSARY" OP COMPLETES REQUIRED ON DATA ENTRY *** SUBTRACTIVE COLOR TABLE MANIPULATION SEEMS AWKWARD/INCOMPATIBLE SPIKES ACROSS THE SCREEN ON 4115 TERMINAL CROSSHAIRS DO NOT RETURN TO ACTIVE IF TERMINAL LOCKS UP ON A 4115 TRIM MULTIPLE CURVES TO A BOUNDARY PRODUCES IMPROPER RESULTS LATHE ROUGH FACING OFTEN FAIL BAD PATH USING BOUNDRY THAT HAS SOME SMALL (.0005") GAPS TEKTRONIX 4115 DISPLAY CHARACTER SIZE IS CHANGED WHEN CD2000 IS EXITE STRING MADE FROM TRANSLATED ENTITIES SCREWS UP REION SELECT TRIMMING OF INFINITE LINES IS WRONG. CONICS DISPLAY VLAUES AE INCONSISTANT·BETWEEN METRIC AND ENGLISH RESULT OF PART MERGE IS INCOMPLETE (6.1.7) (F.17.9) ICEM N/C LATHE FINISH STOCK *CD2000 NC PROBLEMS. DUPLICATIONS OF NON-DELETABLE ARE FLAGGED AS NON-DELETABLE. DISPLAY PREVIOUS LAYOUT DELETABLE STATUS CHANGED INCORRECTLY HIDDEN LINE REMOVAL DOESNT WORK ON MACHING CURVES *SUPPORT OF TEK4109 WITH TABLET TEK4957 BY ICEM PRODUCTS. NO CIRCLE RECORD OUTPUTTED FOR LATHE ROUGHING DISPLAY TOLERANCE TO CIRCULAR ARRAY (17.15) FLAMECUTTING GENERATES WRONG TOOLPATH (7.1) N/C CIRCULAR INTERPOLATION FINDS WRONG RADIUS AND CENTER INCORRECT OUTPUT OF TOOLNO AND FEEDRATE VALUES AFTER 30 POINT CUT CD2000 REQUIRES EXTRA CARRIAGE RETURN W/L=O AND TB=Y PARAMETERS "NC MODAL TOLERANCE" ADVERSELY AFFECTS TOOLPATH DISPLAY WEIGHT/UNIT LENGTH INCORRECT FOR SURFACES ROTATED ABOUT LINES SELECTION LINING WITH ELLIPSE AS A BOUNDARY NOT WORKING MIRROR OF TEXT TURNS TEXT UPSIDE DOWN THE INITIAL PAINT FOR SEVERAL OF THE PARTS ON MY TAPE3 BOMBS OUT *PROBLEM IN UNWRAP FEATURE CD2K SHOULD NOT ALLOW APPLICATION KEYWORDS IN GLOBAL FILENAMES 3 - AXIS TOOLPATH IS WRONG ENTITY SELECTION IN VIEWS OTHER THAN THE WORKING VIEW LINES MODIFIED TO INFINITE LENGTH DON'T DATA VERIFY AS INFINITE MULTIPLE VIEW PLOTTING MODE IN MENU 7.2 . PROBLEM WITH 3-D ANALYSIS MENU 18.4 PROBLEMS WITH ELLIPSES - GENERATION AND OFFSETS (F.8.7.11) UNABLE TO FORMAT A SINGLE VIEW. ENTITY MANIPULATION REQUIRES TOO MUCH REPEAT INPUT. CANNOT WORK AROUND GOTOER.MESSAGE IN DDN 1.5.0 (F. 17. 15) FLAME CUTTING GENERATES WRONG ENTRY AND EXIT TOOL PATH (F. 17. 15) FLAME CUTTING GENERATES WRONG TOOL PATH. C U U U C U S U S U S U U U C U U U S S C C U S S U M M M U C C M M C S U C U U U S U U C U S U - - - - - - _. ._----_ ...._._ .. _-_ ..... --_.- ..- -_._-- - -- .. _.- - .- .. _......- -------------------- - - - - - - - - - - - _ _ --.._.. __._-.. . . ... 79 01/17/86 AD22228 AD22229 AD22230 AD22240 AD22241 AD22242 AD22249 AD22251 AD22254 AD22258 AD22266 AD22272 "AD22291 AD22292 AD22293 AD22297 AD22299 AD22300 AD22302 AD22303 AD22305 AD22309 AD22311 AD22312 AD22314 AD22315 AD22317 AD22319 AD22321 AD22330 AD22335 AD22337 AD22338 AD22339 AD22340 . AD22353 AD22354 AD22355 AD22357 AD22358 AD22359 AD22360 AD22362 AD22363 AD22364 AD22365 AD22367 AD22368 AD22370 AD22371 AD22379 AD22390 AD22394 AD22411 S U U U S S C S S M U U S M U C U U U C U U S C C C C C U S U U U C M C M S C C U U U U U U U U U U C U C U (F.17.15.)FLAME CUTTING GENERATES WRONG TOOL PATH. (F.7.1) PROBLEM WITH CIRCULAR-INTERPOLATION IN FLAME CUTTING. (F.7.1)PROBLEM WITH CIRCULAR INTERPOLATION IN FLAKE CUTTING. SOLID LINES BECOME DASHED LINES CIRCULAR ENTRY/EXIT CUT WRONG (FLAKE CUTTING). *UNCOMPLETE FILLET SURFACE PART MERGE NOT WORKING PROPERLY INTERNAL CORNERS DOES NOT WORK TANGENTIAL CUTTING DOES NOT CHECK FOR GEOMETRY VIOLATION SCREEN BLANKS ON 4114 TERMINAL WHEN CREATING A PRINTR FILE IN CLFILE CANNOT GENERATE ROUGH LATHE TOOLPATH WITH .03 RAD AND DEPTH OF CUT .0 3-SURFACE PROFILE TOOL AXIS PARALLEL TO OS GIVES BAD RESULTS. F.5.9.2 LINE TANTO CURVE HAS DISPLAY PROBLEM F.12.8.1 TRIM ONE END ON INFINITE LINES WORKS INCORRECTLY F.9.15 SURFACE POINTS PRODUCE ERRONEOUS VALUES USING NORMAL & PIERCE ICEM-DDN V1.53 BULKIN INPUT 10 TIMES SLOWER THAN IN V1.45 AND RESERVE 16.13.4 MODE ERROR WHEN ADDING TOLERANCE TO A DRAWING BLANKED ENTITIES TRANSLATED/CHANGED LEVEL BY DUPL/TRANS OTHER ENTITlE GOTOER. CALLED MESSAGE WHEN TRYING TO REPAINT BY CHANGING ZOOM. SCREEN SELECT IS PICKING BLANKED ENTITIES NOT ELIGIBLE IN CURRENT TAS DATA CAPTURE CORRUPTS THE RUN TIME LIBRARY. PERFORMANCE PROBLEM WITH SURFACE MILLING NO "RESCALE?" REQUEST AFTER UNBLANKING FILLET W/SPLINE & LINE FILES 2-D OFFSET OF A 2-D SPLINE DELETE BY LEVEL RANGE" DELETES WHOLE PART FILLET SURFACE RADIAL GOES TO ZERO NC POCKET FAILURE ON 63-CHARACTER SET SYSTEM, A PERCENT SIGN IS CONVERTED TO A COLON. 16.13.14.2 CHANGING RADIUS CHANGES THE ORIGIN OF THE WORDING. 1.9.1.3 CHANGE THE DEFAULT COLOR FOR LEVELS 9 & 10. NON-COMPATIBLE SETS. HIDDEN LINE REMOVAL OF MACHINING CURVES WRONG USER DEFINED SYMBOLS F5.4 PIPEWORK INTERFERENCE CHECK ABORTS . CHAIN SELECT DOESN'T WORK FOR SMALL METRIC ENTITIES •. 16.1.16 DRAFTING MODALS SAY DIAMETER SYMBOL ON EVEN WHEN OFF UNABLE TO ADD FORMAT TO A SINGLE VIEW OF FRONT LAYOUT 1.53 PROBLEMS EXIST WITH CHAIN SELECT ESPECIALLY WITH METRIC UNITS 1.53 CROSSHATCHING 1.53 MODIFYING PENS AND NOT LEVELS IN MULTI-PICKS IS A PROBLEM 1.53 1982 ANSI STANDARDS PROBLEM 1.53 IMPLICIT POINTS PROBLEM 1.53 STRING NOT BEING CLOSED PROPERLY 1.53 PLUS - NEED BETTER TERMINAL RECOGNITION 1.53 PROBLEM WITH DETAIL MAGNIFICATION 8.7 EXTENSIVE LAYOUT USAGE CORRUPTS DATA BASE (11.8)MODIFY ANGLES GIVES UNPREDICTABLE RESULTS 1.53 VIEW LAY-OUT FUNCTION NOT WORKING PROPERLY 1.53 VARIOUS PROBLEMS WITH 2-D ANALYSIS 15.1.4 DRAFT CURVE DOES NOT WORK DRAGGING ENTITIES 7.10 BULKIN INPUT DOESN'T ACCEPT TEXT ANGLES ANY MORE, WRITES. NOTE PARALLEL TO ARC NOT FUNCTIONING CORRECTLY WITH USER DEFINED CHAR 0 ;' t" ~." "" 80 01/17/86 (\ ~) I"'·-~" ~\ 0 AD22416 AD22427 AD22432 AD22434 AD22438 AD22448 AD224513 AD22452 AD22455 AD22466 AD22467 AD22470 AD22471 AD22472 AD22473" AD22480 AD22484 AD22487 AD22488 AD22489 AD22491 AD22493 AD22495 AD22496 AD22497 AD22498 AD22515 AD22518 AD22525 AD22526 AD22528 AD22532 AD22535 AD22536 AD22542 AD22547 AD22550 AD22560 AD22564 AD22565 AD22566 AD22567 AD22568 AD22570 AD22579 AD22594 AD22595 AD22600 AD'22606 AD226070 AD22610 AD22612 AD22613 AD22614 C U C U C M S S S C S, C C M M U U U C S U U U S S S U U S S U U S S C C M C M S S U S U U U C U C U S C C M F.6.1.7--PART MERGE "ORIGIN" AND "SCALE" FAILURE. MENU 11.9- CANNOT DEFINE A FILLET BETWEEN TWO COPLANAR CURVES F.16.3 F.16.X DRAFTING UNRESTORABLE GPARTS. OPTIM (DDNUTIL) READS ONLY 1 PICTURE ON THE TAPE9 CAN'T LOAD TAPE3 DATA OF SELECTED ENTITIES LARGE MSTRING FILES TAKE TOO LONG TO INITIALIZE. CANNOT SELECT SAME ENTITY FOR LABEL ENTITY AND ORIGIN DELTA ENTITY DDN UNABLE TO CREATE POINTS OF LINES IN ANY OTHER VIEW THAN 1. F.10.9 THROUGH POINT PERPENDICULAR TO LINE. TRASHED TAPE3 WON'T RETRIEVE EXISTING PARTS OR CREATE NEW ONES 6.1.7 CHANGING SCALE AND ORIGIN ON PART MERGE DOES NOT WORK MIRROR & ROTATE WORKS ON X-PLANE BY NOT Y-PLANE. # OF ENTITIES PICKED, LIMITED WHEN SINGLE PICK THEN REGION PICK. ICEMDDN TRANSLATE DESTROYS DIMENSION ENTITY POINTERS (F.17.3) PROFILE TO ELLIPSOID SURFACE GIVES UNPREDICTABLE RESULTS (F.17.6) PROBLEMS RELATED TO MACHINING ELLIPSOID SURFACE WITH ISLAND SYS-IST CALLED ERROR MESSAGE. CHANGE OF DEPTH PROBLEM. UNDEFINED ADDRESS ENCOUNTERED PROBLEM END MILL WITH CORNER RADIUS GOUGES SURFACE IN PROFILE ZOOM SCALE NAME FROM ENGLISH TO METRIC DOES NOT TRANSLATE CORRECTLY lEW WORKSTATION ONLY DRAGS 1 ENTITY (IEW)PICKS NEAR SCREEN EDGE WRAP AROUND TO OTHER SIDE OF SCREEN (lEW) DIALOG BUFFER CLEARED WITH ENTRY AFTER SCROLLING BACKWARD THE PARTS ON MY TAPE3 ARE NOT ACCESSIBLE (5.13)GPL TEXT COMMAND PUTS: IN CHARACTER STRING TYPE-AHEAD CAUSES STRANGE GRID PATTERNS. TYPE-AHEAD IN TRANSLATION GENERATES FALSE DISPLAY. PHANTOM LINES SHOW UP WHEN AUTO-ZOOMING. SURFACE MILLING CONTAINMENT DOES NOT WORK F.I0.9 LINE THROUGH POINT-PERPTO LINE CREATES A LINE OF 0 LENGTH. GENERATED TOOLPATH OF ROTATED PART COMES OUT IN BEFORE ROTATED PLACE. UNDEFINED ADDRESS ENCOUNTERED AFTER DELETE LAST TOOLPATH. FILLET DOESN'T WORK BETWEEN AN ARC ANn A 2-DEGREE LINE. NEW DISPLAY VALUES FOR LABEL DIM. WILL NOT CHANGE CORRECT MENU ITEM CANNOT CREATE A CORRECT RULED SURFACE BETWEEN A COMP CURVE & MACH CUR ICEHDDN CORRUPTS DISPLAY LIST AT BAUD RATES HIGHER THAN 4800 BAUD PART INTEGRITY DOESN'T FIND PROBLEM, BUT PART MERGE FIXES PROBLEM. RETRIEVED DWG ONLY PARTIALLY PAINTS, THEN LOCKS UP. IGES TRANSLATOR CREATES FONTED DIMENSION LINES LAST CHAR OF 14 CHAR PARTNAME TRUNCATED ON MOVE TO DATABASE DELETING TOOLPATH CAUSES FUTURE CHAIN SELECTS TO STOP INCOMPLETE. ENTITY DRAGGING ONE PART IN GPARTS IS NOT RETRIEVABLE 18.4 DIFFICULTIES IN USE AND ERRONEOUS RESULTS. ICEMDDN CROSSHATCHING IMPOSSIBLE - OPEN BOUNDARY BUG. PP ABORT ON ICEMDDN TO IGES TRANSLATION IF LOCAL ASSIST/DISPLAY=YES,NO NOTES OF ANY KIND WILL BE DISPLAYED MENU 1.14.1 STORAGE/REFRESH DISPLAY DOESN'T WORK IN 1.57 OR 1.6 F.l1.8 MODIFY ANGLES CAUSES BAD ENTITIES ENTITIES NOT DISPLAYED AFTER BEING CREATED OR UNBLANKED F.16.2.6-7 TAIL LOCATION PROMPT INCONSISTENT ------- ---'--'"""---"","""," 81 01/17/86 AD22619 AD22620 AD22622 AD226247 AD226257 AD226260 S U U U U S F.16.2.3 PARALLEL DIMENSION IGNORES CONSTRUCTION MODAL F.16.8.2 FINISH HARK WITH NO VALUE CAUSES' BAD ADDRESS F.16.13.6 MODIFY TEXT INCORRECT IF TWO It_" (MINUS'S) ARE ,USED. FORMAT OF DISPLY COMMAND IS NON-ANSI CLFILE-PARTNO BEING INSERTED BEFORE EVERYTHING ELSE. TOOLPATH DISPLAY DASHED BUT CANON SAYS SOLID 82 01/17/86 C) APPENDIX B: RESOLVED PROGRAMMING SYSTEM ERRORS (PSRs) This section contains a list of system problems existing under previous versions which were resolved in ICEM DON V1.6. PRIORITY CODE: C=CRITICAL U=URGENT S=SERIOUS M=MINOR PSR NO. o AD2A014 AD2A243 AD2A248 AD2A251 AD2A257 AD2A278 AD2A286 AD2A298 AD2A328 AD2A330 AD2A342· AD2A364 AD2A369 AD2A376 AD2A404 AD2A405 AD2A4l1 AD2A418 AD2A432 AD2A440 AD2A455 AD2A458 AD2A461 AD2A462 AD2A463 AD2A469 AD2A470 AD2A477 AD2A478 AD2A481 AD2A493 AD2A496 PRIORITY S S U ·S S S S S M M M M S S M S S U S M U U M S S U U M U M S S PROBLEM ABSTRACT (15.1.3)SURFACE INTERSECTION CURVES NOT WORKING PROPERLY IN ALL. CASES (17.6)15-AXIS END CUTTING HANGS WHEN CONTAINMENT WITH ISLANDS AND TAN (15.1.3.2) SURFACE INTERSECTION CURVE (SPLINE) HAS PROBLEMS. (10.9) LINE THRU POINT PERPENDICULAR TO A LINE DOESN'T ALWAYS (8.6.14) RETRIEVE ZOOM SCALE DOES NOT WORK PROPERLY DURING (12.4.2) VARIOUS STRING - KEY INS CAN CAUSE ABORT AND LOSS OF (1.11.5/R) ATTENTION INDICATORS DISAPPEAR AFTER REPAINT WHEN (7.4) SEQUENCE NUMBERS ARE NOT DISPLAYED ON 4114 (11) REJECT AT RADIUS f STRT ANGLE, END ANGLE GETS ARC/CIRCLE (11.12) BAD POINTER IN REPLACE/MODIFY ARC (9.9.2) "[It AT INDICATE CURVE BACKS UP TO WRONG MENU (8.3.1.1) DISPLAY SINGLE VIEW AT LAST SCALE USED AFTER MULTI (15.3) HEXAHEDRON INCORRECT.WHEN DEFINED OUTSIDE VIEW 1 (15.5.2) FEATURE DEVELOPMENT CANNOT HANDLE 3-D SPLINES (15.1.5) COMPOSITE CURVE--SUBCURVES NOT CONTIGUOUS. (5.5.3/6.6.1) DISPLAY TABLE "EXITS PREMATURELY AND IT'S LOCATION ON SC (6.6.1) LEVEL DISPLAY TABLE INCORRECT & UNDEFINED VIEW GIVES BAD PTR *BAD PTR ON RETRIEVAL OF PART WITH COMPOSITE CURVE. *USER'S MANUAL DESCRIPTION OF MENU 13.5 TRANSLATE IS MISLEADING. *LEVEL TABLE INITIALIZE ERROR. *LATHE NC MACRO NOT COMPATIBLE WITH OTHER NC MACROS. *DELETE FUNCTION INDICATORS INCONSISTENT. (4~13) WRAP-AROUND PROBLEMS WHEN LISTING 80 CHARACTERS (12.1) CHANGE VIEW WHEN AT ENTRY MODE GIVES BAD POINTER (10.19) MODIFY PARAMETERS FOR CERTAIN LINES IS NOT WORKING. THE SPIKE IS BACK ON ROCKY FLAT LATHE PATH P308. POUND SIGNS ARE DISPLAYED IN STORAGE ON 4114. (6.2.2) MENU OVERWRITE PATTERN RETRIEVE OF '<' (MISC.) SELECT BY SEQ NUMBER IS NOT SETTING ATTN IND COUNT CORRECTLY (5.1.3) CANON HAS INCONSISTENT ERROR MESSAGES-BOTH UAE AND ILLEGAL PT (17.11.4) MIRRORING AN NC MACRO FAILS EVERYTIME. (16.3) IMPOSSIBLE TO CREATE HORIZONTAL CROSS HATCHING. . _ - - - - - - - - - - - - - - - - _ . -------_ ............. -._ .._.-._..... _-- 83 01/17/86 AD2A500 AD2A502 AD2A512 AD2A518 AD2A519 AD2A532 AD2A534 AD2A544 AD2A546 AD2A555 AD2A557 AD2A562 AD2A583 AD2A591 AD2A593 AD2A595 AD2A601 AD2A604 AD2A608 AD2A610 AD2A615 AD2A617 AD2A619· AD2A620 AD2A621 AD2A622 AD2A624 AD2A632 AD2A633 AD2A634 AD2A638 AD2A639 AD2A641 AD2A651 AD2A652 AD2A657 AD2A662 AD2A663 AD2A664 AD2A665 AD2A668 AD2A669 AD2A672 AD2A677 AD2A678 AD2A679 AD2A68 0 AD2A681 AD2A683 AD2A685 AD2A686 AD2A687 AD2A688 AD2A689 U M S M S M S S S S S U U S C S S M M U S S S S M U S M U M M C S S S M S S M S S S S S S M M M S M M S S S (MANUAL) LEVEL TABLE NOT ASSIGNED ERROR MESS INCORRCTLY EXPLAINED. ·(MISC) SECONDARY MESSAGE PATTERN BUNCHING TOGETHER COLUMN 4 AND 5 (TABLET) DOUBLE KEY-IN NAME ON 411X AND TABLET. (5.1) F KEY OUT OF CANON WITH MENUS OFF TOGGLES MENUS ON. (16.10) NOTE WITH TEST CONTROL WILL OVERWRITE DURING KEY-IN (5.4) USER CHARACTER DEFINITION HANDLED INCORRECTLY ON 4114 TERM. (5.10) GOTOERR. WHEN RUNNING NEST1 TRACE ON 1ST 3 (12.4) DELETE LST ENTITY IN STRING MENU CAUSES BAD POINTER CAN'T INDEPENDENTLY SET X OR Y MIN/MAX OFFSET FOR PLOT INCONSISTENCIES BETWEEN MENU OPTIONS--INCREMENTAL POINTS INCREMENTIAL POINTS--WRONG PARAMETER VALUE FOR ARCS (12.2) OFFSET CURVES REDUCE MENU PROMPTS FOR ENTITY SELECT OPTION V.A.E. ERROR WHEN MORE THAN 509 POINTS ENTERED EXECUTE A GRAPL PROGRAM WITH ATTRIBUTES EXITS TO OP SYSTEMS ERROR IN NAMING OF N/C TOOL LARGE POINT MOVE ENTRIES PREVENT CONTROL POINT FIT WHEN KEYING AHEAD BETWEEN PARTS TH£ BEEL SOUNDS TEK 4105,7,9 TERMINALS PRINT GRAPL PROGRAM INFO ON ONE LINE 721 TERMINAL IS IMPROPERLY RESET AFTER LEAVING ICEMDDN THE 721 VIKING TERMINL IS LEFT IN ERROR UPON EXIT 721 GRAPHICS TERMINALS RETURN TO GRAPHICS AFTER EXIT ICEMDDN CAN CNTL-D TO DELETE A DATUM TARGET MODIFY DECIMAL PLACES MESSES UP ON FRACTIONAL DIMENSIONS ON 721 TERMINAL DON LEAVES TERMINAL IN GRAPHICS STATE CANT REGION SELECT NESTED GROUPS LEADER BETWEEN BORDERS NOT SHOWING UP IF IT IS MAGNIFIED GPL EVALS STATEMENT--RETURNING DATA ON POINT NOT ON SURFACE PROBLEMS WITH CREATING FILLETS IN GPL BETWEEN ARCS & SPLINES TERMINATING QUOTE GETS WRITTEN TO SCREEN AS PART OF NOTE DISPLAY & EDIT OVERFLOW IN TOOL PATH DISPLAY MODIFY DISPLAY VALUES CAN ABORT OR GIVE UAE SECTION LINING VISIBILITY MODAL HAS NO EFFECT ON SECTIONING 15.2.12.1.1 LINE PICK POSITION UNUSED IN CONE CREATION 9.18.1 & 2 DELTA XT & YT ARE NOT WORKING AROUND FOR COMPOSITE CURVES THE MANUAL DESCRIBING F.3.9 IS INCORRECT 15.2.4 CAN'T USE A DRAFT CURVE TO DEPTH FOR RULED SURFACE WRONG TOTAL LENGTH OF COMPOSITE CURVE AFTER TRIM CURVE THE SMOOTHING FACTOR IS RETAINED AFTER PRELIMINARY COMPUTATIONZHS F.15.1.7.2.2 AFTER ADDING ONE CONSTRAIN (CURVE THRU THE END POINT) MODIFY SURFACE PATHS OF OFFSET SURFACES 2-D ANALYSIS MENUS WORDING OF OPTIONS IN 18.3 INCREASE COMPOSITE SURFACE LIMIT FROM 20 TO 150 N/C DISPLAY & EDIT NOT PROCEEDING TO LAST LINE PROPERLY GODLTA INSERT DOES NOT CREATE TOOL MOTION ALONG TOOL AXIS. OP REJECT FROM 'ENTER DIRECTION' DOESN'T CLEAR ENTITY ATTN A DISALLOWED CURVE CAN BE SELECTED WITH SEQ. NO./PTR/NAME OP REJECT IS NOT PROCESSED CORRECTLY IN SINGLE SELECT BLANK BY CHAIN WITH DISALLOW. CURVES ALSO BLANKS DIS. CURVE IF #1 IS ENTERED FOR DEPTH, MESSAGE DISPLAYED IS IMISLEADING ] AT ACCEPT THIS TOOL ? TAKES USER BACK TO OPERATION PROMPT [ AT ENDING SEQUENCE DOES NOT TAKE USER TO PREVIOUS MENU ] FOR DEPTH INPUT BUMP USER TO NC MAIN MENU FOR LATHE DRILL FACE THREAD FOR LATHE DOES NOT WORK TOO WELL ON LONG LINE 0 0 0 . _... 84 01/17/86 'U CYCLE DOES FUNCTION WITH INSERTED INFORMATION. S SECTION LINING DOES OT APPEAR IN ALL VIEWS AS IT SHOULD S . DATUM TARGET USES A DIAMETER AS THOUGH IT IS A RADIUS U SECTION LINING BREAKS IF SAME ENTITY IS SELECTED TWICE IN A ROW S POINT SET CURVE U MACCRV/INTOF,~,EDGE WORKS INCORRECTLY M Do.CUMENTATION DOCUMENTATION OF MENU'S 8.6.4 AND 8.6.5 ARE REVERSED S S (13.10)STRETCH DOES NOT STRETCH LINES CONNECTED TO LINE TO BE M (16.2/2.7)PROJECT ENTITY TO OTHER LEVEL, THEN BLANKING AFFECT HANGERS S (6.2. 1) CANNOT CREATE A PATTERN USING AN EXTENDED GEOMETRY ENTITY. (13.2)CIRCULAR ARRAYS PLOTTED AS LINE SEGMENTS BECOME OCTAGON. M S (9.17) FAN POINTS AND INCRMENTAL POINTS FAIL FOR POINTSETS. M (15.1.3) INTERSECTION CURVE NOT FOUND FOR SURFACES THAT ARE (16.3)CROSSHATCH OF 1/4 CIRCLE SELECTS SAME QUADRANT ANY SEQUENCE. S S (16.3) CROSSHATCH OF 1/2 CIRCLE USING CIRCLE AND LINE HATCHES M (8.6.11)AUTO MAX/MIN SETS SCALE TOO LARGE IF DEFINE AXIS (10.16) M (8.6.11) VIEW NOT CENTERED ON AUTO MAX-MIN OF PART M (13.5) ENTITIES NOT TRANSLATED CORRECTLY IN SOME VIEWS. S (RESCALE) DOES NOT WORK CORRECTLY FOR METRIC PART. S (6.2.6) GLOBAL PATTERN OVERFLOW. S (3.7.5) 3 BALLOONS DELETED AS ARRAY AND GROUPS. U (17.12)3-SURFACE PROFILE DOES NOT WORK; LOOPS THROUGH DRIVE, PART S *(16.3) CROSSHATCHING SHOULD ONLY DISPLAY IN VIEW OF DEFINITION. S (6.2.1) GROUPS ARE NOT LEGAL ENTITIES FOR PATTERNS. U *TABLET/TERMINAL BECOME INACTIVE. U *NC - DISPLAY & EDIT TOOL DISPLAY IS VERY BAD FOR ALL MILL USE. S *(16.2) PROJECTED ENTITY NOT ON SAME LEVEL. U *(15.22) SURFACE OF REVOLUTION DEGENERATES AT CENTER. M *PLOT SCALING INPROPERLY CALCULATED WHEN TEXT IS IN DRAWING. S *AFTER OP REJECT, SYSTEM WILL RE-PICK THE SAME ENTITY. S *(16.13.5) MODIFY TEXT DISPLAY VALUES WILL NOT ALLOW FOR VARIABLES. S *(6.2.1-GLOBAL) GLOBAL PATTERNS WITH THE NAMES WILL NOT RETRIEVE. S *MENU #6.2.2 PATTERN RETRIEVE - PATTERN NAME DOES NOT MATCH PATTERN. U *FAN POINTS HAVE INTEGRITY AND CONSISTENCY PROBLEMS. U *GRAIOF DOES NOT SUPPORT' LOWER CASE LETTERS IN CD2000. S *(6.2.6) GLOBAL PATTERN DIRECTORY PROBLEMS. U *(6.2.2) GLOBAL PATTERN DIRECTORY LIMITS. S *(13.10) STRETCH BY SCREEN POSITION WILL NOT RESPOND TO GRID ACTIVATE U LINES--CONSTRUCTION OF LINE PERP TO LINE THROUGH POINT IS UNRELIABLE. S (11.10)ARC INSCRIBED IN 3 LINES IS INCORRECTLY DRAWN IN CERTAIN CASES U *VIEW NUMBERING DURING DEFINITION OF AN AUXILIARY VIEW F.8.9. U 2-D SPLINES DO NOT WORK WELL AS TRIM BORDERS (12.8). S TRANSFORM COORDINATES POINT DELTA DIFFERENT IN 1.47 THAN 1.45 (9.4). U *ROTATE (13.6) FOR ARCS ABOUT AXIS CREATES 'THEM IN A NEW VIEW. S *INCORRECT DEPTH OF LINE TANGENT TO AN ARC AT AN ANGLE. U (5.7) DATA GRAPHS LINE FONT PROBLEMS. U HYPERBOLA NOT DISPLAYED IN DETAIL MAGNIFICATION U ELIMINATION OF UTF BY COMMON PATTERN LIBRARY U TEXT MOVES INCORRECTLY WHEN TOLERANCE IS ADDED U MIRROR ABOUT A POINT??????????????? U PROBLEM WITH FAN POINTS ON CURVE CONTAINING MULTIPLE ENTITIES U NEED THE ABILITY TO TRIM USING SCREEN POSITION U FAN POINTS OUTPUT INCOMPLETE SET OF POINTS AD2A691 .AD2A695 AD2A696 AD2A697 AD2A700 AD2A701 AD2A703 AD2A718 AD20400 AD20477 AD20482 AD20530 AD20546 AD20560 AD20591 AD20592 AD20626 AD20637 AD20642 AD20662 AD20701 AD20720 AD20768 AD20774 AD20822 AD20846 AD20928 AD20944 AD20956 AD20962 AD20996 AD21020 AD21022 AD21024 AD21031 AD21043 AD21050 AD21051 AD21057 AD21065 AD21079 AD21107 AD21131 AD21137 AD21145 AD21150 AD21172 AD21178 AD21180 AD21182 AD21188 AD21189 AD21190 AD21191 _--_._._-_ - "-"._.,,-'._--_.,,_ ..... ...... -.""-,--,-,---,-_.,,. __ .,-- "-'.- ----"., " .... '---'-'-'- ------------------~- \,/' 85 01/17/86 ,-/~ AD21192 AD21194 AD21207 AD21209 AD21215 AD21234 AD21246 AD21268 AD21273 AD21293 AD21295 AD21296 AD21303 AD21307 AD21311 AD21312 AD21317 AD21320 AD21321 AD21326 AD21337 'AD21345 AD21360 AD21378 AD21383 AD21395 AD21403 AD21437 AD21438 AD21440 AD21445 AD21460 AD21465 AD21468 AD21470 AD21471 AD21480 AD21481 AD21501 AD21507 AD21508 AD21525 AD21527 AD21544 AD21545 AD21547 AD21570 AD21571 AD21572 AD21576 AD21578 AD21583 AD21590 AD21591 . S U U U C S M S C U U 5 U M M U U U U M C U U U U 5 S S M U 5 U 5 S 5 S M M 5 U U 5 5 M M S S U 5 5 U 5 M S ATTENT~ON \ BLIPS END UP IN STRANGE LOCATIONS FOR TRIMMING (POINT NEAR) "'~ . -' DISPLAY AND EDIT IS AWKWARD AND TIME-CONSUMING. LATHE TOOL DISPLAY CANNOT BE CHANGED(1.49X) CANNOT TRIM CIRCLE USING TANGENT CIRCLES AS BOUNDARIES(1.49X) *F.1.11.3.1 *CIRCULAR DIMENSION CAN ONLY BE PLACED IN VIEW ARC BEING DIMENSIONED MISTAKE IN VERSo 1.5 MAIN OVERLAY, CHANGE SCALE SHOULD BE CHANGE PAGE DISPLAYING MAIN MENU HEADER-NO CHECK IF HEADER FITS IN AVAILABLE SPAC *TOOL DISPLAY/CYCLE STATEMENTS. *VIEW LAYOUT: WHEN CHOOSE OPTION TO RESIZE INTO NEW WINDOW PROBLEM. *NEED TRIM TO SCREEN POSITION. *CROSSHATCH BOUNDARIES DIFFICULT. *MODIFY REGION SELECTIONS. *DATA VERIFY TO INCLUDE LEVEL/PEN. *DELIMITER FOR CENTERLINE. *INCLUDE BALLOONS IN PATTERNS. UNUSED CODE CHAIN SELECT USING TABLET. PRESELECT CHARACTERS-A,P,L-NOT RESET TO 'c TRIM USING TABLET. PRESELECT CHARACTER-A,P,L-DON'T GET RESET TO 'c' *15 THE RESCALE PROMPT NECESSARY? *VIEW ALIGNMENT IN A LAYOUT. SYSTEM REL/REV NUMBER ATTENTION INDICATORS DISAPPEAR BEFORE OPERATION IS COMPLETED. TRIM BY SCREEN POSITION NEEDED WANT ABILITY TO SELECT ENTITIES BY COLOR LEVELS OR ENTITY TYPES f", THE SELECTED CURVE PARAMETERS SHOULD BE DISPLAYED IN INCREMENTAL PTS~_./ TP BLOCK EDITING/EDITING OF DIMENSIONS AFTER CR~ATION PLOTTING IGNORES TEXT IF IT IS TOPMOST OR RIGHTMOST ON DRAWING. ATTENTION MARKERS ARE NOT DROPPED WHEN SELECTION WAS CANCELED. ONE GRAPL ONLY COMMON. ALLOW GRAPL TO ACCESS COMMON FOR BOTH READ AND WRITE. CREATING A PATTERN CAUSED MODE ERROR NC DISPLAY AND EDIT WILL CHANGE LINE NUMBVERS DURING EDITING N/C - TOOL PATH EDITOR INSERT MOTION VECTORS DISAPPEAR LATHE DRILLING PRODUCES WRONG CENTERING MOTION LATHE DRILLING DOES NOT ALLOW CONTROL OVER DWELL RESCALE QUESTION DISRUPTS FLOW OF TRIM OPERATIONS GROUP IS NOT SELECTED IN SCREEN SELECT MODE FOR PATTERNS UNABLE TO DIMENSION PARTS UNDER DETAIL MAGNIFICATION. RELEASE PATTERN LIBRARY. INCREASE PATTERN NAME TO 16 CHARACTERS. RESCALE QUESTION AFTER EACH OPERATING WHEN SMALL AREA IS ZOOM PATTERN RETRIEVAL IS CUMBERSOME. (5.2.2.)DESIRE CENTERLINE FONT WITH GRAPL COMMAND. (5.2.5)ADD MESSAGE DISPLAY TO PAUSE/GRAFL COMMAND FOR ACKNOWLEDGEMENT (5.5.2)DESIRE ABILITY TO NAME ANY LEVEL (MRE THAN 62) ANY SEQUENCE. *(5.5) WOULD LIKE COMMAND TO MOVE ENTITIES BY LEVEL RANGE (1.7)WOULD LIKE TO MODIFY ENTITY LEVEL WITH ENTITY TYPE *(5.5.X) ALLOW 1024 LEVELS WITH NAME DESCRIPTION IN LEVEL (6.2.2)RETRIEVE PATT~RN - CHECK FOR NEW INFO IN WORD (3). (6.1.8/4.N)MOVE PACK/FILE AWAY FROM FILE/NO/TERMINATE ON *(16. 15) BALLOON DETAIL-NO. HAS ONLY 3 CHAR, INCREASE TO (6.1.5) WOULD LIKE DELETE PART TO REMAIN IN KEY IN NAME MODE. (6.1.2.1)WOULD LIKE GLOBAL RESTORE SINGLE TO REMAIN IN KEY .r: r' ...~~ . o o 86 01/17/86 AD21601 AD21616 AD21617 AD21619 AD21633 AD21669 AD21672 AD21677 AD21702 AD21712 AD21713 AD21717 AD21733 AD21757 AD21762 AD21765 AD21794 AD21804 AD21814 AD21824 AD21840 AD21865 AD21868 AD21886 AD21889 AD21890 AD21897 AD21899 AD21900 AD21904 AD21907 AD21909 AD21911 AD21914 AD21924 AD21928 AD21929 AD21930 AD21932 AD21937 AD21961 AD21971 AD21996 AD22011 AD22015 AD22025 AD22028 AD22030 AD22031 AD22038 AD22050 AIi22064 AD22071 AD22081 U S S U M U M M U U U U U 1 U U S S U S U U U U U U U U U U U U U U S S U S S S U M U U M M S U C M U S C U (6.1/6.2)ACCESSING GLOBAL PART AND PATTERN FILES SHOULD BE (3.9)WOULD LIKE DELETE ALL OF A LEVEL BY REGION IN/OUT. (16.2)WOULD LIKE REGION SCREEN SELECT MODE FOR PROJECTED WOULD LIKE FILE/TERMINATE MOVED AWAY FROM DELETE LAST (12.8)NEEDED CHOICE OF SCREEN POSITION FOR BOUNDARY MODE FOR (3.2/2.1) ALLOW MORE ENTITY TYPES (16.13.5) MODIFY TEXT BY SINGLE/REGION AS WELL AS ENTITY. (16.13) MODIFY DRAFTING ENTITY NEEDS MULTIPLE ENTITY SELECT. (INIT)CHANGE METRIC/ENGLISH QUESTION TO A MENU. (6.1.9)DRAFTING STANDARD ON INDEPENDENT SAVE •. (16.3)INCLUDE CURRENT DEPTH ON CROSSHATCHING. (16.3/8)DISPLAY CROSSHATCH IN VIEW OF DEFINITION. (13.5)ENHANCE WAY TRANSLATE AND SCALE OF PATTERN IMPLEMENTED. (6.6. 1) ENHANCE GLOBAL PARTFILE/GLOBAL PATTERN FILE HANDLING. (REGION)REJECTED LAST REGION SELECTION NEEDS ENHANCEMENT. ADD OPERATION THAT RETURNS FILE TO BEFORE LAST OPERATION. (SCREEN SELECT) REGION IN AND OUT SHOULD BE IN ABOVE MENU (2)BLANK BY NAME. (2.7)ABILITY TO BLANK BY LEVEL. *WORKVIEW SHOULD REMAIN THE SAME IN MULTIPLE VIEWS. 3D MANIPUL OF PATTERN TOOL PATH (DURING PATTERN RETRIEVE). *ATTENTIONS ARE NOT SET CORRECTLY AT SINGLE AND REGION SELECT. SELECTION OF DRAFTING STANDARD SHOULD BE CONSEQUENTLY A MENU OR (7.13) TABLET FILE HANDLING TOO RESTRICTED ANn INSUFFICIENT. (4) CHANGE FILE/TERMINATE TO MENU CHOICES RATHER THAN YIN. (REGION) SELECT, ATTENTION BITS NOT SET. (CTRL-F) NOT RECOGNIZED DURING TABLET INPUT SEQUENCE. PFM23 CONTAINS ALSO LIST OF GLOBAL PATTERNS. (REGION) SECOND BOUNDARY INDICATOR NOT DISPLAYED AS USED. (5.4) USER-GENERATED CHARACTER NOT CENTERED DIMENSION TAIL. BAD POINTER.AT ARC-3D ROTATION IF MORE THAN 84 ENTITIES IN PATTERN (1/1) LETTER I ENLARGED TO DISTINGUISH FROM DIGIT 1. (REGION) NO CHECK MADE FOR ATTENTION ON. (1.7) ATTENTION RESET NOT CORRECT AT MODIFY LEVEL/PEN. (16.4/.9) DROP LEADING ZEROES. *ENHANCEMENT DISPLAY AND EDIT TOOL DISPLAY *GRAPL: PRINT VARIABLES TO SCREEN. *GRAPL: BETTER ERROR CONTROL'. *GRAPL: SCREEN CONTROL. *GRAPL: NUMERIC STRING VARIABLES.' *NC - DISPLAY & EDIT ADD MENU CHOICE TO SKIP TO END OF PATH. *(7,13) THERE IS NO WAY TO DELETE A "TABLET" FROM TFILE. *ONLY 64 OF 1024 LEVELS MAY BE NAMED. *RESCALE? CAUSES PROBLEMS AND IS UNNECESSARY. *LEVEL MANAGEMENT. ADD "DELETE OLD TOOLPATH" PROMPT TO TOOLPATH REGENERATION TRIM OFFSET CURVES OF FILLET NOT WORKING CORRECTLY PART CHECK DOES NOT INCLUDE A CHECK FOR ZERO LENGTH LINES NO CONFIRMATION WHEN DELETING/OVERWRITING GLOBAL PATTERNS MENU 1.10 ON THE ICEM DDN OVERLAY STILL READS TOGGLE BLANK/UNBLANK. (F.17.9) CONSTANT SURFACE SPEED IN ,ICEM N/C LATHE, & MODAL SETTINGS DIAGONAL SCREEN POSITION DOES NOT WORK AFTER CREATING A LAYOUT *REPAINT REQUIRED TO SELECT ENTITIES. GROUPS IN PATTERNS - - - - - - _...._.-...._....... - . _....._.._ - _ . _ - - - - - - - - - - .......- .. _._ .......... _--._-. ·" 87 01/17/86 AD22086 AD22090 AD22092 AD22094 AD22095 AD22096 AD22097 AD22099 AD22100 AD22106 AD22113 AD22141 AD22142 AD22147 AD22153 AD22159 AD22164 AD22165 AD22172 AD22188 AD22196 AD22206 AD22210 AD22215 AD22224 AD22231 AD22235 AD222S0 AD22252 AD22253 AD22260 AD22262 AD22264 . AD22265 AD22273 AD22278 AD22294 AD22296 AD22298 AD22301 AD22304 AD22318 AD22322 AD22323 AD22328 AD22329 AD22346 AD22369 AD22373 AD22374 AD22375 AD22376 AD22378 AD22381 S S S M M U S S S S S U U S U M S S U C U C S C S C S U S M M S M S U S U S U U S C U U C C U U M S U S C M ~-......, LATHE TURNING OF A SINGLE ENTITY 1\ F.17.9 - GROOVING TOOLS WITH 0 TOOL NOSE RADIUS EXCHANGE FEEDRATE TRUNCATES UNIT PARAMETERS SUCH AS IPR F.S.8 - PPMACRO F.17.17 - NC MACRO EDITING F.17.11 - DISPLAY & EDIT F.17.9 - LATHE TOOL HOLDER DISPLAY F.17 SUPPORT OF APT CYCLE STATEMENTS IN ICEM N/C F.17.10 USER-DEFINED CYCLES. COMPACT II TRANSLATION WITHIN ICEM DDN ICEM DDN EXCLUDES THE OP-COMPLETE] IN THE TABLET STRING ENTITY SELECT OF CENTERLINES NEEDS IMPROVEMENT DATUM DIMENSIONING IS NEEDED OFFSET PLOT LEAVES VALUES IN X,Y REGISTERS NEED ABILITY TO CREATE A CIRCLE TANGENT TO THREE ENTITIES ENTITY FLAG SHOWN IN ODD LOCATION WHEN BLANKING PROVIDE AN OPTION TO LIST TABLET PAGE NAMES. A MASK KEY FOR PICKING ONLY CENTERLINES IS.NEEDED. HORIZONTAL AND VERTICAL DIMENSIONS WILL NOT ACCEPT CENTERLINES CANNOT SELECT GEOMETRY FOR ANY OPERATION CHAIN SELECT OF INES AND AN ARC RESULTS IN ERROR--SEE DAYFILE ZOOM DISTORTS LAYOUT FRAMES SCALE TO PART SCALE N/C TOOLPATH EDITOR FAILS TO UPDATE VECTORS IN 4115 DISPLAY HARDCODING CLASS 2000 WORDS CAUSES INCOMPATIBILITY WITH G-POSTS CROSSHATCH IN. A "DETAIL MAG." DOES WRONG AREA IF BALLOON LEFT MODIFICATION OF DIMENSIONING METHOD F.17.10 - GLOBAL TOOL LIBRARY BULKIN DATA ERROR IN ROTATING NOTES MANUAL IS INCORRECT ON TERMINAL SETUP NC MODALS SHOULD INCLUDE LATHE IPM/IPR MODE A REJECT AT SCREEN SELECT IN LATHE BACKS UP TO LATHE OPERATION CAN NOT BACK UP PAST STOCK AND CUT ANGLE PROMPT IN LATHE REJECT IN DISPLAY AND EDIT RETURNS TO NC MANUFACTURING MENU LATHE PACKAGE PICKS UP DEPTH SET IN SYSTEM THREE-SURFACE PROFILE CREATES TIME LIMIT PROBLEMS. A CNTL D ENTERED IN DISPLAY AND EDIT PRODUCES UNDEFINED ADDRESS F.7.2 PLOTTING ROUTINE CAUSES DATA BASE PROBLEMS IF SCALE IS NOT = 1 ADD OPTION FONT/CENTERLINE IN GRAPL F.17.2 - POINT TO POINT PUNCHING NEW ORIGIN OF PATTERN DIMENSION TEXT GIVES WRONG ARROW LOCATION. BULKDATA CIRCLE,2 CAUSES MODE ERROR CREATES INCORRECT GEOMETRY FILLET BETWEEN POINT AND SPLINE FAILS THE NUMBER "1" AND tHE LETTER "I" LOOK IDENTICAL IN TEXT. 1.7 ENTITIES GO TO CURRENT LEVEL OR PEN NUMBER IF NOT CHANGED. DECIMAL PLACES IN DIMENSIONING METRIC PART DRAFTING ENTITY MODIFICATION IS INACCURATE (7.2) AUTO MAX/MIN REQUIRED WITH PLOT/SCALE FROM GEOMETRY. (16.2)LINEAR DIMENSION W/DUAL DlMENS.;O DECIMAL PLCS HANGS DDN MODIFY ENTITY'S LEVEL/PEN NUMBER F.18.l SLOPE VALUES FOR SPLINE ANALYSIS ARE QUESTIONABLE BY DEF. F.18.1.6 SPLINE ANALYSIS OMITS AND PRINTS ERRONEOUS INFORMATION F.18.1 BKC PREFERENCES FOR TAPE4 PRINTOUT OF SPLINE DATA 15.1.4 DRAFT CURVE GIVES ARITHMETIC MODE ERROR CONSISTENT USE OF IMPLICIT POINTS. .......~ ....... CI C) 88 01/17/86 o AD22382 AD22383 AD22388 AD22395 AD22398 AD22401 AD22412 AD22413 AD22414 AD22415 AD22417 AD22421 AD22425 AD22429 AD22447 AD22449 AD22454 AD22464 AD22468 AD22482 AD22486 AD225 06 AD22514 AD22537 AD22541 AD22554 AD22558 AD22569 AD22575 AD22596 AD22599 o . -- ._-_.._-, - - - S M C S M U U U U U S S M S U C U M C S M U M S U M S U U S Ii- DRAFTING LABELS. (12.8) WOULD LIKE TO BE ABLE TO TRIM MORE THAN ONE CURVE AT POINT. 16.5.4 DATUM TARGET, CIRCLE GIVES WRONG SIZE TARGET AREA. SIZING OF LOCAL PATTERN LIBRARY 6.1.2.2. NOT CONSISTENT W/OTHER COMMANDS CREATE TOGGLES TO SPECIFY SCREEN OR ENTIRE DRAWING FOR BLANK & UNBLAN F.16.3-SECTION LINING BOUNDARY IS OPEN AT * DOES NOT APPEAR IMMED. F.16.7 "GEO TOL" DOES NOT PROVIDE A SPACE BETWEEN LEADER AND ENTITY F.16.8 SURFACE TEXTURE SYMBOL CANNOT BE DELETED. F.13.5/F.16.8-TRANSLATION OF SURFACE SYMBOL IS ERRATIC. F.16.1.3/F.16.13.1-AUTO-TAIL LOC INCOMPATIBLE W/NEW ORIGIN. BASE SCALE DOESN'T WORK PROPERLY WITHOUT ALIGNMENT OF VIEWS MODIFYING USER PAGE YOU ALWAYS HAVE TO GO THROUGH STORE PAGE PICKING CENTER LINE 19.2 RESIZE ROUNDS OFF ALL FRACTIONAL DIMENSIONS. DATA GRAPHS DON'T FUNCTION DATUM TARGET DOESN'T GIVE YOU A SELECTABLE CENTERLINE. 2 BLANK/UNBLANK HAS DOCUMENTATION ERRORS F.16.11 LABEL CREATES UNPICKABLE ENTITIES GPL COMPILER DOESN'T ABORT ON SUBROUTINE FATAL ERROR (F.17.6) SCALLOP HEIGHT DEFAULTS TO 0.05 IN BOTH METRIC AND INCHES. YOU SHOULD BE ABLE TO SCREEN SELECT TABLET SQUARES WHEN EDIT. CAN'T DO A FILE/SUSPEND FROM THE SUPPLIED TABLET OVERLAYS F.12.4.3[ STRING BY POINTS CANNOT BE [ OUT OF. F.12.8 TRIM USING TANGENT ENTITIES ERROR'S:INTERSECTION NOT FOUND. F.16.13.5 DRAWING LIMITS DUPLICATES TEXT THAT IS AFTER DIM. NUMBER SELECT VIEW UNBLANKING DOES NOT PERFORM PROPERLY .THE (+/-) AND DEGREE (0) SQUARES ON THE TABLET DON'T WORK IN 1.57 5.13.3 POSITION PICKS WHILE RUNNING GPL DO NOT GO TO GRID POSITION DEGREE SYMBOL ON TABLET DOES NOT WORK. COMPILATION ERROR ON SAVE COMMAND 1,"'--""'" C\, / 89 01/17/86 "\ ~) APPENDIX C: 800 TUNING GUIDE FOR ICEM DON 1.0 INTRODUCTION: BACKGROUND - PROBLEMS The tuning of 800 Systems has not been explored to the extent we would like. This guide will explore possible solutions to some of the common tuning situations. c) The main problem is that users are expecting to setup and run the hardware/software with no adjustments. This practice causes the site to run with the default setup parameters which were built for a small job environment. ICEM DDN is usually overlay bound and has a rather large field length. Depending on the disk configuratio~, the site is usually disk bound due to overlay loading and swapping ICEM DON to disk. In the cases where the site has a lot of memory, the memory is not being utilized because no one has designated it as a "DE" equipment for ICEM DDN overlays and/or a swap device. Because system arialysts do not have a quantitative method of ascertaining what tuning functions cause improvements, tuning is not attempted. By using CPO, CTIME, RTIME, and ICEM DON trace files, an"objective index of performance can be obtained and improvements made. o - - - - - - - - - - - - - - - - - - _ _._._-_._. __ .. .... -_._.-.. _--------------------_. / 90 01/17/86 2.0 OVERVIEW OF CYBER 800 2.1 800 FEATURES The 800 has the following features: o * The 800 has a high speed central processing unit that runs with a memory that can be very large - 2 to 128 megabytes (262 thousand to 16 Million central. memory words). * * * The cache memory speeds up effective memory cycle. * The range of ability for each machine has more than one dimension. As you go up the line in CPU power, the memory size can also be upgraded. Peripheral processors operate at 4 times the original PPU speed. The 800 microcoded instruction set allows both NOS and NOS/VE operating systems to exist and run in the same machine (dual state) • The following chart shows the different models and the allowed memory size options and multiple CPU option: MODEL 810 815 825 830 835 840 845 850 855 860 o MEMORY SIZE OPTION (Megabytes) 2 4 8 12 16 32 64 96 128 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Dual CPU NO NO NO YES NO NO NO NO YES YES It is the memory expansion characteristic that is most interesting for large applications like ICEM DDN. It has been observed that customers are overlooking the ability of the 800 to use this memory in many different ways. 91 01/17/86 2.2 800 MEMORY USE The 800 memory can be used in the following ways: 1) Job area - the job execution area is normally about 262K but can be bigger or smaller. 2) Swap area - Rather than roll the job to disk, it can be swapped from memory to memory and avoid the disk accesses. 3) System resident - specific overlays and/or PPU programs can be stored and retrieved from memory and also avoid disk accesses. 4) NOS/VE execution area. All the above memory allocations are controlled by deadstart parameters in the CMR, EQP, and IPR decks. o 92 01/17/86 3.0 TUNING .METHODS 3.1 STEPS FOR TUNING The following is a summary of the steps you can go through to tune 800s for ICEM DON: 1) Run CPO - Find what the botttenecks are. Tune by making NOS configuration changes such as system resident and channel/disk configuration .(see section 3.5). Check disk use percentages from the CPD run. 50-607. is pretty high. Moving overlays to eM (Central Memory) or UEM (Unified Extended Memory) and/or allowing ICEM DON to run as system resident will help speed up the product and decrease disk access. Also, try to arrange your configuration so that equal access is occurring across all disk channels. AVoid channel 0 because it cannot be alternated in each mass storage device Equipment Status Table (EST) entry. o 2) Run ICEM ODN with the T option on and collect overlay load numbers (CT file) for a given script. The IT file resulting from the T option run is used for input (I=lfn) so that the run can be repeated for comparison after each tuning attempt (base timing). A program included on page C-14 of this Tuning Guide appendix counts and sorts the counts by overlay for each overlay that was loaded during the script execution.3) Based on CPD and the CT counts, move selected overlays into CM (Central Hemory) and/or UEM (Unified Extended Memory). In level 630 of NOS a limited number of overlays can be put in CM, and near 400K the system hangs. The work~round is to put additional overlays in UEM. At this level of the system, there does not seem to be any performance difference between overlay loading from CM or U~. 4) Recheck response time by running a script in a quiet system with CTlME and RTlME control cards on each side of the ICEM ODN call. These numbers will tell you the amount of CPU time and real time used to make the run. Also, rerun CPD to check what is happening to the system resources. There is a Timesharing Instrumentation Package which measures response time, think time and transaction rates of IAF (LOS Publication number 15190016). This package will show how tuning has affected response time. o 93 01/17/86 3.4 ICEH DDN SYSTEM RESIDENT The advantage of having ICEM DDN system resident is that when it is in the system, more than one copy of the code is available from multiple disk channels. Also, selected overlays can be resident in CM. Do not bother moving ICEM DDN to the system if you have only one ~hannel to disk and you do not want to move overlays to CM or UEM. Also, remember that ICEM DDN will "increase your system file by about 70K PRUs on each device that is designated as a system devi.ce. On small capacity disk systems put ICEM DDN on the deadstart tape rather than on a permanent file which is SYSEDITed after deadstart. This will save 70K PRUs of permanent file space. GPL overlays must be on a local file at execution time for GPL users. It currently does not run any other way. 3.3 ICEM DDN OVERLAYS IN CENTRAL MEMORY The problem with NOS 800 performance is caused by ICEM DDN having to load overlays from the disk. Generally, if the most frequently called overlays can reside in memory, the disk accesses will be much lower. If all the overlays that are called are put in memory, a script will run ~s well as it would on NOS/VE (virtual environment). Of course, the data caching will not be as good as VE but the performance should be considerably better than before the overlays were put in CM. Following is an exampl~ of the performance improvement on an 855 with the overlays in CM and other numbers showing relative performance: SYSTEM ------ 760 NOS Running time CPU time Comment ------- ------------ --------13 12 48 78 DDNlS3 on 844s (System file) DDN1S3 on FMD's 830 NOS/VE 810 NOS/VE 374 18 78 138 760 NOS 760 NOS 371 291 7 7 DDNlS7 on 844s (System file) DDNlS7 on FMDs (Local file) 855 NOS 855 NOS 267 160 9 9 DDNlS7 on Disk (Sys tem fi Ie) 3 overlays in CM+System file 855 NOS/VE " " " " " " ~, ....../ 94 01/17/86 (J The 100 second improvement for the 855 NOS is caused by reducing disk accesses. In theory, if all the overlays that are called are put in memory, the script would run as well as the 855 NOS/VE (18 seconds). Also, notice the CPU time for each of the above machines. The CPU time requirement for DDN157 is less than DDN153. The 830 and 810 is 4 and 6 times less capable than the 760 or 855. If the site is CPU bound, the moving of the overlays into memory may not help response time during periods of CPU saturation. The following table summarizes the overlay situation with a typical script: Overlay ------- o CL04 CL52 CL02 CL72 CL270 CL75. CL51 CL14 CL54 Load Count ---------- Field Length of Overlay* ----------------------53040 52551 43215 23066 44031 60042 54513 41300 30441 276 247 136 135 97 88 62 '56 48 Accumulated Sum* --------------54K 126K 171K 215K 261K 340K 415K 457K ,507K * Field length and sum are in octal. These 9 overlays were loaded 1145 times. There were 1442 overlay loads in all with a total of 32 overlays used. After the 4th or 5th most frequently loaded overlay, the payoff from having the overlay in Central Memory (CM) goes down. The rest of the CM can be used for swap area. Both of these uses take away some CPU usage that would be normally available to user programs. But because most sites are disk bound, the swapping and overlay loading from memory to memory saves on disk access and speeds up the user response time. o If CPD runs and RTIME and CTlME control cards are used around a script run before and after these tuning suggestions, the effect can be measured. With less disk access the product (ICEK DDN) will speed up and will make more use of the CPU so that swapping and overlay loading will occur faster. This can have a secondary effect of causing more CPU utilization due to more jobs (through CPU swapping) having access to the CPU and less disk access due to overlay loading from memory to memory loading. This secondary effect may necessitate a reduction in the the job switch delay so that the CPU is shared better between competing jobs. In any case, the above tuning should have a positive effect on response time for the average lCEK DDN user • _---------,.,,_ .. - . -.-- --- _._----_.---- ---- -- -- -- 95 01/17/86 ~, 3.4 CPU'BOUND 800 If your site is CPU bound (95-99%) , the moving of overlays to Central Memory may cause the individual ICEK user to run a lot faster but when a large terminal load is present the total throughput may decrease. You may take steps to decrease the CPU usage to optimize. Because the CPU is used to move overlays around in memory, the moving of overlays to disk may decrease CPU usage. This will slow down the terminal response for the user at lightly loaded times but should make the user at CPU bound times run better. This situation seems to be rather rare and is found only on the 825s and lower machines. In determining if your site is CPU bound do not be misled by maintenance jobs or batch jobs which use the CPU when the time-sharing jobs are not running. 3.5 CPD READING CPD or TRACER (NOS System Maintenance Reference Manual - 60459300) and PROBE are used for statistical analysis of your system performance. The data is used to determine areas where problems occur and where improvements in design and system tuning can be made. These products work by periodically gathering data about the system and writing the data to a file. TRACER is made up of 4 programs: 1) ICPD - Starts up CPD PPU program 2) CPD - CPD is a dedicated PPU program which mon-i tors sys tem activity. Data is written to a direct access· permanent file for future analysis • . 3) ACPD - A post-processor program which generates an output report from the direct access permanent file written by CPD. See the NOS Maintenance Manual (60459300) for details of calling parameters for TRACER. The following sequence will start and complete TRACER operation: 1) ICPD,pl,p2, ••• pn. (~tarts CPD up) (ends CPD data gathering) 2) ENDCPD. 3) ACPD,pl,p2, •.• pn. (processes the CPD data and generates a report) The ACPD report is in three sections 1) System parameters and EST configuration. 2) Sy~tem Control Information. I \.. ... 96 01/17/86 C) 3) Interval Samples.· 3.5.1 SYSTEM PARAMETERS AND EST CONFIGURATION The System Parameters relate such things as the start ·date and time, report interval, memory size, UEM, number of PPUs and various lengths of software tables. The EST table is dumped showing the channel and disk connections. 3.5.2 SYSTEM CONTROL INFORMATION The System Control Information relates what the priority is for each job class. The BC, TS, and D1 classes are especially important to good system response. The BC and D1 should have a lower PR (CPU priority) than the TS class. This will allow time-sharing to always get the CPU before BC or D1 can get it. o The other important parameters are the UP (upper priority limit) and LP (lower priority limit). These parameters are set based on how often batch jobs are rolled in and out without ever getting executed. If there is usually a lot of CM available, t·he UP and LP can be lower for batch and detached jobs than for time-sharing' jobs. These parameters control the rolling out of batch or detached jobs when a time-sharing job requests more memory than is currently available. If the execution memory is small in comparison to the field length requests, the batch and detached jobs should have the same UP and LP so that jobs are not rolled in and out without doing any work. The NJ parameter can help this situation. By controlling the number of batch jobs that can execute at the same time, the batch field length can be controlled. The NJ parameter for time-sharing controls the number of users allowed. The FL and AM parameters for each job class can be designated to limit by job and/or job class how much Field Length (FL) may be used and when to schedule the job to CM. These parameters can be used to partition the memory by job class and run specific jobs at a selected time of the day. The CM parameter controls how long the UP priorities are in effect. With faster CPUs a short duration (4-5 seconds) is desired so that users that are running batch jobs in time-sharing mode are dropped down to the batch priority (assuming that batch priority is the same as the time-sharing lower bound priority). Thus, short duration time-sharing tasks will get the most attention • ._" ...._. __ .. _.__ .. .. ... ""_._"_.,,._.__......,,._. __ ...._" .._..•._-_.. " " _--_.• .. _".. _---" ... "----",, •.. __ ._... .._ " - - - , , - - - - - - - - - _ _ 97 01/17/86 3.5.3 INTERVAL SAMPLE The following table shows some of the parameters and what action might be taken to improve performance when a high percentage of use is shown: Parameter (high percentage) PPUS ACTIVE NO PPU AVAILABLE CHANNEL ACTIVE CPU USAGE IDLE SYSTEM SUB-SYS SYS ORG USER FL AVAILABLE IAF USERS TRACKS AVAILABLE Not enough Disk Channels or PPUs. Same as PPUS ACTIVE. 40 + up means there are not enough disk channels. High idle percent means the CPU is not being used could be caused by the system being disk bound. System Software using excessive cpu. Same as SYSTEM. Same as SYSTEM. You are getting as much as you can out of the system. Application CPU usage may be excessive. Large percent is good - lots of room to run jobs. Number of users. When a device has only 10% of its tracks available the system automatically does not use this device for TEMP files. TOTAL ROLLOUTS SECONDARY ROLLOUTS TOTAL SECTORS ROLLED SECONDARY SECTORS ROLLED INSUFFICIENT CM NO CONTROL POINT Cause/Information The statistics on total and secondary rollouts . will tell you if your secondary rollout threshold is large enough and how much your secondary rollout device is being used; Number of times no CM was available to bring in a job. This number will tell you if you have enough control . points defined. 3.6 PROBE SECONDARY ROLLOUTS will tell you if your secondary rollout threshold TOTAL SECTORS ROLLED is large enough and how much your secondary rollout SECONDARY SECTORS ROLLED device is being used. 3) The number of PP requests to CPUMTR by function number. 4) The number of MTR requests to CPUMTR by function number. S) The statistical data accumulated in low central memory - includes such items as number of sectors rolled and number of rollouts. PROBE data gathering is enabled at deadstart time by an IPRDECK entry. SYSEDIT resets the PROBE data tables to zero. PROBE is useful in moving PP routines to CM when they are called (.r' I \"--....-" 98 01/17/86 frequently enough, thus improving system performance. 3.7 CONSOLE WATCHING Many times all the various tools are not as useful as just watching the system console for signs of thrashing and/or particular user abuse. The following items are worth watching for: 1) Users running batch jobs in time-sharing mode. 2) Batch jobs that are being rolled in but not getting the CPU before they are rolled out again. 3) Jobs that have excessive resource requests over extended periods. 4) Maintenance jobs running at too high a priority and/or too many of them running. One. job (CT7) is probably enough. Too many maintenance jobs cause a forced rollout every time a time-sharing job is brought in. r _____ l) o 5) Permanent file dumping and loading during the prime shift will slow down or stop any PF requests by your users. 6) NOS/VE running in a dual 800 can have a default priority that allows NOS/VE to take the CPU away from NOS. . ;! ...... j" 99 01/17/86 (~ 4.0 PERMANENT/TEMP FILE ALLOCATION We have found that allowing the temporary and permanent files to be allocated on every device seem to be the best strategy to spread the load onto as many units as possible. C) 100 01/17/86 In many sites the Engineering Data Library (EDL) runs with ICEM DON and can contribute to excessive resource use. The following EDL file (IMF2STF/UN=IMF) should have the following values for best performance: 3 NUMBER OF USER PROCESSES TO CHECK FOR EACH MTR LOOP 2 SEMI-IDLE RECALL TIME (MILLISECONDS) 1 ACTIVE RECALL TIME (MILLISECONDS) 1 K-DISPLAY REFRESH CYCLE 50 MAX NUMBER OF TIMES IDLE BEFORE SCP SWAP-OUT 30 MAX NUMBER OF CONNECTED USERS 10 MAX NUMBER OF OPEN DATA-BASES 170 MAX NUMBER OF ATTACHED FILES 3 NUMBER OF ALLOCATED USER STACKS 5 NUMBER OF INPUT BUFFERS 1 NUMBER OF INPUT QUEUE ENTRIES 3 NUMBER OF I/O BUFFERS o NUMBER OF TRANSACTION FILES ON ECS. 1 NUMBER OF LONG WAKE-UP WAITS ALLOWED AT STACK 2 NUMBER OF SHORT WAKE-UP WAITS ALLOWED AT STACK 6000 LONG WAKE-UP WAIT SWAP-OUT DELAY 4000 SHORT WAKE-UP WAIT SWAP-OUT DELAY 30 PARCEL STACK PREEMPTION DELAY 30 SINGLE READ STACK PREEMPTION DELAY o TRACE The file DEFSTF/UN=IMF (installation file for IMF)·should be used as a model. The default values which have been changed above are: ACTIVE RECALL TIME - 30 TRACE = 1 Also, journal logging may be turned off for the EDL database. This will save considerable overhead. However, if the system crashes with the database open, the database file may have to be reloaded from the last permanent file backup, instead of being recovered to the point of failure. To turn off journal logging, log into the account where the EDL database file E120DDB resides,. and type the following commands: GET,CHLOG21/UN=IMF CHLOG21,OFF,E120DDB,E120LOG. o - - - ---- -_ .... _--- /---.... \. C) 101 01/17/86 6.0 CONCLUSION Due to the many ways ICEM DDN is used, and considering the many other applications that are run on 800s, the tuning recommendations mayor may not be applicable. Please send any additions or deletions to the CIM Hotline. CIM Hotline Numbers: o (U.S.) 800-227-9999 (Minnesota and International) 612-639-4040 102 01/17/86 C) 7.0 TUNING GUIDE APPENDIX The following procedure and program will count the times each overlay is called and the total number of overlays called by processing the CT file which is output from a ICEM DDN run with the T option on: o .PROC,SORTCT. PACK·,CT, TAPE2. FILE,TAPE2,BT=C,RT=U. FTN5,I=SORTC,B=LGO,L=L,OPT=2. LGO. NOTE./ RESULTS ON FILE LIST • •DATA,SORTC. PROGRAM SORTCT(INPUT,OUTPUT,TAPE2,LIST,TAPE1=LIST) INTEGER IBUF,INUM(512) REWIND 1 REWIND 2 ITOTAL = 0 5 READ(2,END=15)IBUF IF(IBUF .GT. 512)GO TO 5 IF(IBUF .LT. O)GO TO 5 lNUM(IBUF) = lNUM(IBUF)+l ITOTAL = ITOTAL+l GO TO 5 C 15 DONE READING CT. WRITE(1,3000) DO 30 J=1,512 K .. 0 20 30 9000 1000 2000 3000 LASTBG - 0 DO 20 1-1,512 IF (INUM(I) .GT. LASTBG) THEN LASTBG - lNUM(I) K= I ENDIF CONTINUE IF(LASTBG .EQ. O)GO TO 9000 WRITE(1,1000) K,INUM(K) lNUM(K) -= 0 CONTINUE WRITE(1,2000) ITOTAL FORMAT (' CL - ',03,3X,I10) FORMAT (' SUM = ',110) FORMAT ('1', 'OVERLAY NUMBER',' END COUNT') o ---------------- ------------- 103 01/17/86 o APPENDIX D: REPLACEMENT PAGES FOR ICEM DDN Vl.6 MANUAL SECTIONS The remaining pages of this document consists of replacement pages for the ICBM DDN V1.6 Reference Manuals. Reference information for ICEK DDN Vl.6 is organized into eleven separate manuals. The replacement pages are grouped respectively under each of the separate manuals. MANUAL 0 0 PUBLICATION NUMBER MANUAL REVISION SRB CHANGE PAGES? ICEM Design Drafting: Introduction and System Controls 60457130 rev K yes ICBM Design Drafting: Data Management 60461410 rev D no ICBM Design Drafting: Basic Construction 60461420 rev C no ICBM Advanced Design 60461430 rev C yes ICEM Design Drafting: Drafting Functions 60461440 rev C yes ICEK Numerical Control 60461450 rev C yes ICBM Design Drafting GRAPL Programming Language Reference Manual 60461460 rev B no ICEM GPL 60462520 rev B yes ICBM DDN Instant 60457140 rev G no ICBM DDN User's Guide 60456940 rev F no ICBM DDN System Programmers Reference Manual 60458560 rev C no 1.8 Resel"'ed for Future Use (J 1.8 Reserved for Future Use 1.9 Color Display You can use the color display mode on any terminal, color or monochromatic. However, the colors appear only on the color terminals. When you are working on a color terminal, you must do a host repaint to view your changes. A host repaint uses the R key, as opposed to a local repaint, which uses the PAGE key. The modal menu is as follows: COLOR DISPLAY '.COLOR DISPLAY MODE 2.COLOR ENVIRONMENT The following is information about the use of color: o • Group and change color display mode require host repaints to change the color. • Groups (rectangular and circular arrays, balloons, and surface texture symbols) return to their base entity color after the group is deleted. • The main header has a C = 0 to 15. • The values entered for the color table use ICEM DDN's modal for the number of decimal places. • To see your current color display mode, enter 1.12 DISPLAY MODAL STATeS. The following sections describe the choices in this menu. 1.9.1 Color Display Mode With this modal, you can assign colors to entities, pens, and levels and perform color management functions. COlOR DISPLAY MODE 1.COLOR BY ENTITY TYPE 2.COLOR BY PEN NUMBER 3.COLOR BY LEVEL NUMBER •. COLOR BY ENTITY COLOR 5.CURRENTCOLOR NUMBER 6.MODIFY PEN NUMBER COLOR 7.MDDIFY LEVEL NUMBER COLOR 8.COLOR SPECTRUM DISPLAY 9.MODIFY ENTITY COLOR 10. TEMPORARY ENTITY COLOR The foIIowing sections describe the choices in this menu. o ._ _ _ ._ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ....__ .. _•.. _,..-~-I-_--..a_I:' .. -.P_'l.'-'7_ _ _ __ 1.9.1.1 Color by Entit,. Type 1.9.1.1 Color by Entity Type With this modal, entities are displayed by type. The color cannot be changed unless you change the color table. This is the default color display mode if you enter the system with a new part or you call up an old part that has this display mode saved. Whether the color assignment was assigned by entity type or not (refer to table 3-1), the system changes the color assignment to entity type and displays: COLOR BY ENTITY TYPE ON You return to 1.9.1 COLOR DISPLAY MODE. You must do a host repaint to view the color change in old entities. The newly created entities appear in the correct color. Table 3·1. DeCault Color Numbers by Entity Type Color Number Entity Type o Points 1 Line, are, conic, two-dimensional spline 2 Groups and arrays 3 Label and note 4 Linear, angular, diameter, and circular dimensions 5 Point to point, lathe, and grid 6 Three-dimensional spline, tabulated cylinder, and hexahedron 7 Section lining 8 Point set 9 Balloon, surface texture symbols, and composite curves 10 Template, vector, and data graphs 11 String 12 Tool 13 Surfaces and plane 14 True position and centerline 15 String ... _. ___ .______~.18_ ~~!~_~~~raftj~g Inu.oduction and System Controls for NOS Revision K · o . Menll 2: BlanklUnblank 4 Using Menu 2 This menu controls blanking of current parts. Blanking leaves an entity in a current part but does not display it. Unblanking makes it visible again. 1.10 BLANKIUNBLANK VIEW SELECT is used exclusively with this menu. Refer to Using 1.10 BLANKIUNBLANK VIEW SELECT for more information. The menu for this section is: BLANK/UNBLANK 1.BLANK-SELECT 2• -LEVEL RANGE 3. -ALL OF A TYPE 4. -ALL 5.UNBLANK-SELECT 6. -LEVEL RANGE 7. -ALL OF A TYPE 8. -ALL o The BlanklUnblank menu offers these features: Menu Title Description 2.1 BLANK-SELECT In a current part, blanks selected entities. 2.2 BLANK-LEVEL RANGE In a current part, blanks entities on selected levels. 2.3 BLANK-ALL OF A TYPE In a current part, blanks all entities of the selected type(s). 2.4 BLANK-ALL In a current part, blanks all entities. 2.5 UNBLANK-SELECT In a 2.6 UNBLANK-LEVEL RANGE In a current part, unblanks entities on selected levels. 2.7 UNBLANK-ALL OF A TYPE In a current part, unblanks all currently blanked entities of the selected type(s). 2.6 UNBLANK-ALL In a current part, unblanks all entities. curre~t part, unblanks selected entities. o _ _ _ _ _ _ _ _ _--=::Revision K Menu 2: BlanklUnblank .·1 Using 1.10 Blan~nblank Vie\\' SelE'ct Using 1.10 BlankfUnblank View Select Through the use of 1.10 BLANKIUNBLANK VIEW SELECT, you have the option of displaying or not displaying entities in specified views. This function is called selective view blanklunblank. It is independent of the blanklunblank function in that an entity can be blanked but not necessarily selectively blanked, and vice versa. For example, suppose you select a view in which an entity is to be selectively blanked. That entity is selectively blanked in that specified view and is not displayed in that view; however, the entity is still displayed in all other views, and is still unblanked. Changing the 1.10 BLANKIUNBLANK VIEW SELECT modal to ALL VIEWS and blanking that same entity causes it to be both selectively blanked and unblanked, and therefore not displayed in any view. Unblanking the entity causes it to be only selectively blanked again, and displayed in all views except the view you originally specified. If the modal is turned on, the system displays the following when you choose a submenu from 2 BLANKIUNBLANK: VIEW SELECTION , . RANGE 2.VIEW NUMBER Enter: 1 To select a range of views. FROM VIEW • TO VIEW • Enter the range of views (1. to 420) to be selectively blanked. Enter] or [ to return to the VIEW SELECTION prompt. If the sequence number of a group lies within this range, the subentities within this group will be blanked, even though the sequence numbers of the subentities do not lie within this range. 2 To select an individual view. VIEW NUIEER • Enter the individual view number. Enter [ or ] to return to the VIEW SELECTION prompt. You continue to the blanklunblank choice you selected. Selective view blanking is a cumulative function. If an entity is selectively blanked in two different views in separate operations, that entity is selectively blanked in both views. To reduce the number of views in which an entity is selectively blanked, use a aelective unblank function. An entity may be selectively blanked or unblanked in views 1 through 420. An unblank with the blanklunblank view select modal set to all displayed views does not unblank views that have been selectively blanked. These views must be selectively unblanked to be redisplayed. Hexahedrons cannot be selected with the blanklunblank or selective view blanklunblank functions. Dimensions, notes, centerlines, and feature frame symbols may be selected, ,but are selectively blanked only if the view number entered corresponds with the entity's view of definition. 4·2 ICEM Deaign/Drafting Introduction and System Controls for NOS Reviaion K REPLACEMENT PAGES ----------------- o MANUAL TITLE: ICEM Advanced Design PUBLICATION NUMBER: REVISION LEVEL: 60461430 C INSTRUCTIONS: To update this manual, for which the previous revision was C, make the following changes: ;----.... U Remove: Insert: 3-21,22 3-21,22 3-27,28 3-27,28 3-39,40 3-39,40 4-25,26 4-25,26 5-3,4 5-3,4 o - - - - - - - - _ ••.........._-._... _..... _........ - .... _ ..- .._-_. - - - c' 15.2.5 Composite Curve o 15.2.5 Composite Curve With this choice, you can create a composite curve from a set of contiguous curves. The curves of the composite curve must be selected end to end in sequential order. You cannot refer to the subcurves of a composite curve individually, but only as the whole composite curve. The allowable entities in composite curves are lines, arcs, conics, two-dimensional splines, three-dimensional splines, and Bezier curves. Composite curves have these characteristics: • Composite curves are single entities. • Composite curves are displayable entities and can be assigned display attributes, such as level. • A composite curve cannot be a member of another composite curve. • The number of allowable entities incorporated in a composite curve ranges from a minimum of 2 to a maximum of 100. • Composite curves are selectable entities but the individual entities incorporated in them cannot be selected. • Composite curves can be deleted without deleting the individual entities incorporated in them (refer to 3 DELETE in the ICEM Design/Drafting Introduction and System Controls manua}). When the composite curve is deleted, the individual entities retain the display attributes of the composite curve. The original display attributes of the individual entities are lost. • Composite curves behave as single entities when these operations are applied to them: TRANSLATE, ROTATE, MIRROR, SCALE, DUPLICATE, or any combination of these operations. o When you begin using the Composite Curve operation, the system displays: INDICATE ENTITY Use the graphics cursor to screen select the curves to be selected. If you want to use another method of selection, enter CTRL-E to receive the following menu: Use the entity selection procedure to select the contiguous curves that are to form the composite curve. Selected curves must be connected from end to end. You may select a maximum of 100 curves. After you select the curves and enter ], the system defines the composite curve and displays! ENTITY SELECTION 1.SCREEN SELECT CO~POSITE CURVE WITH XXX SUBCURVES CREATED, o You are then returned to the Screen Select Mode with the composite curve operation, rnen~ to continue 16.2.6 Vec:t.or If' you h~ve ended the curve selection procedure and fewer than two curves have been lpecified, the system displays: COMPOSITE CURVE NOT DEFINED. AT LEAST TWO CURVES REQUIRED. If the selected curves are not contiguous, the system displays: COMPOSITE CURVE NOT DEFINED. CURVES ARE t«lT CONTIGUOUS IN THE ORDER OF SELECTION. If the selected curves are members of groups, the system displays: CURVES CANNOT BE IN GROUPS If you selected fewer than two curves or the selected curves were not contiguous, you are returned to the Entity Selection menu to reselect the curves. You are not allowed to select more than 100 curves for incorporation in a composite curve. If you select more than 100 curves, the system displays: MAXIMUM OF 100 ENTITIES HAS BEEN SELECTED. 15.2.6 Vector With this choice, you can create new vectors or modify existing vectors. A vector is a lingle line segment that has magnitude and direction. Its length represents its magnitude. The direction of a vector is from its tail to its head, which has barbs on it. Vectors are always dermed in model coordinate space. The following menu is described in this section: VECTOR 1.SCREEN POSITION 2.KEY-IN 3.2 POINTS 4.SURFACE UNIT NORMAL 5. SCALAR TIlES VECT~ 6.CROSS 2 VECTORS 7.NORMALIZE VECTOR 8.LENGTH AT GIVEN ANGLE 9.INTERSECTION OF 2 PLANES 10.SUM OR DIFF OF 2 VECTORS 11.PT AT ANGLE TO LlNE/VECTOR 12.MOOIFY/REPLACE l3.REVERSE SURFACE NORMAL The choices in this menu are described next. Reviaion C 15.2.6.12 ModifylRepJace INDICATE 2-D CURVE U Be the graphics cursor to select an existing line or vector to use as the base for the angular measurement. 1.ANGLE • n.nnnn 2.LENGTH • n.nnnn Enter new values for the angle and length of the vector. NOTE Vectors defined by these menus cannot be modified: 2 Points (15.2.6.3), Surface Unit Normal (15.2.6.4), Cross 2 Vectors (15.2.6.6), Normalize Vectors (15.2.6.7), Intersection of 2 Planes (15.2.6.9), Sum or Diff of 2 Vectors (15.2.6.10), and Reverse Surface Normal (15.2.6.13). If vectors defined by these menus are selected for modification, control will be returned to the Select Entry Mode menu. o o Revilion C Menu 15.2: 3·D Curvel 3·27 -_.................. _ _._._._._--_._._..._._ _ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ... ... 15.2.6.13 Revene Surface Normal 15.2.6.13 Reverse Surface Normal With this choice, you can create and display a unit surface normal vector. You can also reverse the normal direction of a specific surface. This is useful because some Numerical Control manufacturing operations require that the normal vectors point away from the material side of a surface. You can create a surface without regard to its normals and then confirm or change them later. SURF ACE tOtMAL fII)OE 1.DISPLAY VECTOR 2.REVERSE tOtMAL Enter: 1 To define and display a unit surface normal vector on a selected surface. INDICATE SURFACE Use the graphics cursor to select a surface. Selecting the surface with the graphics cursor on the surface causes the system to define the unit surface normal vector at the graphics cursor location. Selecting the surface with the graphics cursor off the surface causes the system to define the vector at the surface parameters u,v (0.5,0.5). 2 To reverse the normal direction of a surface. REVERSE trJRMAL II>DE 1.INDICATE SURFACE 2 . REV. LAST VECTOR Enter: 1 To use the graphics cursor to indicate the surface for which the normal direction is to be reversed. The system indicates this surface by displaying a unit normal on the surface at u,v-(O.5,O.5). Previously created normal vectors are unchanged. 2 The surface whose normal direction is to be reversed is the one which is associated with the last normal vector created with 1. DISPLAY VECTOR under the SURFACE NORMAL MODE prompt. This vector is delected and replaced by a new reversed vector at the same location. C,I 3·28 JCEM Advanced neaign for NOS ReviaioD C 15.2.7.1.4 Conversion o 15.2.7.1.4 Conversion With this choice, you can approximate curves (lines, arcs, conics, two-dimensional splines, three-dimensional splines, machining curves, point set, composite curve, Bezier curves) by using a Bezier curve. The approximation is an interpolation if the curve is a line. INDICATE CURVE Select a curve. CURVE EXTENT 1.ENTIRE CURVE 2.PART OF CURVE Enter: 1 To approximate the entire curve. 2 To approximate only part of the curve. If you entered 2.PART OF CURVE, the system displays: START PARAMETER 1.SCREEN POSITION 2.K.EY-IN 3.EXISTING POINT 4.SElECT CURVE END Enter: 1 To indicate a position near the desired point at which the new curve starts. If the position does not lie on the curve, the shortest two-dimensional normal is dropped from the position to the curve. 2 To enter the parameter value to define the start point. The system displays the parameter values of the start and endpoints of the curve. You can enter a-value between those two values to define the point within the curve, or beyond them to define the point on the extended curve. o 3 To select an existing point near the desired point at which the new curve starts. If the point does not lie on the curve. the shortest three-dimensional normal is dropped from the point to tile curve. 4 To indicate one end of an existing curve. Then you are prompted for the END PARAMETER having the same choices. After entering 1. ENTIRE CURVE or after prompting END PARAMETER for 2. PART OF CURVE, the system displays: ORDER • n o A default order is given that varies by the curve type. You can accept the value n or enter an appropriate value. If the .elected curve is a line, the order is always 2. For other types of curves the minimum order is 4. If the existing curve is an ellipse and the opening angle is larger than 180, two curves are generated in order to more closely match the ellipse. Reviaion C Menu 16.2: 3·0 Curves 3-39 16.2.7.1.6 Dupl&~clEs1end 15.2.7~1.5 Dupl&TrunclExtend \'-- ..... With this choice, you can define a Bezier curve that is identical to part of the Bezier curve (segment) or that extends a Bezier curve (extension). INDICATE BEZIER CURVE Select a Bezier curve. START PARAMETER Enter: 1.SCREEN POSITION 2.KEY-IN 3.EXISTING POINT 4.SELECT CURVE END 1 To indicate a position near the desired point at which the new curve starts. If the position does not lie on the curve, the shortest two-dimensional nonnal is dropped from the position to the curve. 2 To enter the parameter value within the range from -1 to 2 to indicate where the starting point is to be. The parameter values o to 1 defme points within the existing curve. The parameter values from -1 to 0, or from 1 to 2, define points on the extended curve. 3 To select an existing point near the desired point at which the new curve starts. If the point does not lie on the curve, the shortest three-dimensional normal is dropped from the point to the curve. 4 To indicate one end of an existing .curve. Then you are prompted for the END PARAMETER having the same choices. 15.2.7.2 Modification With this choice, you can modify a Bezier curve. The menu described in this section is: IIlOIFICATION 1.POLYGON 2.CONSTRAINTS 3. DEFORMATION 4.DEGREE 5.SEGMENT 6.PARAMETER The choices in this menu are described next. Revision C 3-40 ICEM Advanced Daign for NOS -------- ------------------------------------ - ----------------------- CI 15.3.9 Sphere o 15.3.9 Sphere With this choice, you can create a sphere. This surface is 'the set of points located at a specified distance from a center point. 15.1.3 SURFACE PATHS is used to construct the sphere with the desired number of surface paths. CENTER POINT 1.SCREEN POSITION 2.KEY-IN 3.EXISTING POINT Indicate the center point of the sphere. Enter: 1 To use the graphics cursor to indicate a position. 2 To enter the xt-, yt-, and zt-coordinates. 3 To use the graphics cursor to select an existing point. After you select a center point for the sphere, the system displays: FULL EQUATOR? Enter: Y To construct the sphere with a full 180° equator. The equator rotates counter-clockwise from the positive x-axis of the work olane around the normal vector of the work plane. Furthermore. the equator angles can only range between 0 and 180 degrees. o N To construct the sphere with' other than a 1800 equator. If you enter N, the system displays: 1.STARTING ANGLE • n.nnnn Enter the starting angle and the ending angle of 2.ENDING ANGlE • n.nnnn the equator. Default angles are 00 and 180°. After you define the equator, the Iystem displays: FULL CIRCUMFERENCE? Enter: Y To construct the sphere with a full 360° circumference. The circumference rotates about the horizontal axis in the view of definition and is measured from the top out of the screen. N To construct the Iphere with other than a 3600 circumference. End minus start angle must be less than or equal to 360 degrees. If you enter N, the system displays: o 1.STARTING ANGLE • n.nnnn 2.ENDING ANGLE • n.nnnn Enter the starting angle and the ending angle of -the circumference. Default angles are 0° and 360°. After you defme the circumference, the system displays: 1.RADIUS • n.nnnn Enter the sphere radius. Default is 6.35 mm (0.25 in). Reviaion C - - - - - - - - - - - - - - - - - - - - - - - - --_ .. __._--- Menu 15.3: Surfaces "·25 15.3.10 CJliDder The sphere in figure 4-5 bas an equator of 300 to 170° and a circumference of 00 to 270°. CIRCUMFERENCE EQUATOR o SURFACE PATHS 1. NUMBER OF U 2. NUMBER OF V 3. POINTS PER U 4. POINTS PER V PATHS=21 PATHS=7 PATH =7 PATH =21 170 VIEW OF DEFINITION RIGHT SIDE OF VIEW OF DEFINITION Figure 4·5. Sphere 15.3.10 Cylinder With this choice, you can create a right circular cylinder. This surface is the set of points at a specified distance from a center axis line. A cylinder may be generated using one· of two methods. With the rll'st method, you specify an axis, radius, and start/end angles. With the second method, you specify an arc and a height. The system generates an axis normal to the arc and through its center. The cylinder is dermed using the radius and angles describing the arc. 15.1.3 SURFACE PATHS can be used to construct the cylinder with the desired number of surface paths. CYLINDER DEFINITION 1.AXIS 2.EXISTING ARC Enter: 1 To specify an axis, radius, and starting and ending angles. Continue to AXIS. 2 To specify an arc and a height. Continue to EXISTING ARC. The choices in this menu are described next. Axis If you select 1.AXIS from the Cylinder Dermition menu, the system displays: AXIS FORM 1.EXISTING LINE 2.EXISTING POINTS .·18 ICEM Advanced Dnicn (or NOS Reviaion C ,- .. ~ 15.4.1 Hexahedron o 15.4.1 Hexahedron With this choice you can create a hexahedron, which is a solid bounded by orthogonal planes. Indicate the center point of the hexahedron. CENTER POINT 1.SCREEN POSITION 2.KEY-IN 3.EXISTING POINT Enter: 1 To use the graphics cursor to indicate a position. 2 To enter the xt-, yt-, and zt-coordinates. 3 To use the graphics cursor to select an existing point. After you select a center point for the hexahedron, the system displays: 1.0XT • n.nnnn 2.0YT • n.nnnn 3.0ZT • n.nnnn Enter either the distances along the x-, y-, and z-axes from the center point to the hexahedron faces, or the normal distances from the center point to the orthogonal planes bounding the hexahedron. o o Reviaion C Menu 15.4: Solids 5-3 16.4.2 Spheroid 15.4.2 Spheroid With this choice, you can create a solid sphere. Indicate the center point of the spheroid. CENTER POINT 1.SCREEN POSITION 2.KEY-IN 3.EXISTING POINT Enter: 1 To use the graphics cursor to indicate a position. 2 To enter the xt-, yt-, and zt-coordinates. 3 To use the graphics cursor to select an existing point. After you select a center point for the spheroid, the system displays: FULL EQUATOR? Enter: Y To construct the spheroid with a full 180° equator. The equator rotates about the vertical axis in the view of definition and is measured from the right to the left. N To construct the spheroid with other than a 180° ~uator. If you enter N, the system displays: 1.STARTING ANGLE • n.nnnn 2.ENDING ANGLE • n.nnnn Enter the starting angle and the ending angle of the equator. Default angles are 0° and 180°. After you derme the equator, the system displays: fULL CIRCUMFERENCE? Enter: Y To construct the spheroid· with a full 360° circumference. The circumference rotates about the horizontal axis in the view of dermition and is measured from the top out of the screen. N To construct the spheroid with other than a 360° circumference. If you enter N, the system displays: 1.STARTING ANGLE • n.nnnn 2.ENDING ANGLE • n.nnnn Enter the starting angle and the ending angle of the circumference. Default angles are 00 an~ 360°. End mi~us start an~les must be less than or equal to 360 degrees. After you define the circumference, the system displays: 1.RADIUS • n.nnnn I-t leEK Advanced Desicn for NOS Enter the radius of the spheroid.' Default is 6.35 mm (0.25 in). ReviaiOD C REPLACEMENT PAGES o MANUAL TITLE: ICEM Design/Drafting Drafting Functions PUBLICATION NUMBER: REVISION LEVEL: 60461440 C INSTRUCTIONS: To update this manual, for which the previous revision was C, make the following changes: o o Remove: Insert: 2-21,22,23,24 2-21,22,23,24 18.3 2·D Section Analysis o Select the type of analysis to be performed. SELECT ANALYSIS 1. PERIMETER 2.AREA 3.CENTER OF GRAVITY 4.AXIAL MOMENTS OF AREA S.AXIAL MOMENTS OF INERTIA 6.PRINCIPAL MOMENTS OF INERTIA 7.PRINCIPAL AXES ANGLES a.PRODUCTS OF INERTIA 9.AXIAL RADII OF GYRATION 10.POLAR MOMENT OF INERTIA 11.POLAR RADIUS OF GYRATION Enter: 1 To determine the perimeter of the figure. 2 To determine the area of the figure. 3 To determine the center of gravity of the figure. 4 To determine the axial moments of the area of the figure with respect to each coordinate axis. 5 To determine the axial moments of inertia (second moments of area) of the figure with respect to each coordinate axis. . 6 To determine the principal moments of inertia of the figure with respect to the principal axes. 7 To determine the angles between the coordinate axes and the principal axes (in degrees). o 8 To determine the products of inertia of the figure. 9 To determine the axial radii of gyration of the rlgUl'e with respect to each coordinate axis. 10 To determine the polar moment of inertia with respect to the local origin of the figure. 11 To determine the polar radius of gyration of the figure. The origin used in response to selections 3 through 11 is the origin indicated in response to the LOCAL ORIGIN FOR ANALYSIS prompt. The coordinate axes used in response to selections 4. 5, 6, and 9 are those that pass through this origin and are parallel to the bottom and left edges of the screen. o Reviaion C Menu 18: Analysis 2·21 .. - ' . _ - " ' - - ... _---------- 18.4 3·D Analysis 18.4 3·D Analysis With this choice, you can calculate specific analytical properties of certain three-dimensional figures. These figures should be two-dimensional, closed shapes that will be projected to a depth, rotated about the XT-axis. rotated about the YT-axis, or rotated about a given line. If the fi~ures are to be rotated about an axis, they may not cross· the axis of rotation. Shapes in three-dimensional space may also b~ used, but only their nrojection onto the XT,YT plane will be considered. The following approximate analyses can be performed: • Surface" area • Volume • Weight and/or weight per unit length • Firat moment and center of mass • Moment ofmertia • Radius of IYJ"&tion • Spherical moment • Spherical radius of gyration or inertia The system displays the following menu choices: 3-D ANALYSIS 1.PERFORM ANALYSIS 2.DISPLAY ACCUMULATED RESULTS Enter: 1 To perform analysis on a projected or rotated object. 2 To display the accumulated results of three-dimensional analysis on two or more distinct objects. Revision C 18.4.1 Perform Analysis o _ 18.4.1 Perform Analysis With this choice, you can specify the type of three-dimensional figures to be analyzed. SELECT ANALYSIS 1.PROJECTED 2.ROTATED ABOUT 3.ROTATED ABOUT •. ROTATED ABOUT TYPE THE Xl-AXIS THE YT-AXIS A LINE Enter: 1 To select projected two-dimensional entities. Enter the bottom and top zt values of the projected figure to be analyzed. The default values are: 1.lT BOTTOM • n.nnnn 2.lT lOP • n.nnnn l.ZT BOTrOM = -1.0 in (-25.4 mm) 2.ZT TOP = 1.0 in ( 25.4 mm) Enter: To return to the Select Analysis ~ menu. o To accept the default -/alues and continue to the DENSITY prompt. 2 To select a two-dimensional figure to be rotated 3600 about the xt-axis. 3 To select a two-dimensional figure to be rotated 3600 about the yt-axis. 4 To select a two-dimensional figure to· be rotated 3600 about a line in the XT, YT plane. Use the graphics cursor to select an existing line as the axis of rotation for the two-dimensional figure. The line should be coplanar with the figure and both should be in the XT, YT plane. If they are not, the system projects them onto the XT,YT plane and uses the projections for analysis. INDICATE LINE Enter: [ To return to the Select Analysis Type menu. ] To return to 18.4 3-D ANALYSIS. o MeDU 18: Analyais 1·13 ReviaioD C - - - - - - - - - - - - _ .__ .. --_._._ .. _.._--.... _... - - _.. -.----.. -.-- ._-- .~-~.-.------~---- -----... .....- .. -._-_.. _.- - ...--. ----------.- -- -. 18.4.1 Perform Analysis For all types of figures, the system next displays: 1.DENSITY • n.n Enter the de1?-sity of the figure in grams per .cubic millimeter (pounds per cubic inch). The default value is 1.0. Enter: [ To return to the Select Analysis Type menu. ) To accept the deCault density. Now .elect the entity you want to analyze. INDICATE 2-D CURVE Use the graphics cursor to screen select the edges of the figure. A maximum of 250 curves can be selected. The generating figure must be closed. 11' you want to use another method oC .election, enter E or CTRL-E to receive the following menu: ENTITY SELECTION 1.SCREEN SELECT 2.OlAIN a.REGION IN UBe the Entity Selection menu to identif'y the edges. For more information, reCer to the ICEM Design/Drafting Introduction and Systems Controls manual. Enter: [ To return to the DENSITY prompt. ] To return to the Select Analysis Type menu if' you made no' .elections. If you made the selections, entering) sends you to the INDICATE 2·D CURVE prompt. In the case oC a rotated figure, if the edges do not Corm a closed curve, perpendiculars Crom the ends of the curve are dropped onto the axis of rotation, thereby closing the curve. c c 2·24 ICEM Design/Drafting Drafting Functions for NOS Revision C REPLACEMENT PAGES o MANUAL TITLE: ICEM Numerical Control PUBLICATION NUMBER: REVISION LEVEL: 60461450 C INSTRUCTIONS: To update this manual, for which the previous revision was C, make the following changes: Remove: o Insert: 6-23,24 6-23,24 7-17,18 7-17,18 14-3,4 14-3,4 17-1,2,3,4,5,6,7,8,9,10 17-1,2,5,6,7,8,8.1,9,10 19-35,36,37,38 19-35,36,36.1,37,37.1,38 19-45,46 19-45,46 20-5,6,7,8,9 ·0 Retraction Between Points CPoint·to-Point Only) C) GPG Statement The SRTRCT statement sets tool motion from point to point. Statement Format: SRTRCT / PROMPT] NONE CLEAR RETRCT I o Parameter Description PROMPT Prompts for the options at generation time. NONE Moves the tool directly with no retraction between points. CLEAR Moves the tool from point to point using the clearance distance from the next point. If the next point is lower or equal to the next point, the retract distance is that of the current point plus the clearance distance. If the next point is higher, the retract distance is that of the next point plus the clearance distance. RETRCT Moves the tool to the retract plane for motion between points. o _... __ .. _-----_.• _- _ - - - .. - - - - - - - - - - _ _--_.- .......__ _._ .• .. .... .. - -- - ....__ .. ' .. - Spindle Spindle The spindle speed and direction is set using the following methods. Generate The prompts that appear at toolpath generation time are the. same as for the Modify Current Parameters menu except that you do not select the prompting option. Modify It you selected Spindle from the Modify Current Parameters menu, you can set the .pindle speed and direction. SPINDLE SPEED 1.SPINDL SPD 2.DIRECTION 50 CLW Enter [ to return to the Modify Current Parameters menu with no changes. Enter] to accept the values. Enter: 1 To set the spindle speed. 1.SPINDL SPD 50 Enter the spindle speed. Enter: ] To accept the value and return to the Spindle menu. [ To return to the Spindle menu with no changes. 2 To set the spindle direction. SPINDLE DIRECTION 1. CLOCKWISE 2. COUNTERCLOCKWISE .Enter: 1 To indicate clockwise direction. 2 To indicate counterclockwise direction. - ---- - - - - - - ......... --.,. ..... ,- ... ,.~-- -~--, "' __ • __ 1_~___ ~nc: ] To accept the value and return to the Spindle menu. [ To return to the Spindle menu with DO changes. N/C Command Editor c) Move Command (M) The M command aovel test froa one point in the, file to another point in the file. Delcription COtllDUlnd Move line lpl after lp2. M lp1 T lp2 " " M lp1,lp2 T lp3 Move line. lpl to lp2 after lp3. 11 M N III T lp2 Move nl line. beginning with the current line after line Ip2. 11 M lpl N n1 T lp2 Move nl linel beginning with line lpl after line lp2. HOT! The text of the lalt line aoved il the only line dilplayed. baaples: o Entry SYlte1l Action 11 M X T 100 Kove line X after line 100. 11 M G,G T G Move the linel between the nearest toolpath points of two .creen .electionl and inlert thea after the toolpath point of a third .creen-Ielected point. " Move liDeI 300 to 400 to the beginning of the file. M 300,400 TO" . 71 K H3 T L 7' M 22 HID T 200 Move 3 I1nel beginning with the current I1ne after the 1•• t I1ne. ", Move 10 l1n•• beginn1nl with 11ne 22 after line 200. o 11-38 leEM Numerical Control for NOS - - - - - - - - - - - - '-"--"-'---"'-'" '" .,-_._._._... _...._.. - Revision C NIC Command Editor Copying and transforming lines from another toolpath. Command Description ?? C lp1 (S.M) T lp3 Copy and transform ltne lp1 from the selected toolpath after lp3. 1? C lp1,lp2 (S,M) T lp3 Copy and transform lines lp1 to lp2 from the .elected toolpath after lp3. 1? C N n1 (S,M) T lp3 Copy and transform n1 lines beginning with the first line from the selected toolpath after lp3. ?? C lp1 N n1 (S.M) T lp3 Copy and transform n1 11nes beginning with line lp1 from the .elected toolpath after lp3. NOTE 1) The letter'S' must be included within the parentheses to indicate that the lines copted are from another toolpath. To choose the toolpath to copy from, follow the standard .election procedure for toolpath entities. 2) The letter 'M' must be included within the parentheses to ind;cate that a matrix copy operation is to be performed. 3) Line parameters C. X. y. Z. G. line+num. and 11ne-num cannot be used to .pecify the line range to copy . • ) The text of the la.t line copied is the only line displayed. You can add a repeat para~eter to the MATRIX COpy coNftand which will .'low you to copy and transform the .ame lines multiple times. The form of the repeat parameter is R r1 wnere r1 indicates the number of times the lines will be copted. Command Descript10n 1? C lp1 (M) T lp3 R r1 Copy and transform line lp1 after lp3. Repeat .r1 times. 11 C lp1.1p2 (S.M) T lp3 R r1 Copy and transform lines lpi to lp2 from the .elected toolpath after lp3. Repeat r1 times. 11 C N n1 Copy n1 lines beginning with the f1r.t line from the file fna""e after lp3. Repeat r1 t1 ..es. (fna~e.M) T lp3 R r1 Example: Entry System Action 1.1 C 100.200 (M) T 10 Copy and transform lines from 100 to 200 after line 10. 11 C A (FRED.M) T L Copy and transform all lines from file FRED after the last line. 11 C F N3 (S,M) T G Copy and transform 3 lines beginning with the first line after the nearest scr •• n selected goto point. 11 C 10.100 (M) T C R2 Copy and transform lines 10 to 100 after the current line. Repeat the operation twice. Revision C Menu 17.11: Display and Edit 19.37.1 NJC Command Editor o Matrix Copy Command (C) The C cOMmand can .lso copy .nd tr.nsform lines from one place to .nother, either within the edit.d toolp.th, or from .nother fil. or toolpath. Copying .nd tr.nsforming ltnes within the edit.d toolpath. Comm.nd D.scription 11 C lp1 (M) T lp3 Copy line .nd tr.nsform lp1 .ft.r lp3. 11 C lp1,lp2 (M) T lp3 Copy and tr.nsforll lines lp1 to tp2 aft.r lp3. 11 C N n1 (M) T lp3 Copy .nd tr.nsform n1 lin.s beginning with the current line .fter lp3. 11 C Ip1 N n1 (M) T lp3 Copy .nd tr.nsform n1 lines beginning with line lp1 .ft.r lp3. NOTE 1) The letter 'M' lIust be included within the parentheses to indic.t. that a •• trix copy op.r.tion is to b. perform.d. 2) Line par.m.t.rs C, X, Y, Z. G, line.num, .nd line-num c.nnot be us.d to sp.cify the line rang. to copy. 3) The text of the last line copied in the only line di.play.d. Copying .nd tr.nsfor",ing lines from .nother fil •. 0 Command D.scription 11 C lp1 (fname.M) T lp3 Copy .nd tr.nsform line lp1 from file fn.m. aft.r lp3. '11 C lp1,lp2 (fn.m.,M) T tp3 Copy .nd tr.nsform lines lp1 to lp2 from fil. fname .fter lp3. 11 C N n1 (fn.m.,M) T lp3 Copy .nd transform n1 lines beginning with the first line from fil. fna ... after lp3. 11 C lp1 N n1 (fna".,M) T lp3 Copy .nd tr.nsform n1 ltnes b.ginning with line lp1 from fil. fname after 1p3. NOTE 1) The f ne na ...... st be included within the p.rentheses. 2) The letter 1M' lIust be includ.d within the par.nthes.s to indic.te that a aatrix copy op.r.tion i. to be perforMed. 3) Line p.r.... t.r. C, X. Y. Z, G, line.num, .nd line-null c.nnot be used to .p.cify the line r.nge to copy . • ) File na ... 's' c.nnot b. copied. line. frOll .nother to01p.th. See copying .nd tr.nsfor.ing 5) The text of the ' •• t line copi.d is the only line displ.yed. o 19.37 lCEM Numerical Control for NOS Reviaion C N/C Command Editor c\ Copying lines from another toolpath. Command Description 11 C lpi (S) T lp3 Copy line lp1 from the toolpath selected after lp3. 11 C 1pi. 1p2 (5) T 1p3 Copy lines lp1 to lp2 from the toolpath .elected after lp3. 11 C N n1 (S) T lp3 Copy n1 lines beginning with the first line from the toolpath .elected after lp3. 11 C lp1 N n1 (S) T lp3 Copy n1 lines beginning with line lp1 from the toolpath .elected after lp3. NOTE 1) The letter '5' must be included within the parentheses to indicate that the lines copied are from another toolpath. To choose the toolpath to copy from. follow the standard selection procedure for toolpath entities. 2) Line parameters C. X. Y. Z. G. line+num. and line-num cannot be used to .pecify the line range to copy (lp1 or lp2). 3) The text of the last line copied 15 the only 'ine displayed. You can add a repeat parameter to the COpy command which will allow you to copy the same lines multiple times. The form of the repeat parameter is R r1 where ri indicates the number of times the lines will be copied. Command Description 11 C 1p1 T 1p3 R r1 Copy line lp1 after lp3. 11 C lp1.1p2 (S) T lp3 R ri Copy lines lpi to lp2 from the toolpath .elected after lp3. Repaat r1 times. 11 C N n1 (fname) T lp3 R ri Copy n1 lines beginning with the first line from the file fname af.ter lp3. Repeat ri times. Repeat ri times. Example: Entry System Action 11 C A (FRED) T L Copy all lines from file FRED after the last '1ne. 11 C 100.200 (S) T 0 Copy lines 100 to 200 from the toolpath that is selected to the beginning. 11 C N3 T 100 Copy 3 lines beginning with the current line after 'ine 100. 11 C F.C T C R5 Copy the '1nes from the first line to the current line after the current line. Repeat the operation five times. C,I Revision C Menu 17.11: Display and Edit 19. 36 .1 NIC Command Editor C\ Copy Command (C) The C command copies te~t from one place to another. either within the edited file. or from another file or toolpath. Copying lines within the edited file. Command Description 17 C 'pi T lp2 Copy line -lp1 after lp2. 17 C lp1.1p2 T lp3 Copy lines lp1 to lp2 after lp3. 17 C N n1 T 1p1 Copy n1 lines beginning with the current line after lp1. 77 C lpi N n1 T 1p2 Copy n1 lines beginning with line lp1 .fter lp2. NOTE The text of the last line copied is the only line displayed. Copying lines from another file. o Command Description 11 C lp1 (fname) T lp3 Copy line lp1 from file fname after lp3. 11 C lp1.1~2 (fname) T lp3 Copy lines lp1 to lp2 from file fname after lp3. 77 C N n1 (fname) T lp3 Copy n1 lines beginning with the first-line from file fname after lp3. 11 C lp1 N n1 (fname) T lp3 Copy n1 lines beginning with line lpi from ftle fname after lp3. NOTE 1) The file name is to be included within the parentheses. 2) Line parameters C. X. V. Z. G. line+num. and line-num cannot be used to specify the line range to copy. 3) File name '5' cannot be copied. another too' path . See copying lines from • ) File name 'M' cannot be copied. See matrix copy. 5) The text of the '.st line copied 1s the only line displayed. 19-38 ICEM Numerical Control for NOS Revision C N/C Command Editor Replace Command (R) The R command replaces one string of characters for another string of characters. Command Description 11 R /t 1/t2/ Replace t1 with t2 in the rust line found. The search for tl begins with the current line and ends when either t1 is found or the end-of-file was reached. 11 R lp /t1/t2/ Replace t1 with t2 in the rust line found. The search for tl begins at line Ip and ends when either t1 is found or the end-of-file was reached. If lp = A, then replace all occurrences of tl with t2. 11 R lp1, lp2/t 1/t2/ Replace all occurrences of t1 with t2 from line parameter lpl to Ip2. 11RNn1t1t2 Replace t1 with t2 in nl lines with the search with the current line. begin~ing Replace tl with t2 in -nl lines with the search for t1 beginning at line lp. NOTE All lines that contain the string in the range are displayed. Examples: Entry System Action 11 R/text1/text2/ Replace the occurrence of textl with text2 in the rust line f'ound beginning with the current line. 11 R2S/text1/text2/ Replace the occurrence of'textl with text2 in the rust line f'ound beginning with line number 25. ~ 11 RF ,G/text 1/text2/ Replace all occurrences of textl with text2 from the first line to the line of the nearest screen-selected toolpath point. 11 RA'text1'text2' Replace all occurrences of textl with text2. Replace in three lines the occurrence of textl with text2 starting at line 100. Revision C ----------------- - --- Menu 17.11: Display and Edit 19·35 -- -- ---------------- - - - - - - - Ci 17.9.2 Contouring o 17.9.2 Contouring You can use this menu to generate a lathe contouring N/C machining toolpath. The lathe contouring operation removes excess material left from a roughing operation, casting, or forging. The cutting passes are run parallel to the fmish part geometry. This operation may produce a finished part, or may leave small amounts of stock for other operations, such as grinding. The menu for this chapter is: CONTOURING 1.GENERATE TOOLPATH 2.MDDIFY GENERATION PARAMETERS 3.READ PARAMETERS FROM TOOLPATH 4.READ PARAMETERS FROM FILE S.WRITE PARAMETERS TO FILE The choices in this menu are described more fully in chapters 3, 5, and 7. o 1.GENERATE TOOLPATH Refer to the following section for a listing of the prompt sequence. Refer to chapter 3 for a general overview of the generation sequence. Refer to chapters 5 and 7 for specific operations. 2.MDOIFY GENERATION PARAMETERS Refer to the following section for a listing of the menu. Refer to chapter 3 for a general overview of the modify sequence. Refer to chapters 5 and 7 for specific operations. 3.READ PARAMETERS FROM TOOLPATH Refer to chapter 3 for a description of this sequence. 4.READ PARAMETERS FROM FILE Refer to chapter 3 for a description of this sequence. Refer to chapter 3 for a description of this sequence. . S.WRITE PARAMETERS TO FILE o 1'1.10 lCEM Numerical Control for NOS Revision C -----------------------------,--"'-'----- 17.9.1 Roughing The .y.t.. then ••k. you to defln. the .tep 11ze. IDter the 11z. of each cut in the flr.t .et of cut. ia aill1aet.r. (lacbe.). 1.n1ST STEP- The .y.t. . .It. JOu to defl.e • Itep .1z. for the re.t of the zone. US! LAST SUI rOI eST or ZOM!? Eater: Y To aae the firlt Itep 111e OD .11 lub.equent Itep. of the contour. • To deflDe another Itep 11ze for lublequaDt Itapl. 1. STU COUNT- IDtar the auaber of Itep. to ba .ade wlth the current Itap 11ze. 1.11!XT STIP - IDter the Itep .11a for aach cut la the Dest let of Itep' 1. 81111.. ter. (lnche.). Tha IYlt.. retuml to the DS! J.\ST Sl%! POI lEST or ZOH!? ,rapt UDtl1 you eDter t. The Iy.tn theD ••t. you if you vaDt to follow the .hape or DOt. 1. POLLOW SHAPE 2.oo5'T POLLOW IDter: 1 2 PRE-GENERATION INSERTS 1.ENTER STATEMENTS To Indlcate that the tool 1. to follow the Ihape of tbe eDtlre contour before llftina· '0it reache. Indlcate that the tool 11 to 11ft •• 100D •• the .cock dl.cance fro. the part. Enter: ~.NONE to use display and edit to insert .tatements. ~ to proceed with out inserts. At this point the system displays GENERATING TOOLPATH. If an error occurs during generation an error message is displayed. If no .rrors occur the system displays: CUU!NT COMPOSITE IS _e IIAK!! APPEND TOOLP ATH I.IAKE AND APP!ND TO CUleNT Q)MPOSITI 2.D!PIR! CUlR!HT COMPOS IT! 3.KAME, DO MOT APPEND 4.DO BOT IIAK!. DO HOT APP!ND ReVWOD C tou can DAae or append the toolpatb juat defined to the current coapo.lte toolpath. lafer to the teralaatloD .equence ia chapter 1. Menu 17.9: Lathe 17·9 Cl o o 17.9.1 Roughing C~T~ GEQt.ETRY FI~ Revision C - - _ . _ - - _...._ .. _ - - - - - - - '7-3. OAIVE LI~ Menu 17.9: Lathe 17-8.1 17.9.1 RoUfhing ENTER TOOL NAME: o TOOL PARAMETERS TOOL NAME: name TOOL TYPE: LATHE TURNING TOOL IMAGE': NON-ROTATING 1.TOOL NUM-1 2.NOSE RAO-0.0625 3.ANGLE 1 a45.000 4.ANGLE 2 -90.000 S.X GAGE LEN-O.OOOO 6.Z GAGE LEN-O.OOOO 7.0FFSET NO.a1 ACCEPT THIS TOOL? Enter the name of the tool to be used to generate the tool path. The tool ;s checked for correet type. If the tool type is incorrect or the tool does not exist you are prompted for another name. Refer to table 1-1 for a list of available tool types. If the tool is valid the system displays: Enter: Y to use this tool to create the toolpath. N or or [ to reject the tool and return to the enter tool nar,e prompt. SELECT BLANK INDICATt:: ENTITY Select the curve or curves forming the outside of the blank. INDICATE TOOLSIDE Use the graphics cursor to indicate the outside of the blank. can be along any entity selected. SELECT CONTOUR INDICATE ENTITY Aftor the blank material is is defined for the rough cut. define the outline of the part to be finished machined. INDICATE TOOLSIDE Use the graphics cursor to indicate on which side of the contour geometry that the material will be removed. o The system then asks you to define CheCk lines. Check lines 'are lines that intersect the contour geometry. The contour geometry will be intersected with the start check line and the end check line. When the toolpath is generated. it will follow the contour geometry from the intersection of the start check line to the intersection of the end check line. If only an end check line is desired, a start check line can be selected that does not intersect the contour geometry. Check lines should only intersect the contour geometry once. CHECK LINES? Enter :Y to define check lines. N to not define check lines and continue to the drive line prompt. o SELECT STARTING CHECK LINE INDICATE ENTITY Use the graphiCS cursor to select the line to be used for the starting check 1 ine. SELECT ENDING CHECK LINE INDICATE ENTITY Use the graphics cursor to select the line to be used for the ending check 1 ine. You are then prompted for a dr(ve line. A drive line is used to skip grooves and contours that are not wanted in a toolpath. When the drive line is further from the axis of rotation than the contour geometry. the toolpath will follow the drive line. Refer to figure 17-3 for an example drive line. DRIVE LINE? Enter: Y to select a drive line. N to not select a drive line and continue at the first step prompt. 17-8 ICEM Numerical Control for NOS Revision C The indication 17.9.1 Roughing Lathe rouch operatloD uae. the roulh feed rate .alue fro. 17.1.5 rEED IATES. The system then prompts for the cut type. CUT TVPE i.FACE 2.TURN 3.BORE Enter: To cut perpendicular to the axis of rotation. 2 To cut parallel to the axis of rotation. 3 To cut on the internal surface of the part. or [ to return to the cutting mode prompt. DIIlCTtON I.AWAY PRO" BEAD 2.TOWAJU) BEAD The direction cho.en 1. the dlrectioD of tool travel duriaa a faciD& operation, aDd it i. the direction of the cut .ectora durinl a turaiDI or borinl opera~1on. Inter: 1 To •• lect avay fro. the head.tock. Z To .elect toward the head.tock. 1.STOCl Select the -.aUftt of .tock or the anale of the tool. 2.CUT ANCLE bter: I.ENGAGE ANG-D.DDDD 2.LlrT ANGLE-n.anDD 3.!NGAC DIST-n.DDnD 4.LIPT DIST -a.DDDD 1 to ladlcate the .-cunt of .tock Cesce. . . . teriai) to be left OD the part. Z to ladlcate the aacie of the tool a. it cut. the part. Select tbe aDlle. aDd dl.tance. of tbe tool. Inter: 1 to .elect the eDlale CeDtry) anale. Default.: 11lI1De turret 2 225 315 to .elect the lift (retract) _Glle. Default.: Eftline Turret 3 to .elect the eDlale di.taDce. Default: 4 45 135 6.35 •• (0.250 in) to .elect the 11ft dl.taftce. Default: 6.35 . . (0.250 In) Revision C Menu 17.9: Lathe 17.7 o o Revision C Menu 17.9: Lathe 17·5 17.9.1 RoughiDc 17.9.1 Roughing You can use this ~nu t~ generate a lathe roughing N/C ~achining toolpath. The lathe roughing operation removes large amounts of material in preparation for a another operation like threading or contouring. If you select 1. ROUGHING from the lathe menu. the system displays: -FROM- DESIRED ? -RAPTO SETPT- DESIRED? LATHE TYPE 1.HORIZONTAL 2.VERTICAL Refer to the initialization sequence in Chapter 1. The lathe roughing initialization sequnce is the same as described in chapter 1 except a point needs only XT and VT coordinates. Enter: To define a horizontal lathe that spins around a line parallel to the x-axis. 2 To define a vertical turrent lathe that spins around a line parallel to the y-axis. or [ to return to the -RAPTO SETPT- prompt. The system asks for the headstock origin. The headstock is the part of the lathe to which the part is attached. The origin Should be at the left of the blank for an engine lathe and at the bottom of the blank for a vertical turrent lathe. Refer to figure 17-1. HEADSTOCK ORIGIN 1.SCREEN POSITION 2.KEY-IN 3.EXISTING POINT 4.NAMED POINT Enter: To use the graphics cursor to select a screen position as the headstock origin. 2 To enter the x and y coordinates of the headstock origin. 3 To use the graphics cursor to select an existing point as headstock origin. 4 To use the coordinates of a named point as the coordinates of tne headstock origin. or [ The system prompts for the cutting CUTTING MODE 1.1PR 2.IPM to return to the -HEADSTOCK ORIGIN- prompt. ~ode. The cutting mode is the ~thod used to calculate feedrates. Enter: To select a feedrate based on inches per revolution. The feedrate is calculated by 17.1.5 FEED RATE • )( in/min • )( in y rev/mln 11. 1.6 SPINDLE SPEED 2 To select a feedrate based on inches per minute. If metric units are being used the system displays: CUTTING MODE 1.MMPR 2.MMPM Enter: To select a feedrate based on millimeters per revoluton. The feedrate is calculated the same way as english units desribed above. In this calculation millimeters would be used inplace of inches. 2 --~~--_-'''A_''''1:''U_", .• -_ .. : .. To select a feedrate based on millimeters per minute. _t_,.,,.. ........ l_I',..._lJnc:! o aAMtMOFLE 1---:----l--~-1-1 I : CONTOUR I I I I I t················· I ......., ~~:~:~t::j I AXIS OF ROTAnON I I I Q. 0. I I I II______ .... __ ...!-: _ _ _ _ _ _ _ _ _ II I I INTERMEDlATE7 RETRACT IIOINT .----._..._._ ...._-_._._-. •........,-..------....--- .: .: ---------,"-,:,'::.._------. ..: : '. -------- ..... SEMI ;,------.~ " - . ______ , . , - I ..... ''',' CONTOUR :::: : (NO BLANK) .11,1 ::i:: .. () \ FINISH .. .......••.••-.......... pe._ '---------·• ··•• I!,'' HEADSTOCK ORIGIN Figure 17·2. Lathe Profile o .,.......... _- -~--, __ ,..--.-:.=~_~.=.~ ~'2~_._._" ___.__ . . _ Revision C 17 Menu 17.9: Lathe You can use this menu to machine surfaces of revolution. Refer to figures 17·1 and 17-2. Although the produced part is three-dimensional, the data used to generate lathe paths onsists of a two-dimensional profile in a quadrant. The lathe operation can be used with engine lathes and vertical turret lathes. The available operations are rough, semifinish, and drill. Only half the profile requires definition all in one quadrant. The x-axis is used for the axis of rotation for an engine lathe and the y-axis for the turret lathe. The generated tool path is two-dimensional, defined at the current depth. To ensure that no spikes occur in offsetting geometry all entities selected should be contiguous. t The retract plane and clearance distance modal values control the positions of the first two GOTOI points in a lathe drilling toolpath. The first GOTOI point is at a retract plane value away from the indicated start position. The second GOTOI point is at a clearance distance away from the indicated start position. (At this position, the FEDRAT is changed from the rapid value to the fmish feed value.) If the first GOTOI point is not desired, the retract plane should be set to a smaller value than the clearance distance. The clearance distance also controls the distance the drill is withdrawn during reciprocating moves and how close the drill approaches the bottom of the hole before switching to fmish feed from rapid . : ....,pt- ~' l \.~h;;·;~···-··-··············i ~1 ..' . ....... ............... : l i. -.......... : \....... !: \ .A. : !\..""- ~ ~..... _.~ . .Gt. : .~-- _.__.....•......_...__. ..... . ENGAGE MOLl ··· · · ............ _............................. . i . Figure 17-1. Lathe Parameters The lathe operations contouring, drilling, and threading use the Easy Generation User Interface feature. For more information on the Easy Generation User Interface feature refer to chapters 3, 4, 5, and 7. C~I Revision C Menu 17.9: Lathe 17·1 o Indicate the start and end of the rust cut. INDICATE START OF 1ST CUT U Be the graphics cursor to select a position near a corner of the surface to be machined that is the position of the tool at the start of the rust cut. INDICATE END OF 1ST CUT Use the graphics cursor to select a position Dear a comer of the surface to be machined that is the position of the tool at the end of the first cut. If' milling to a depth, specify the pus preparation parameters. PASS PREPARATION 1.NUMBER OF CUTS Enter the number of cuts desired to be equally spaced over the surface. 2. SCALLOP HT Enter the maximum scallop height permissible between cuts. 3.STEP OVER Enter the amount that the center of the tool is to step over for each consecutive path. Select the containment ~. Refer to figure 14-1. CDNTAINIENT TYPE o 1.DRIVE 2.STOP S.JtIF 4 • tOE OR I«) .:ItE Enter: 1 To drive the tool along the containment curve. 2 To stop the tool motion when the containment motion comes to the end of a cut and redirect it to the next cut, path. 3 To have the tool stop at the containment, retract to a position that allows the tool to clear the containment. move across the containment, and then resume cutting on the other side. 4 To terminate the containment selection sequence. This series of' prompts continues until the maximum number of selections is achieved or this choice is made. 1.ZT MINIMUM- n.nnnn Enter values for the zt containment. Defaults: 1270 mm (50.00 in). o By specifying a minimum z-clip value, the toolpath points are generated such that the tool does not travel below the z-clip value. The tool center point does not necessarily lie on the z-clip value. However, the tangent point of'the tool is at the clipped value. The tool ,maintains the same orientation that it had with no z-clip value specified. Ref'er to figures 14-2 and 14-3. 14... leEM Numerical CoDUoI for NOS Revision C Select the method of controlling the cutting depth of the tool. CONTROL SURFACE 1. SURFACE 2.DS,TH Enter: 1 To mill to a surface. the system displays: INDICATE SURFACE Ule the graphics curlor to lelect a lurface. When a surface is chosen, the screen will display a message stating the current retract height and the highest displayed surface point. The user must then use discretion as to whether the retract value should be increased. 2 To mill to a specific depth, the Iystem displays: DEPTH • n.nnnn Select the method of controlling the direction of the cut. CUT DIRECTION I.DIRECTION IN DEGREES 2.INDICATE LINE 3.PARALLEL SURFACE DISPLAY PATK c Option 3 is displayed only when a surface is used to control the cutting depth. Enter: 1 To enter the direction of the cut by lpecifying the degree departure from the 3 orclock position (for example. for a vertical cut. enter 90 0 , -90 0 , 270 0 , or -270 0 ). 1.ENTER DEGREES • n.nnnn 2 To use the graphics cursor to indicate a line to be used to provide the direction. INDICATE LINE 3 Enter the d,egrees. Use the crolshairs or tablet to lelect the line. To have the tool cut parallel to the lurface dilplay. Revision C Menu 1'1.6: Surface Milling 14·3 Headstock Origin CDri1lin~ and Threading Only) o Headstock Origin (Drilling and Threading Only) The origin point of the headstock is set using the following methods. Generate The prompts that appear at toolpath generation time are the same as for the Modify Current Parameters menu except that you do not select the prompting option. Modify If you selected Headstock Origin from the Modify Current Parameters menu, you can set the headstock origin point. HEADSTOCK ORIGIN 1.SCREEN POSITION 2.ENTER COORDINATES 3.EXISTING POINT ~.NAMED POINT 5.PROMPT Enter: 1 To indicate a screen position. Select a screen position as the headstock origin using the graphics cursor. INDICATE POSITION 2 To enter the coordinates of the headstock origin point. Enter the coordinate values of the headstock origin point. ENTER COORDINATES 1.XT • 0.0000 2.YT • 0.0000 3 To indicate an existing point. Select an existing entity as the headstock origin using the graphics cursor. INDICATE POINT 4 To enter the point name of the headstock origin point. Enter the name of the headstock origin point. ENTER POINT NAME: S To be prompted for the headstock origin point at generation time. , o '7-18 ICEM Numerical Control for NOS ......_ .. _ .. Revision C _ _--_ .._-_... - - - - - - _•._.. _...._............. _..._.._......_...__ _. __.__ ._.. _.......................... _............. .. Final Depth Mode COrilling Only) GPG Statement Th~ SDEPTH statement sets the rmal depth mode for drilling. Statement Format: PROMPT n.nn SOEPTHI ptname,thru OELTA,n.nn COIA,dia,pldia CDPTH,depth,pldia Parameter Description PROMPT Prompts for the final .depth calculation options at generation time. n.nn Sets the fina' depth to the axis coordinate n.nn. ptname,thru Uses a named point as the thru amount. Thru amount is the amount drilling is to go past the named pOint. DELTA,n.nn Uses a delta distance (n.nn) to calculate the final depth for each pOint. CDIA,dia,pldia Countersinks to a diameter, with a pilot diameter as the second parameter. CDPTH,depth,pldia Countersinks to a depth with a pilot diameter. ~~~~-----~..-.----_RI!vUion_ C __ ~ ._ _E~uy_~gen/GPG: Lathe 7·17 C,' Command Editor Errors G Message Condition COMMAND PARAMETERS NOT RECOGNIZED. An illegal character appears in the COMMAND PARAMETERS command. or the command format is incomplete. Example: 11 PC-S,L The • (asterisk) is invalid. 11 L.FRED. The . (period) is invalid. 11 C 100,200 (S,H) T 900 Parameter N is illegal within the parentheses. 1?MATRIX/TRAHSL,3,3 The MATRIX command is missing the z parameter. LINE PARAMETERS OVERLAP. o The location to move or copy text is within the range lpecified. This only applies to moving or copying data within the same file. Example: 11 C 100,200 T 150 You cannot copy lines into the same range as the lines themselves. II F,C T F+1 You cannot move lines into the same range as the lines themselves. o ReviaiOD C Menu 11.11: Display and Edit 19-45 Command Editor Errors Table 19-1 shows the basic formats of the commands. Table 19-1. Command Editor Formats Function Command IDITOl MODALS I PIINT •P lp • 1p1,lp2 , N 111 , 1, N 111 DE1.ETE D D lp D lp1,lp2 D.N 111 D 1, N 111 lMSEaT 1 1 1p LOCATE L Ite ...tl BrUCE I. M,e ...tl",ext2" L 1p Ic..xtl L lpl,lp2 Itextl L N III I t ....tl • L 1p N 111 It ....tl c' I. 1p text1 c.ext2 • 1pl,lp2 l,e ...t1/c.e ...c.21 I. N 111 'c.e... tl'C..xc.2' I. 1p N III " .... t1't ....t2' COpy C C C C lp1 T 1p2 R r1 lp1.1p2 T lp3 R r1 N n1 T lp R r1 lp1 N n1 T lp2 R r1 COpy from another file fname C C C C 'pi (fname) T 1p2 R r1 lp1.1p2 (fname) T lp3 R ,..1 N n1 (fname) T 1p R r1 'pi N n1 (fname) T lp2 R ,..1 COpy from another toolpath C 'pi (S) T lp2 R r1 C , pi. 1p2 (S) T 1p3 R ,..1 C N n1 (S) T lp R r1 C lp1 N n1 (S) T lp2 R ,..1 MATRIX COpy C 1P 1 (M) T 1 p2 R ,..1 MATRIX COpy from another f i ,. fname C C MATRIX COpy from another tool path C lp1 (S.M) T lp2 R ,..1 C , pi. , p2 (S. M) T 1p3 R ,..1 C N n1 (S.M) T 1p R ,..1 C lp1 N n1 (S.N) T 'p2 R ,..1 C lp1.1P2 (M) T lp3 R ,..1 C N n1 (M) T lp R ,..1 C 1piN n 1 (M) T 1 p2 R ,..1 lp1 (fname.M) T lp2 R ,..1 lp1.lp2 (fname.M) T lp3 R ,..1 C N n1 (fname.M) T lp R ,..1 C lp1 N n1 (fname.M) T lp2 R ,..1 (Continued) Revision C 19-48 JCEM Numerical Control for NOS . - - - - - - -... ~-~--.-.---------~.- o 2 - Surface Profile Tool axis control for paral,.' to drive surface condition Since the condition normal in ruling of tool axis is not fully defined by this condition. a second is set. The tool axis in case of a toolpath or the curve case of a machine curve i5 generated parallel to the V the drive surface at the contact pOint. Example A toolpath is generated with a horizontal cylinder as part surface and a vertical cylinder as a dr.ve surface. The multi axis condition parallel to drive surface is used. In the first case the vertical cylinder is defined as a surface of revolution. through the cylinder definition or by rotating a line. Figure 20.01 showS that the tool axis is horizontal. thus parallel to the V ruling. In the second case. the cylinder is defined as a ruled surface. between two congruent arcs in parallel planes. Figure 20.02 now ShOWS a vertical tool axis. again parallel to the V ruling. C) o 20-5 -------- _._---_._-----_.. _- -_.._--_... , !., • ~ o o Cr 20-6 o L...--L.~m:i1~~~!~ll;[---- o -------- 20-7 WARNING MESSAGES FROM 2 SURFACE PROFILE MODULE 1. \'-., .-" 5.1. FROM START POSITION NOT FOUND "Tool Tangent Surfaces and Edges" was indicated. The system searches for any Surface Intersection point from a selected 3-D start position. If the intersection point is not found, then the message is displayed. 2. OFFSET 5.1 FROM START POSITION NOT FOUND "Tool Tangent Surfaces" was ,indicated. The system searches for any Surface Intersection point of offset surfaces with the offset distance equal to .the radius. The search process is started from a selected 3-D position. If the offset S.I. is not found, then the message is displayed. 3. USE SMALLER TOOL 3.1 "Tool Tangent Surfaces" was indicated. The radius of the surface curvature is smaller than the tool radius. The calculation is stopped and the calculated path is displ~yed. The user can start the calculation of a second path from the opposit direction. To avoid the undercutting the Machine Cu~ves can be generated and then tri~.ed by using Trim Curves. By chaining these curves toge~her by sel~ction in Absolu~e Tool Ho~ion the teol path is generated. 3.2 "Tool Tangent. Surfaces and Edges" was indicat.ed. The radius of the surface curvature in the interval where the tool maintains tangency with both surfaces is smaller than the tool rad1us (= unde==utting). The calculation of the teol path con~inues. The "undercutting" is not eliml.nated from the calculated and cisplayed path. c/ 20-8 --,.,-. -- ._--, ' --,,'._, ~'--'.-.-~-,--,--'" --, , o 4. USE SMALLER TOOL (TYPE 4) "Tangent to Surfaces and Edges" was indicated. The radius of the surface curvature in the interval where the tool maintains tangency with one surface and the edge of the second surface is smaller than the tool radius or the radius of the surface curvature is smaller than the tool radius (undercutting). The calculation 9f the path continues. The "undercutt.ing" is not eliminated from the calculated and displayed· path. Use Trin Curves method. 5. NON CONVERGENCE (TYPE 1) "Tool Tangent Surfaces" was indicated. The system cannot calculate the next point on the path within tolerance. The maximal number of iteration steps was exceeded. The calculation is stopped and the calculated path is displayed. o 6. NON CONVERGENCE (TYPE 2) "Tool Tangent'Surfaces and Edges" was indicated. The system cannot calculate the next point on the path within a tolerance. The maximal number of iteration steps was exceeded. The calculationn is stopped and the calculated path is displayed. Try again by changing the parameter setting ·the STEPSIZE negative The Calculation will s~art from the opposit side. 7. NON CONVERGENCE (TYPE 5) The sec~rity leop having control of the whole iteration process was exceeded. The calculation is stopped and the calculated displayed. o 8. pa~h is SURFACES PARALLEL The system has recognized the parallel surfaces. 20-9 . _ - - - - - - - - - - - - - - - - - - - - - _ . _ - - - - _ . _...- - - c C ~I / REPLACEMENT PAGES o MANUAL TITLE: IeEM GPL 60462520 PUBLICATION NUMBER: REVISION LEVEL: B INSTRUCTIONS: To update this manual t for which the previous revision was B t make the following changes: Remove: Insert: 13-7,8 13-7,8 21-3,4 21-3,4,5 o o ._.._-_._.._..,-------,,_.,".- ......--_._._._._--_. __ .... .. .. _,. ,-, ,-' , __ ..__._-_._._._ ..- .'.'.".. ,.'. -' .. "-,, -._---_._.,_._,--- .. '._---_._..__..._._--_._.._._-----------,--_ ..__ ..... _-- r I \.._ .. , CI •. - - - - - - - - - - - SPLINE o SPLINE A spline is a free-form curve generated from a series of ordered points so that slope and curvature are contiguous at each given point, approximating the physical use of a spline. The spline start or end condition can be either circular (default) or parabolic. For circular start or end conditions, specified slopes are optional. All symbolic points are projected into transform space before processing. The depth coordinate is determined by ZSURF if the points are not coplanar. A minimum of three points and a maximum of 42 points must be specified. Refer to menu 12.1 SPLINE in the ICEM Design/Drafting Basic Construction manual. The optional parabolic start and end conditions provide for a starting or ending parabolic segment in the spline. If parabolic conditions are not specified, the end segments are assumed to be circular. o The spline tolerance option is used to specify the maximum discontinuity in the curvature of the spline. Acceptable values are positive and greater than or equal to 0.000001. Smaller values slow the creation of the spline, and, depending on the particular points, values very much smaller may prevent the spline from being created. The optional circular start and end slopes are used to force the angle of tangency of the spline at the first or last points. If the start and end slopes are not specified, a circular end condition is assumed. The point movement option provides for a minimum of strain energy at each point. If the point movement option is used, the spline points are adjusted to the specified tolerance. The spline constrains to the first and last points, but is within tolerance of the intermediate points only if needed. The spline can be defined by the following methods: • Specifying existing points or coordinates. • Polar from origin. • Specifying a number of points from an entity array. o ". Reviaion B .....-........ _._._------------ Two-Dimensional Curve Statements 13·7 -._...... _--------------------------- Statement format: . [POint ) SPLINE/ xcoord.ycoOrd [.SLOPE.angle]. RADANG.rad1us.angle PMBLe • [.SLOPE.angle]I.(~I.DOtnt PMBLe neve l [POint xcoord.ycoord ) [ •••• ] RADAHG.rad1us.angle NUMBER,nu.ber.(D01nt array) coord array adj value][.TOL£R.SDune tol value] . Parameter DeacriptiOD point The names of the points uaed to create the apline. scoord The z-coordinate of the point. ,coord The y-coordinate of the point. RADANG The minor word for specifying the points of the spline from the origin (0,0) using the radius and angle. radius The .radius from the origin to the point in units of meuure. angle The angle of the point to the horizontal axis in degrees. SLOPE The minor word indicating a Ilope angle for the ltarting or ending point. . angle The Ilope angle PARBLC The minor word lndicatini that the tint or Jut tegment of the ~liDe point NUMBER or the ltarting or eDd;n, point. 11 • parabola. The Dame of • Itarting point for the Ipline. The minor word for specifying a Dumber of points from a point or .. coordinate array. number The Dumber of points or coordinates in the entity array. point array The Dame of. point array. coord array The XYMOVE, XMOVE, YMOVE The minor words indicating the point adjustment value. XYMOVE allows the movement constraint in both the %t and yt directions. DOVE allows movement only in the %t direction. Ule movement eonstraint cautiously and only with very Imall values. Avoid movement constraint unless it is ablOlutely necessary. point adj value The amount curve. TOLER The minor word indicating the spline tolerance. spline tol value The maximum amount of discontinuity in the curvature of the Dame apline. 13-1 JeEM GPL ~ ~~_~ of. coordinate array. or allowable point movement used in approximating the TLPATH o Example: Program Statement Explanation ENTITY/T143 Defme entity T143. REAL/S Defme status variable. OBTAIN/ENTPTR.'TL143'$ .T143.S Obtain the pointer of existing toolpath TL143 and assign it to T143. SETGPG/LATHE.DRILL.T143 Replace the current drilling GPG with the GPO from toolpath TL143. TLPATH The TLPATH statement provides the ability to define toolpath entities for LATHE contouring, drilling, or threading operations. Contouring and threading toolpaths are generated along part geometry (specified as a list of entities). Drilling toolpaths do not require any geometric entities. Each toolpath reflects the current GPG settings for that operation. Interactive prompts are not allowed with this statement. Therefore, any GPG settings of PROMPT are changed to default values. o The following self-explanatory error messages can occur from improper use of the TLPATH statement. ENTITY t()T FOUND INCOMPATIBLE ENTITY USED IN DEFINITION DEFINITION START INDETERMINATE INVALID NUMBER SUPPLIED GPG tilT C(lFATIBLE WITH ENTITY TYPE CONTOURING Statement format: t p name.TLPATH/LATHE.CONTUR.(ent1.ent2 •...• entn )[.START.(xt.yt)] NUMBER.number.ent array po1nt Parameter o Description tpname The name assigned to the defined toolpath. LATHE The minor word indicating lathe toolpath parameters. CONTUR The minor word indicating a entl through entn A list of entities used to create a toolpath. The entities can be lines, arcs, conics, two-dimensional and three-dimensional splines, bezier curves, point sets, and machine curves. The limit of the total number of entities is lathe contour toolpath. 64. ReviaiOD B Numerical CoDtrol StatemeDts 21-3 TLPATH Parameter De.cription NUMBER The minor word indicating the number of entities in the entity array. number The number of entities in the entity array. of entities is 100. ent array The name of an entity array. START The minor word indicating the starting entity selection point. xt,yt A space location expressed in transform coordinates indicating the starting entity selection point. point The name of a point indicating the starting entity selection point. The maximum number Example: The following statement creates a lathe contour toolpath using 21 entities cuntained in the entity array AR33. The new toolpath is named T322. T322-TLPATHiLATHE,CONTUR,NUHBER,2l,AR33(1) c DRILLING Statement format: t~·TLPATHlLATHE.DRILL Parameter Description tpname The name assigned to the defined toolpath. LATHE The minor word indicating lathe toolpath parameters. DRILL The minor word indicating a lathe drilling toolpath. Example: The following statement creates a lathe drilling toolpath named .TP134. All the parameters needed to create the toolpath must be specified in the GPG. TP134-TLPATH/LATHE,DRILL 11-4 ICEM GPL for NOS , Revision B TLPATH 10 THREADING Statement format: Parameter DeacriptiOD tpname The name assigned to the defined toolpath. LATHE The minor word indicating lathe toolpath parameters. DRILL The minor word indicating a lathe contour toolpath. entl The entity used to create the toolpath. START The minor word indicating the starting entity selection point. xt.yt A space location expressed in transform coordinates indicating the starting entity selection point. point The name of a point indicating the starting entity selection point. Example: The following statement creates a lathe threading toolpath using the entity LN52 with the starting entity selection location at point PT10. The new toolpath is named T4l3. T4l3-TLPATH/LATHE.THREAD.LN52.START.PT10 :0 - - - - - - -_ _ _ _ _ _ _ _ _ _ _ Nn"".rieal .. CoDtrol_8t.atamenta __.21.::5 .. _ ...____ - ---- - - ~------~- C""/7 .---.----*---.. -~. SOFTWARE RELEASE BULLETIN ICEM DDN VERSION 1.57 NOS 2.3 LEVEL 617B ******** URGENT ********** Please make this document available to all ICEM DDN users! ** This document describes new features and changes to ICEM DDN. ** Also found here is a list of known and outstanding system problems (PSR's) and a list of resolved system problems. SMD130848 _. . r~ TABLE OF CONTENTS PAGE INTRODUCTION 2 ICEM DDN V1.57 PUBLICATION STATUS 3 GENERAL SYSTEM WARNINGS 4. REVIEW BY MENU SECTION: 5 SECTION 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. TERMINAL SUPPORT SPECIFYING THE TERMINAL CREATING A PART CONTROL CARD PARAMETERS MODALS AND FONTS BLANK/UNBLANK DELETE FILE/TERMINATE SPECIAL FUNCTIONS DATA BASE MANAGEMENT INPUT/OUTPUT DISPLAY CONTROL POINT LINE ARC/CIRCLE/FILLET OTHER CURVES ENTITY MANIPULATION DATA VERIFY EXTENDED GEOMETRY 16. DRAFTING FUNCTIONS 17. N/CMANUFACTURING 18. ANALYSIS 19. SI/US/RESIZE TABLET INTERFACE (no changes) (no changes) (no changes) (no changes) (corrective code) (no changes) (corrective code) (no changes) (new feature, menu changes, corrective code) (corrective code) (corrective code) (no changes) (corrective code) (no changes) (corrective code) (corrective code) (no changes) (no changes) (enhancements, menu changes, corrective code) (corrective code) (enhancements, menu changes, corrective code) (no changes) (no changes) (no changes) 6 6 6 6 6 6 6 6 7 10 11 11 11 11 11 11 11 11 12 13 15 23 23 23 OUTSTANDING SYSTEM ERRORS ••••••......•.•..•••...•.•.••• A-I RESOLVED SYSTEM ERRORS B-1 1 --_. _._--_ .. __........._._- r', ( '----.. ,,/' INTRODUCTION This SOFTWARE RELEASE BULLETIN (SRB) is designed to inform site analysts and ICEM DDN users of: ~', New features, Menu revisions, * Operational changes and enhancements, ,': Known, outstanding system problems and suggested work arounds, and * Resolved system problems which existed in previous versions. * The review of new features, menu revisions and enhancements is organized by menu section (see Table of Contents for t~e menu sections of particular interest). () o 2 C .. , ",,/ i ., ICEM DON Vl.57 PUBLICATIONS STATUS The ICEM DDN Reference Manuals have been updated 'for the Vl.57 release and can be ordered through Control Data's Literature Distribution Service (LOS). The following table summarizes the Vl.57 manual update plans: MANUAL (---. ~;. NUMBER MANUAL REVISION PLANS: MANUAL NO MANUAL NEW MANUAL CHANGE PACKET CHANGE ICEM Design Drafting: Introduction and System Controls 60457130 rev J ICEM Design Drafting: Data Management 60461410 rev C ICEM Design Drafting: Basic Construction 60461420 rev B ICEM Advanced Design 60461430 ICEM Design Drafting: Drafting Functions 60461440 rev B ICEM Numerical Control 60461450 rev B ICEM Design Drafting GRAPL Programming Language Reference Manual 60461460 rev B ICEM GPL 60462520 rev A ICEM DDN Instant 60457140 rev F ICEM Tablet Overlays 60458080 rev D ICEM DDN User's Guide 60456940 . rev E rev B () 3 " : o GENERAL SYSTEM WARNINGS A problem exists with ICEM DDN and the NOS 2.3 63-character set. The per cent sign (%) character is incorrectly converted to a colon (:) character. Corrective code for this problem has been generated but is not included in the VI.S7 release. Please consult your local CDC representative, if you use the NOS 63-character set at your site. The ICEM GPL 2D Wilson-Fowler spline implementation for VI.57 does not contain the enhancements that were incorporated into the interactive version of ICEM DDN VI.53. o 4 ". VERSION 1.57 REVIEW BY MENU SECTION This section of the system release bulletin provides a detailed description of those revisions outlined in the overview. The descriptions are organized in the same manner as in the overview--by menu section. Refer to the table'of contents to quickly locate the full description of changes for a particular menu section. I \_.._--' 5 .' TERMINAL SUPPORT No revisions. SPECIFYING THE TERMINAL No revisions. CREATING A PART No revisions. CONTROL CARD PARAMETERS No revisions. 1. MODALS AND FONTS 1.7 Modify Entity Level/Pen No A problem that causes the user to get the current level or pen number when the user answered no (N) to the modify level/pen prompt has been corrected in Vl.57. 2. BLANK/UNBLANK No revisions. 3. DELETE Corrective Code. 4. FILE/TERMINATE o No revisions. 6 ----------,._-, ..",., "'-".'-, , - - - _... ".",., "'-,- .. _ .•.., - , - , , - - - 5. SPECIAL FUNCTIONS ,r'-~ I, \." 5.13 GPL - NEW FEATURE The GPL (Graphics Programming Language) is The ablilty to execute previously compiled via menu 5.13 was added to ICEM DDN at the The GPL compiler is released with ICEM DDN release. a new feature. GPL programs Vl.53 release. at this Vl.57 FEATURE DESCRIPTION GPL is a higher level computer language which executes via an interpreter module within ICEM DDN as the result of an ICEM DDN menu selection. While execution of a GPL program is evoked from within ICEM DDN, it must first be compiled by the GPL compiler external to ICEM DDN. Hence, the GPL system consists of two parts: an interpreter within ICEM DDN and a stand-alone compiler. GPL is designed to mimic ICEM DDN features, not interactively, but parametrically from within algorithms. Therefore, in addition to the standard ICEM DDN features such as modals, entity definitions, and view control, GPL includes statements for declarations, assignments, program control, character manipulation, subroutines, funct ions, input/output, and' several interactive commands. FEATURE CAPABILITIES GPL provides the capability to design families of parts, study kinematics, calculate serial functions, develop tutorials, create customized (user-friendly) applications, and other such high level design tools. One of the most important graphics programming features demanded by customers is "performance improvement". This feature was provided by GPL in version 1.53. Several predecessor features found in GRAFL are targeted for implementation under GPL in version 1.6. 7 ... ~ GPL EXECUTION While the GPL compiler is not required in order to execute GPL programs that are already compiled, another file, GOLIB is required for execution. Although part of ICEM DDN, this file is separate from the file that contains the major portion of ICEM DDN. Thus, to execute GPL programs from menu 5.13, this file must be local with the local file name GOLIB. Refer to figure 5-1. ICEMDDN COMPILER GOLIB GPLLIB SOURCE ICEMDDN: Menu 5.13 GOLIB: GPL secondary overlay file (part of ICEM DDN) COMPILER: To compile GPL source programs SOURCE: File containing GPL source programs (name not unique) GPLLIB: Library of compiled GPL programs plus source Figure 5-1. o 8 -.--................_ - - - - - .... -.. 5.13 GPL .'.... ,~I With this choice, you can execute pre-compiled GPL (Graphics Programming Language) programs. These programs are custom applications ranging from family of parts generators to interactive tutorials. These programs must be contained in a local GPL library. The menu for this section is: GPL 1. RECOVER LAST FILE 2. CONTINUE GPL PROGRAM 3. RUN GPL PROGRAM 4. LIST GPL NAMES 5. CHANGE LIBRARY NAME The following section describes the choices in this menu. 5.13.1 RECOVER LAST FILE With this choice, you can continue program execution following a FILE command in a GPL progr~m (refer to the FILE command). Execution continues at the next statement following the last FILE command. 5.13.2 CONTINUE GPL PROGRAM With this choice, you can continue program execution following a . PAUSE statement in the GPL program. Choosing this menu item when there is no PAUSE statement in the current GPL program returns you to 5 SPECIAL FUNCTIONS. 5.13.3 RUN GPL PROGRAM With this choice, you can execute a GPL program. Prompt Action ENTER SIX CHARACTER NAME Enter the name of the GPL program to run. This name can be from one' to six characters long. 9 ,r~~' ',"- .. " (~) 5.13.4 LIST GPL NAMES With this choice, you can display the names of GPL programs and subprograms contained in a local GPL library. 5.13.5 CHANGE LIBRARY NAME With this choice, you can change the name of the local GPL library that you want to access. The default name of this library is GPLLIB. r··· . ·' Prompt Action ENTER LIB NAME Enter the name of the local GPL library that you want to access. The name of this library can be from one to six characters long. 6. DATA BASE MANAGEMENT ~.) 6.1.8 Pack Part A problem with packing parts has been corrected in Vl.57. 6.2 Pattern Management A problem of two consecutive operation rejects during pattern retrieval occassionally causing ICEM DDN to terminate execution, has been corrected in VI.57. o 10 ---.-----_. __........_._ .... _------ 7. INPUT/OUTPUT ...... Corrective code. 8. DISPLAY CONTROL Corrective code. 9. POINT Corrective code. 10. LINE No revision. 11. ARC/CIRCLE/FILLET Corrective code. 12. OTHER CURVES Corrective code. 13. ENTITY MANIPULATION No revisions. 14. DATA VERIFY No revisions. 11 ,.". 15. EXTENDED GEOMETRY 15.2.1.8 BETWEEN TWO LINES - ENHANCEMENT A ninth method for defining planes has been added in Vl.57. Under menu 15.2.1.8, BETWEEN TWO LINES, two options are now available. The second option, 2. CENTER AND CORNER, is the BETWEEN TWO LINES method from Vl.53, and the first option, 1. ALONG FIRST LINE, is new. This new option creates a plane that is displayed with one edge of its rectangular grid along the first line selected. The plane is displayed as a square with side length equal to the magnitude of the first line selected. The plane is positioned along the first selected line. 15.2.12.1.1 CONE DEFIFITION - CORRECTIVE CODE The def ini t i on of cones wi th 15 ;·i'2. 12.1. 1, CONE DEFINITION using AXIS FORM, EXISTING LINE has been corrected. The pick position used for selecting the line will now determine which way the cone is oriented. The cone will be created with the smaller end toward the selected end of the line. 15.2.15 PROJECTED SURFACES - ENHANCEMENT._.~. The Projected Surfaces feature of ICEM Advanced Design has been rewritten for Vl.57. Projected surfaces allows the user to project a curve, or series of curves, to a depth or onto a surface, then automatically create ruled surface entities between the original curve and its projected counterpart. One surface is created for each curve projected. Up to 240 surfaces may be created in a single operation. The new user interface closely parallels the Draft Curve interface that was implemented in Vl.53. All of enhanced capabilities of the new Draft Curve have now been added to Projected Surfaces. 12 16. DRAFTING FUNCTIONS ~ ..... _ . .. .J 16.1.1 CHARACTER CONTROL - CORRECTIVE CODE The number 1 has been changed in the ICEM DDN drafting character set to make it easier to distinguish from the capital letter I. The letter M and the number 3 in the ICEM DDN drafting character set have been changed so that they now comply with ANSI standard. 16.1.2 TEXT JUSTIFICATION - CORRECTIVE CODE Text justification was modified for Vl.57 so that preceding text with limits will be centered only when there is preceding text with the first limits line and no preceding text with the second limits line. 16.1.4.3 AUTOMATIC DIAMETER SYMBOL - CORRECTIVE CODE A problem with the automatic diameter symbol always appearing ON when drafting modals are displayed has been corrected in Vl.57. ,~ 16.1.14.2 SECTION LINING VISIBILITY MODAL - CORRECTIVE CODE The Section Lining Visibility Modal will now allow you to have section lining displayed in the view of definition only. 16.2 DIMENSION - CORRECTIVE CODE Any dimension with preceding text other than R or a diameter symbol will be marked as keyed-in in Vl.57. 16.2.5 ANGULAR DIMENSION - CORRECTIVE CODE The problem of extension lines not being modified correctly on angular dimensions has been corrected in Vl.57. 13 . . . . . .1" •• 16.3 SECTIONING - CORRECTIVE CODE Problems encountered with open boundaries' in section lining have been corrected in Vl.57. Reasonable boundary gaps are now permitted for section lining. 16.7 GEOMETRIC TOLERANCE - CORRECTIVE CODE Text created with 'geometric tolerance symbols will now be defined at the current depth. 16.11 LABEL - CORRECTIVE CODE Problems with parts that had labels with multiple dashes or plus signs and problems with labels pointing to the opposite side of the selected arc have been corrected in Vl.57. 16.13.4 ADD/CHANGE TOLERANCE LIMITS - CORRECTIVE CODE A problem with adding tolerance to a dimension that has multiple lines of text has been corrected in Vl.57. C~) 16.13.13 BALLOON MODIFICATION - CORRECTIVE CODE The problem of text in a balloon taking on the current pen and level when modified and the problem of text moving incorrectly when modifying the radius of a balloon have been corrected in Vl.57. 16.13.17 MODIFY DECIMAL PLACES - CORRECTIVE CODE Fractional dimensions will have the correct number of decimal places and will be displayed correctly after decimal places are modified. o 14 . - ._----_._-_..-.. - - - - - - - - - - ._..__ .__ ....... _..._.. _.. ....... - - - _ . /"'- -" I \,,-,., 17. N/C MANUFACTURING 17.1 DRILL REFERENCE MODAL ENHANCEMENT A Modal will be added to the Modals section of N/C to allow the user to define the reference point of the tool used in Lathe Drilling and Point to Point Machining. The Present menu in Lathe for tool reference will be removed. The menu will be located at 17.1.16. The modal will only effect the Drill, Centerdrill, and Countersink tool reference points. The modal will appear as: DRILL REFERENCE POINT 1. DRILL TIP 2. DRILL LIP Choosing 1 will locate the reference point at the tip of the tool, and will configure the system to output a move that will bring the tip to a desired depth. Option 2 will bring the lip to a desired depth. Option 2, Drill Lip, will be the default. 17.2 POINT-TO-POINT USER DEFINED CYCLES NEW FEATURE Menu 5. Cycle Control in the Tool Motion Control section of Point-To-Point will be split into two new menus. The first of these two, 5. Machine Controlled Cycle, will be the same as the old menu. When this menu is selected you are prompted to enter cycle commands that will appear just before the first selected point. These commands will tell a postprocessor to turn on the cycle G-code. After each machine motion the cycle sequence is executed. The second menu, 6. User Defined Cycle, will allow you to enter N/C statements which will appear after each selected point. This option can be used to make machine independent cycle sequences. This option will increase the length of the toolpath because the user defined cycle will appear after each point not just in front of the first selected point. 15 17.2 and 17.9 COUNTERSINK/CENTERDRILLING ENHANCEMENT This enhancement can be categorized into three major areas, the addition of a countersink operation in Lathe and Point to Point Machining, the adding of a modal defining drill reference points for Point to Point Machining and Lathe, and the use of an upgraded chip relief option in Lathe. A change in the Lathe entity select will also be incorporated. 17.2 and 17.9 POINT-TO-POINT/LATHE COUNTERSINK OPERATION ENHANCEMENT The countersink enhancement will be contained in the Final Depth menu in Point to Point Machining, and the Depth Mode menu in Lathe. For Point to Point the menu will appear as: FINAL DEPTH 1. ABSOLUTE 2. INCREMENTAL 3. COUNTERSINK TO DIAMETER 4. COUNTERSINK TO DEPTH This form of the final depth menu will only appear if a legal countersink tool of Drill, Centerdrill, or Countersink is chosen. If any other tool is chosen only the first two options of the final Depth menu will be given. In Lathe the menu will appear as: FINAL DEPTH 1. SCREEN POSITION 2. KEY-IN POSITION 3. EXISTING POINT 4. KEY-IN DEPTH 5. COUNTERSINK TO DIAMETER 6. COUNTERSINK TO DEPTH As in the Final Depth menu of Point to Point, if a tool other than a countersink tool is chosen only the first 4 options of this menu will appear. o 16 COUNTERSINK TO DIAMETER Countersink to Diameter allows countersink to a desired diameter. Upon selection of this option the user is prompted for the desired diameter: 1. CSINK DIA 2. PILOT DIA Tool motion is generated using the tool angle to give the desired diameter as measured across the countersink at the indicated part surface. A clearance distance from the contact point on the edge of the pilot hole is used to stop the rapid motion. If the desired countersink is larger than the tool diameter a warning will be given. Execution will not be effected since some shops may desire to define their tools with a l~p diameter as opposed to a body diameter. COUNTERSINK TO DEPTH Countersink to Depth will output a tool motion that will give a desired depth of a countersink measured from the part surface. Provisions for a pilot hole are made. Upon selection of this option this user is prompted for: 1. CSINK DPTH= 2. PILOT DIA The depth of the countersink is defined as the distance along the drilling axis from the start position to the point where either the countersink intersects the pilot hole or in the case of no pilot hole, the position of the tip. The default value for the pilot hole diameter will be O. TOOL AVAILABILITY The only legal tools allowed by the countersink operations are the Drill, Centerdrill and Countersink Tools. o 17 () 17.9 LATHE CHIP RELIEF ENHANCEMENT '-,- Currently in the Lathe package there are three options for chip relief; none, reciprocate, and chip break. This menu will be replaced with the same chip relief options available in the present Point to Point Machining. After selecting from the DRILL METHOD menu the user will be given the chip relief options in the TOOL MOTION CONTROL menu: TOOL MOTION CONTROL 1. ONE CONTINUOUS CUT 2. CHIP RELIEF/DELTA RETRACT 3. CHIP RELIEF/WITHDRAWAL 4. CHIP RELIEF/DWELL 5. MACHINE CONTROLLED CYCLES These options will function exactly as in Point to Point Machining ( limited to 2-D ). 17.9 LATHE ENTITY SELECTION MAINTENANCE C) ENHANCEMENT Currently in Lathe, when an entity is selected for the start or end of drilling, the end of the entity furthest from the headstock is chosen. This will be changed to allow the end of the entity closest to the selection point to be chosen instead. 17.9 LATHE INSERT NEW FEATURE The Lathe Insert feature provides the user capabilities to insert, delete, and list postprocessor commands at the beginning and end of lathe toolpaths prior to toolpath generation. Only commands defined in the current postprocessor word library may be entered. (See ICEM Numerical Control Reference, section F.17.10.5). A similar capability currently exists for point-to-point, profile, and pocket toolpaths. o 18 · .. _._._-----_._---------------,_._-,,,,-"' "'" , . -_. __._--_._ _--------"...._,,-_ .. ....... ,,,_ .. __ . STARTING SEQUENCE The starting sequence will allow the user to enter, delete, or list N/C statements at the beginning of a lathe toolpath. The starting sequence will be contained in the Lathe menu under Lathe Operation. After the type of operation (rough, semi, finish, drill) and tool have been selected, the system will prompt for the starting insert sequence. Prompt Action STARTING SEQUENCE I.LIST Enter: To list the existing inserted commands. 2 To enter commands at the start of the toolpath. 3 To delete all inserted starting commands. 4 To exit the insert menu. 2.ENTER 3.DELETE 4.EXIT 1 The N/C statements created in this menu will appear at the very beginning of the toolpath before any GOTO or FROM statements. All postprocessor startup commands may be entered here. ENDING SEQUENCE The ending sequence will allow the user to enter, delete, or list N/C statements at the end of a lathe toolpath. The ending sequence will be contained in the Lathe menu under Lathe Operation. 19 Just before the toolpath is displayed and named, the system will prompt for the ending insert s~quence. The ending insert sequence is identical to the starting insert sequence. Prompt Action ENDING SEQUENCE I.LIST Enter: 1 To list the existing inserted commands. 2 To enter commands at the end of the toolpath. 3 To delete all inserted ending commands. 4 To exit the insert menu. 2.ENTER 3.DELETE 4.EXIT The N/C statements created in this menu will appear at the end of the toolpath before the SETPT command. 17.9.5 LATHE THREADING CJ NEW FEATURE This feature allows the user to create a single point tool threading toolpath. The threading feature can produce external or internal threads, single or multiple lead threads, axial threads (parallel or tapered) or face threads. The toolpath can have up to 30 constant volume cut passes. DEFINE TURNING TOOL The threading feature will use the standard tool definition and selection sequence. The threading tool's parameters are as follows: TOOL NAME: name TOOL TYPE: LATHE THREADING I.TOOL NUM N 2.TIP ANGLE = NN.NNNN 3.X GAGE LEN= NN.NNNN 4.Y GAGE LEN= NN.NNNN default: default: default: default: o 20 I 60.0 0.0 0.0 range: N>=O range: 0 MARKS GET INCREMENTED TO THE RIGHT (5.10) LDF NOT UPDATED WHEN NESTING TEMPLATE IS MODIFIED. (TABLET) DOUBLE KEY-IN NAME ON 411X AND TABLET. (5.2.3.2) ERROR MSSAGE ON 721--0UTPUT TOO BIG FOR UTF--OUTSIDE DIALOG MODIFY/REPLACE VECTOR, LDF NOT UPDATED WHEN KEYING AHEAD BETWEEN PARTS THE BELL SOUNDS TEK 4105,7,9 TERMINALS PRINT GRAPL PROGRAM INFO ON ONE LINE 721 TERMINAL IS IMPROPERLY RESET AFTER LEAVING ICEMDDN THE 721 VIKING TERMINL IS LEFT IN ERROR UPON EXIT 721 GRAPHICS TERMINALS RETURN TO GRAPHICS AFTER EXIT ICEMDDN (DIGITIZE) EVENTUALLY LOST THE ABILITY TO DIGITIZE CERTAIN ENTITIES. BACKSPACE DOES NOT ERASE CHARACTER WITH TABLET, ALPHA, 4016,GTA-1. TABLET/TERMINAL BECOME INACTIVE. TERMINAL 4115B BAD CUT VECTORS IN LDF. SPIKES ACROSS THE SCREEN ON 4115 TERMINAL CROSSHAIRS DO NOT RETURN TO ACTIVE IF TERMINAL LOCKS UP ON A 4115 TEKTRONIX 4115 DISPLAY CHARACTER SIZE IS CHANGED WHEN ICEM DDN IS EXITED SUPPORT OF TEK4109 WITH TABLET TEK4957 BY ICEM PRODUCTS. ICEM DDN REQUIRES EXTRA CARRIAGE RETURN W/L=O AND TB=Y PARAMETERS MANUAL IS INCORRECT ON TERMINAL SETUP FILLET W/SPLINE & LINE FILES (17.4) STEP-OVER IN POCKET LEAVES MATERIAL. (17.9) SEMI FINISHES FAILS TO FOLLOW BOUNDARY MISC. FUNCTIONS INVERTS LATHE DISPLAY NC - LATHE ROUGHING FACE CUT ORIGIN IS AMBIGUOUS. ICEM DDN NC LATHE AND MILLING PROBLEMS. LATHE ROUGH BORE PLACES ROUGH STOCK OFFSET ON WRONG SIDE(1.49X) LATHE DRILLING PRODUCES WRONG CENTERING MOTION LATHE DRILLING DOES NOT ALLOW CONTROL OVER DWELL LATHE ROUGH FACING OFTEN FAIL (F.17.9) CONSTANT SURFACE SPEED IN ICEM N/C LATHE, & MODAL SETTINGS (F.17.9) ICEM N/C LATHE FINISH STOCK NO CIRCLE RECORD OUTPUTTED FOR LATHE ROUGHING LATHE TURNING OF A SINGLE ENTITY A REJECT AT SCREEN SELECT IN LATHE BACKS UP TO LATHE OPERATION A-8 C~ c) PRIORITY CODE: C=CRITICAL U=URGENT S=SERIOUS M=MINOR D=DEFERRED NUMBER AD22262 AD22265 AD22266 AD22226 AD20928 AD21194 AD21465 AD21468 AD22092 AD22210 AD22264 AD22278 AD2A455 ---. AD2A525 C,\AD20772 AD22298 AD20577 AD20803 AD21193 AD22190 AD22309 AD22310 AD2A555 AD2A557 AD2A599 AD2A603 AD2A612 AD2A654 AD21246 AD21268 AD21359 AD21362 AD22038 AD22220 AD2A286 AD2A440 AD2A467 AD2A470 AD2A500 (--") '" PRIORITY STATUS: C=CURRENT 1= INTERNAL PRI C I PROBLEM ABSTRACT S M S S UU S S UU UU S S S S S S S S MM S S UU S S UU UU UU CC UU CC UC CC S S S S S S MM MM MM MM S S UU S S MM CC S S MM S S UU UU CAN NOT BACK UP PAST STOCK AND CUT ANGLE PROMPT IN LATHE LATHE PACKAGE PICKS UP DEPTH SET IN SYSTEM CAN NOT GENERATE ROUGH LATHE TOOLPATH WITH .03 RAD AND DEPTH OF CUT .02 (F.17.15)FLAME CUTTING GENERATES WRONG ENTRY AND EXIT TOOL PATH NC - DISPLAY & EDIT TOOL DISPLAY IS VERY BAD FOR ALL MILL USE. DISPLAY AND EDIT IS AWKWARD AND TIME-CONSUMING. NC DISPLAY AND EDIT WILL CHANGE LINE NUMBERS DURING EDITING N/C - TOOL PATH EDITOR INSERT MOTION VECTORS 'DISAPPEAR EXCHANGE FEEDRATE TRUNCATES UNIT PARAMETERS SUCH AS IPR N/C TOOLPATH EDITOR FAILS TO UPDATE VECTORS IN 4115 DISPLAY REJECT IN DISPLAY AND EDIT RETURNS TO NC MANUFACTURING MENU A CNTL D ENTERED IN DISPLAY AND EDIT PRODUCES UNDEFINED ADDRESS LATHE NC MACRO NOT COMPATIBLE (17.2.2) PITCH DOES NOT WORK AS DOCUMENTED. (17.2.2.2) TEMPLATE RELATIVE TO PLATE (TOOL PATH WRONG). F.17.2 - POINT TO POINT PUNCHING (17.5) COMPOSITE SURFACES DO NOT MACHINE (17) ICEM DDN ABORTS DURING PATH OF RULED SURFACE. CAN NOT USE COMPOSITE CURVE AS DRIVE OR CHECK CURVE 3 - AXIS TOOLPATH IS WRONG PERFORMANCE PROBLEM WITH SURFACE MILLING METRIC INCOMPATIBILITY FOR NC. INCONSISTENCIES BETWEEN MENU OPTIONS--INCREMENTAL POINTS INCREMENTIAL POINTS--WRONG PARAMETER VALUE FOR ARCS MENU CHOICES LIKE 00, 111 AND 88 ARE ACCEPTED AN [ TO LEVEL CHANGE REQUEST RETURNS TO ENTITY SELECTION NO HELP MESSAGES IN ANALYSIS AREA (12.4.6)STING BEARING DEGREE ENTRY NOT TURNED ON MISTAKE IN VERSo 1.5 MAIN OVERLAY, CHANGE SCALE SHOULD BE CHANGE PAGE DISPLAYING MAIN MENU HEADER-NO CHECK IF HEADER FITS IN AVAILABLE SPACE TOO MANY "UNNECESSARY" OP COMPLETES REQUIRED ON DATA ENTRY SUBTRACTIVE COLOR TABLE MANIPULATION SEEMS AWKWARD/INCOMPATIBLE MENU 1.10 ON THE ICEM DDN OVERLAY STILL READS TOGGLE BLANK/UNBLANK. ENTITY MANIPULATION REQUIRES TOO MUCH REPEAT INPUT. (1.11.5/R) ATTENTION INDICATORS DISAPPEAR AFTER REPAINT WHEN· LEVEL TABLE INITIALIZE ERROR. MULTI VIEWS AND OFFSCREEN ENTITY HAS PROBLEMS IN SELECTION. POUND SIGNS ARE DISPLAYED IN STORAGE ON 4114. (MANUAL) LEVEL TABLE NOT ASSIGNED ERROR MESS INCORRCTLY EXPLAINED. ./ A-9 - - - - - - - - - - - _ . __ ..__ ._--.-- ._-_.-..........- ................. PRIORITY CODE: C=CRITICAL U=URGENT S=SERIOUS M=MINOR D=DEFERRED PRIORITY STATUS: C=CURRENT 'i=INTERNAL NUMBER PRI C I PROBLEM ABSTRACT AD2A537 AD2A551 AD2A657 AD2A660 AD20720 AD20996 AD21002 AD21159 AD21174 AD21183 AD21192 AD21215 AD21320 AD21321 AD21360 AD21438 AD21497 AD22061 AD22071 AD22113 AD22159 AD22188 AD22193 AD22196 AD22315 AD22349 AD2A274 AD2A276 AD2A469 AD2A540 AD2A257 AD2A364 AD2A433 AD2A507 AD2A661 AD20626 AD20637 MM S S MM S S S S S S UU MS UU S S S S CC UU UU UU MM UU CC CC S S MM CC UU UU CC UU S S S S UU UU S S MS MM UU MM MM MM (5.2.3) WHEN AN ERROR OCCURS, MENUS GET TURNED OFF. (F.12.1.5.3) CHAIN SELECT THE MANUAL DESCRIBING F.3.9 IS INCORRECT POINTS OUTSIDE OF E-CLIP RANGE MAY BE SELECTED (3.7.5) 3 BALLOONS DELETED AS ARRAY AND GROUPS. AFTER OP REJECT, SYSTEM WILL RE-PICK THE SAME ENTITY. (3.3.3.1)ENTITIES OUTSIDE OF REGION PICKED FOR DELETION. CHANGE VIEWS - RIGHT/LEFT DOES NOT SCALE CORRECTLY. PROGRAM STOPS ACCEPTING SCREEN POSITIONS. TITLE BLOCK OVERLAY ATTENTION BLIPS END UP IN STRANGE LOCATIONS FOR TRIMMING(POINT NEAR) F.l.l1.3.1 CHAIN SELECT USING TABLET. PRESELECT CHARACTERS-A,P,L-NOT RESET TO 'e' TRIM USING TABLET. PRESELECT CHARACTER-A, P, L-DO NOT GET RESET TO 'C' ATTENTION INDICATORS DISAPPEAR BEFORE OPERATION IS COMPLETED. ATTENTION MARKERS ARE NOT DROPPED WHEN SELECTION WAS CANCELED. STRING MADE FROM TRANSLATED ENTITIES SCREWS UP REION SELECT DELETABLE STATUS CHANGED INCORRECTLY REPAINT REQUIRED TO SELECT ENTITIES. ICEM DDN EXCLUDES THE OP-COMPLETE ] IN THE TABLET STRING ENTITY FLAG SHOWN II ODD LOCATION WHEN BLANKING CAN NOT SELECT GEOMETRY FOR ANY OPERATION ENTITY SELECTION IN VIEWS OTHER THAN THE WORKING VIEW CHAIN SELECT OF LINES AND AN ARC RESULTS IN ERROR--SEE DAYFILE DELETE BY LEVEL RANGE DELETES WHOLE PART (1.7)MODIFY LEVEL/PEN PRODUCES UNDESIRABLE RESULTS (17.13) 3-AXIS FLANGE IS GENERATING INCORRECT TOOL PATHS (17.12) SURFACING WITH MULTIPLE ISLANDS FAILS THE SPIKE IS BACK ON ROCKY FLAT LATHE PATH P308. (17.11) BAD POINTER IN DISPLAY AND EDIT. (8.6.14) RETRIEVE ZOOM SCALE DOES NOT WORK PROPERLY (8.3.1.1) DISPLAY SINGLE VIEW AT LAST SCALE USED RESCALE ON NOTE FAILS (4114). (MANUAL)DESCRIPTION NON STANDARD AND CONFUSING IN 8.6.15 CHANGE PAGE. MANUAL DOES NOT SPECIFY DEFAULT WORK VIEW (8.6.11)AUTO MAX/MIN SETS SCALE TOO LARGE IF DEFINE AXIS (10.16) (8.6.11) VIEW NOT CENTERED ON AUTO MAX-MIN OF PART A-IO C-,' I r- , ~j! PRIORITY CODE: C=CRITICAL U=URGENT S=SERIOUS McMINOR D=DEFERRED NUMBER AD20662 AD21107 AD21252 AD21293 AD21335 AD21337 AD21357 AD22060 AD22064 AD22206 OAD22213 AD22272 AD22273 57R056 57R082 57R163 57R040 57R184 57R148 57R183 57R156 57R158 57RI05 57R154 57R164 57R052 57R071 57R176 57R178 57R179 57R180 57R170 57R016 57R173 57R130 57R128 ('" 57R142 ~) 57R136 • 57R167 PRIORITY STATUS: C=CURRENT IcINTERNAL PRI C I PROBLEM ABSTRACT S S UU UU UU CC CC CC CC S S CC UU UU UU UU MM MM S S S S UU MM S S S S UU MM MM MM MM S S S S S S S S UU S S S S MM MM MM MM S S (RESCALE) DOES NOT WORK CORRECTLY FOR METRIC PART. VIEW NUMBERING DURING DEFINITION OF AN AUXILIARY VIEW F.8.9. ZOOM AUTO MAX/MIN DOES NOT WORK IF AN INFINITE LINE IS PRESENT. VIEW LAYOUT- WHEN CHOOSE OPTION TO RESIZE INTO NEW WINDOW PROBLEM. LOSS OF SCALE DURING LAYOUT CONSTRUCTION. VIEW ALIGNMENT IN A LAYOUT. VIEW MATRICES ARE NOT CHECKED SUFFICIENTLY. DISPLAY PREVIOUS LAYOUT DIAGONAL SCREEN POSITION DOES NOT WORK AFTER CREATING A LAYOUT ZOOM DISTORTS LAYOUT FRAMES SCALE TO PART SCALE (F.8.7.11) UNABLE TO FORMAT A SINGLE VIEW. 3-SURFACE PROFILE TOOL AXIS PARALLEL TO DS GIVES BAD RESULTS. THREE-SURFACE PROFILE CREATES TIME LIMIT PROBLEMS. PART MERGE DOES NOT CONVERT ENGLISH TO METRIC .UNITS ARROW ON A RADIUS DIMENSION DISPLAYS ICORRECTLY ON TOO CLOSE LEADERS LABEL USING SLOPE METHOD DOES NOT ALWAYS POINT TO THE ENTITY SECTION LINING DOES NOT APPEAR IN ALL VIEWS AS IT SHOULD DATUM TARGET USES A DIAMETER AS THOUGH IT IS A RADIUS SECTION LINING BREAKS IF TWO ENTITIES ARE SELECTED IN A ROW ARC THROUGH 3 POINTS CREATES LINE WITHOUT WARNING USER VERTICAL LDIMEN DIMENSION LINES POINT SET CURVE MACCRV/INTOF ••• EDGE WORKS INCORRECTLY 4114 W/ADM-3A TWO LINE DIALOG DOES NOT SCROLL TEK 4105 DOES NOT RUN TEST SCRIPT WELL IF -1 IS ENTERED FOR DEPTH, MESSAGE DISPLAYED IS MISLEADING ] AT ACCEPT THIS TOOL? TAKES USER TO OPERATION PROMPT [ AT ENDING SEQUENCE DOES NOT TAKE USER TO PREVIOUS MENU ] FOR DEPTH INPUT SENDS USER TO NC MAIN MENU FOR LATHE DRILL FACE THREAD FOR LATHE DOES NOT WORK WELL FOR LONG LINE MAJOR DIAMETER CAN NOT BE MODIFIED FOR A LINE PASSING THROUGH ORIGIN CYCLE DOES FUNCTION WITH INSERTED INFORMATION N/C D&E IS NOT PROCEEDING 'TO THE LAST LINE PROPERLY GODLTA INSERT DOES NOT CREATE TOOL MOTION ALONG TOOL AXIS OP REJECT FROM 'ENTER DIRECTION' DOES NOT CLEAR ENTITY ATTENTION A DISALLOWED CURVE CAN BE SELECTED WITH SEQ. NO./PTR/NAME OP REJECT IS NOT PROCESSED CORRECTLY IN A SINGLE SELECT SCREEN SELECT FOR SURFACE PATHS CAN BE SELECTED WITH A CR BLANKING WITH DISALLOWED CURVES ALSO BLANKS THE CURVES A-II c _.......-- .. - - - ......•._. ·0 --~ APPENDIX B RESOLVED PROGRAMMING SYSTEM ERRORS (PSRs) This section contains a list of system problems existing under previous versions which were resolved in ICEM DON Vl.57. PRIORITY CODE: C=CRITICAL U=URGENT S=SERIOUS M=MINOR PSR NO. PRIORITY PROBLEM ABSTRACT I~------------------------------------------------------------------------------------ AD22328 AD2A593 AD2A623 AD21951 AD22353 AD22357 AD22358 AD21182 AD21345 AD22323 AD2A622 AD2A625 AD22087 AD22299 AD22359 AD22362 AD2A591 AD2A619 AD2A620 AD2A641 AD2A651 AD20774 AD21020 AD22033 C C C C C C C U U 'U U·· U U U U U S S S S S S S S DECIMAL PLACES IN DIMENSIONING METRIC PART EXECUTE A GRAPL PROGRAM WITH ATTRIBUTES EXITS TO O.S. ENTITY VANISHES IF YOU ] AT DETAIL NO BUT ENTER SHEET NO PATTERN CREATION SHOULD BE ABLE TO USE IMPLICIT POINT CHAIN SELECT DOES NOT WORK FOR SMALL ENTITIES 1.53 PROBLEMS EXIST WITH CHAIN SELECT IN METRIC UNITS 1.53 CROSSHATCHING TEXT MOVES INCORRECTLY WHEN TOLERANCE IS ADDED SYSTEM REL/REV NUMBER (1. 7) ENTITIES GO TO CURRENT LEVEL OR PEN NUMBER CAN NOT REGION SELECT NESTED GROUPS DELETING NESTED GROUPS DOES NOT WORK CORRECTLY LATHE THREADING (16.13.4)MODE ERROR WHEN ADDING TOLERANCE TO DRAWING 1.53 MODIFYING PEN AND NOT LEVELS IN MULTI-PICK PROBLS 1.53 IMPLICIT POINTS PROBLEMS V.A.E. ERROR WHEN MORE THAN 509 POINTS ENTERED CAN CNTL-D TO DELETE A DATUM TARGET MODIFY DECIMAL PLACES ERRORS ON FRACTIONAL DIMENSIONS SECTION LINING VISIBILITY MODAL HAS NO EFFECT ON SECTIONING (15.2.12.1.1)LINE PICK POSITION UNUSED IN CONE CREATION (16.3) CROSSHATCHING SHOULD DISPLAY IN VIEW OF DEF (16.13.5) MODIFY TEXT DISPLAY VALUES (16.13.1)NEW ORIGIN GIVES INCORRECT WITNESS LINES WITH ANGLE B-1 .,------_..- .... ,. - - _ . , .. ~~ ".- ..._._ .. _--_ .. "."" ,---- PRIORITY CODE: C=CRITICAL U=URGENT S=SERIOUS M=MINOR PSR NO. PRIORITY AD22169 AD22219 AD22032 AD2A595 AD2A596 AD2A644 AD2A659 AD22285 AD22330 AD22284 AD22285 AD2A607 AD2A667 AD21492 AD22354 AD22151 AD22211 S S S S S S S >S S S S M M M M M M r PROBLEM ABSTRACT MODIFY BALLOON ALTERS TEXT TO CURRENT LEVEL AND PEN TEXT FOR GEOMETRIC SYMBOLS STAY AT ZERO DEPTH. (16. 11) LABEL-ARROWHEAD NOT ALWAYS PLACED AT SELECTED PT. ERROR IN NAMING OF N/C TOOL GPL INTOF RETURNS PT OF INTERSECTION BETWEEN TWO LINES EXTRA ITEMS APPEAR IN MOVE WINDOW MENU UNDER VIEW LAYT (6.1.10) IPARTD RETRIEVE LOSES SELECTIVE VIEW BLANK 10 ENTITIES ARE NOT SELECTABLE FROM VERY SMALL ZOOM AREAS (16.13.14.2) CHANGING RADIUS CHANGES ORIGIN OF WORDING (2.11) DOES NOT RECOVER FROM A ZOOM ON A VERY SMALL AA . ENTITIES ARE NOT SELECTABLE FROM VERY SMALL ZOOM AREAS R AT INDICATE CENTER PROMPT IN FILLET RETURNS WRONG VE REDUNDANT PARAMETER SPECIFICATION NOT HANDLED PROPERLY TRANSLATE BASE POSITION DOES NOT ALLOW IMPLICIT POINT (16.1.16) DRAFTING MODALS SAY DIAMETER ON EVEN WHEN OF GEOMETR Y EXI STS A'i -0.0000 WHICH CAUSES CONFUS ION OPTIM CAN PRODUCE INEFFICIENT PLOT FILES B-2 . ., ; o CONTROL DATA CORPORATION L!CEM Facilities 1 Version 1.1 Operating System Level: NOS 2.3 Level 617 Date 12/14/84 INSTALLATION INSTRUCTIONS DISCLAIMER o NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Control Data Corporation gives the user permission to reproduce this document. SMD130753 o .~ c c' ----_. __.. _- .. _._--_.-....._------_ .• _- - _..•. __ ._--. _._---- U \ 1 CONTROL DATA CORPORATION ICEM Facilities Version 1.1 INSTALLATION INSTRUCTIONS NOS 2.3 Level 617 12/14/84 RELEASE DESCRIPTION ICEM Facilities Version 1.1 runs under the CDC® Network Operating System (NOS) Version 2 and the CDC Interactive Facility (IAF) Communications Subsystem. ICEM Facilities is· designed to increase the drawing productivity and enable the automatic generation of reports for facilities building managers and plant engineers. ICEM Facilities requires ICEM Design/Drafting Vl.53. The operation of ICEM Facilities under NOS 2 requires the installation of the CDC Network Access Method (NAM), IAF and the associated products. C) HARDWARE CONFIGURATION The minimum hardware configuration required for NOS 2 and IAF is required to support ICEM Facilities Version 1.1. RELEASE MATERIALS The ICEM Facilities release files reside on the tape with a VSN of REL37A. This tape has the following characteristics: 9-track with either 800 or 1600 CPI binary recording mode, FACILITIESII as the file ID in the HDRI label, and 28 files. File 1 INSTALL Installation procedure file. File 2 FACINI Script file that defines tablet file FACTFIL. o - - - - - - _ .. -"--"-"-'-'-"." ... _------ c c c · ......... --.----~.-.-.-.- ---- •..- . - ... -------- 0 CONTROL DATA CORPORATION ICEM Facilities Version 1.1 INSTALLATION INSTRUCTIONS NOS 2.3 Level 617 0 o 2 12/14/84 File 3 FACIN2 Script file that defines tablet file FACTFIL. File 4 FACIN3 Script file that defines tablet file FACTFIL. File 5 FACIN4 Script file that defines tablet file FACTFIL. File 6 FACIN5 Script file that defines tablet file FACTFIL. File 7 FACIN6 Script file that defines tablet file FACTFIL. File 8 FACTFIL· Facilities tablet file. File 9 TABLET TAPE3 drawing file with physical tablet overlays. File 10 FACMSTR t Facilities MSTRING file. File 11 FACPATI ' Facilities global pattern file. File 12 FACPAT2." Facilities global pattern file. File 13 FACGRAI GRAPL programs (Source). File 14 AUXGRAI Auxiliary GRAPL programs (Source). File 15 FACGUTF File 16 FACTP3 TAPE 3 drawing file wi th example layouts. File 17 EXAMPLE Script file for example layout. .s> GRAPL programs (Object). c o CONTROL DATA CORPORATION ICEM Facilities Version 1.1 INSTALLATION INSTRUCTIONS NOS 2.3 Level 617 0 3 12/14/84 File 18 ICEMFAC Procedure file for ICEM Facilities. File 19 DEV Development utility procedure file loading a trace to draw a tablet overlay. File 20 PROCFIL A utility procedure file with a number of procedures in it. File 21 REPORTS CCL procedure file to generate reports. File 22 HWDATA Haworth Bill of Materials data base. File 23 OFDATA Office furniture Bill of Materials data base. File 24 CEDATA Construction estimate data base. File 25 REPSRC Report generator source code. File 26 REPABS Report generator absolute binary. File 27 VERIFY Installation verification procedure file. File 28 VERIT Data for verification procedure. o .- ......................... _._ .. ----_._- - - - - - - - c C,\I _- .. _-------_..... .. _ - - - .._-----,,---_.,,- - ----. - - - - - .... .... o 4 12/14/84 CONTROL DATA CORPORATION ICEM Facilities Version 1.1 INSTALLATION INSTRUCTIONS NOS 2.3 Level 617 NOTES AND CAUTIONS All limitations applicable to NOS 2 and IAF also apply to ICEM Facilities. The installer must be sure that permanent files do not exist with the same names as the files generated in the installation procedure. The permanent files listed above will be generated. INSTALLATION PROCEDURE o The files which are part of the ICEM Facilities product are installed by executing the installation procedure which is file 1 of the ICEM Facilities tape, VSN=REL37A. The installation procedure must be run in·teractively. Enter the following commands: LABEL,FACTAPE,R,L=FACILITIES11,VSN=REL37A,F=I, D = l·RD\. (9-track, 800 cpi) PE • (9-track, 1600 cpi) COPYBF,FACTAPE, INSTALL. BEGIN"INSTALL. Successful installation will be indicated at the terminal by th:e message, "INSTALLATION COMPLETE". o - - - - - ......._----... _... _.................... -_.. - - - _... _.._... __ __ ... _ - - - - - - - - - - _ . -. . -_ ......... _ ...... _-- - - - - - ......... - ... ---- o CONTROL DATA CORPORATION ICEM Facilities Version 1.1 INSTALLATION INSTRUCTIONS NOS 2.3 Level 617 5 12/14/84 VERIFICATION PROCEDURE To verify the proper installation of ICEM Facilities complete the following steps. The verification procedure must be run interactively. NOTE This procedure was written assuming that ICEM Design/Drafting Version 1.53 is stored as a direct access file named ICEMDDN on user name APPLLIB or that ICEMDDN has been sysedited into the system. If this assumption is incorrect, the user must change lines 13 and 14 of file VERIFY to specify the file name and user name in use. o If the above changes are needed, lines 9 and 10 of procedure ICEMFAC and lines 8 and 9 of procedure EXTRACE both on file ICEMFAC must also be changed. Step 1. Log onto a graphics terminal supported by ICEM Design/Drafting. Step 2. Enter: BEGIN"VERIFY ICEM Facilities will retrieve certain files from your permanent catalog, and prompt the user with the prompt shown in Figure 1 to allow the user to enter ICEM Design/Drafting. o ------------ ------_... _... _----_ .... -._-_._----------_. - - - - - - - - - - _ . _ -.... _--_. CI C) 6 CONTROL DATA CORPORATION ICEM Facilities Version 1.1 INSTALLATION INSTRUCTIONS NOS 2.3 Level 617 12/14/84 1~ Step 3. Answer prompts shown in Figure Step 4. After ICEM Design/Drafting places the user at the main menu, enter the following ICEM Design/Drafting command string. F.1.17.4.IT o Step 5. Compare the display with Figure 2 to verify that the layout is the same. Step 6. Enter: Step 7. ICEM Facilities will complete ICEM Design/Drafting and generate an office Bill of Materials. A carriage return. Compare the report with Figure 3 to verify that the report is the same. NOTE: Depending on the terminal used, the report may be written over the verification figure. Verification of ICEM Facilities will then be complete. o - - - - - - - - - - - - - - - - - - _ . _ .._- .. _._ ... _ ...... - - - - - - - ' - - - - - - - - - - - - - - - c o o CONTROL DATA CORPORATION ICEM Facilities Version 1.1 INSTALLATION INSTRUCTIONS NOS 2.3 Level 617 7 12/14/84 IECIN"UERIFY OtTER lAUD RATE. g ICEftDDt4 UERSIOH Rl.S3. COPYIU GMT PlAHUFACTOR ING AriD COrtStJL TlNG SERVICES, INC. ID78 COPVRICHT CONTROL DATA CORPORATION 1~78, .ung, 'lNG, IgBl, IgS2, IDa], lSJa.. UE~£ TO ICE"DDH GRAPtilCS TERftlHAL TYPE TEKTRONIX TEKTRONIX TEt-.iROtUX ... TEKTRONIX 1. 4814 2. ... 16 S. TE~iROHIX ~10g 3. 41tS 4187 I. TEKTRONIX 4113 1. TEKTRONIX 411" I. TE~iROHIX ~llS g. CDC UIKIHC 721 1•• CDC 1ST III 11. CDC lEY 7DO UITH TElCO. o 1 ftENU AREA 1. CRAPHICS TER"IttilL I. CDC 722/752 3. ADtt-3A 4. ALPHA-3 I. REF'RESH BUFFER •• INTERACTIVE IUFFER 1 TAIUT 1. ON I. 2 OFF LOCAL CHARACTER SET AND GRID 1. OH 8. 2 OFF Figure 1. Initialization Prompts o .._..__ ." .....""."" .. -._. __ ... _._--- --------------- c o CONTROL DATA CORPORATION ICEM Facilities Version 1.1 INSTALLATION INSTRUCTIONS NOS 2.3 Level 617 r 8 12/14/84 I ~ ~ 0" -- -i I- rr Figure 2. o ._-------_.__ ._--_ .. _ - - - - - Verification Figure c o CONTROL DATA CORPORATION ICEM Facilities Version 1.1 INSTALLATION INSTRUCTIONS NOS 2.3 Level 617 9 12/14/84 REPORT 1 OFFICE IIlL OF "ATERI~lS 2 ~WOATH IILl OF nATERIALS 3 NEW COHSTRUCTIOtt COST ESTIMTES .. TERfU"ATE ------THIS REPORT RESIDES ON lOCAL FILE REftE"BER TO ~UE IT OFBILL-------- OFFICE IILl OF P.ART HArtE I "ATERJ~lS UERIFV __mIME tWtE . DESCRIPTION .auinu CHAIR.SVMOL DESK .....72.HC U'''"U"UI CHAIR STD. DESK ....)(72 QTV ,u COllff~ 1 1 UHIT COST un 115.75 377.55 TOT~L o REPORT 1 OFFICE IILL OF "ATERIALS e HAYORTH IILL OF "ATERI~lS 3 HEY COrtSTRUCTIOtt COST ESTIMTES .. TERftIHATE CORRECT IHSTALLATIOH HAS lEEN VERIFIED ,REVERT. . Figure 3. o """Ia* 175.75 377.55 S53.3e ----THIS REPORT RESIDES Ott LOCAL rILE OFIILL-----REftE"BER TO SAVE IT 2916c EXTENDED COST Verification Report c SOFTWARE RELEASE BULLETIN ICEM Facilities 1.1 (NOS 2.3 LV 617) o SMD130772 . - - -. . . ---------- o NOTES AND CAUTIONS l> 1. Procedure files ICEMFAC and VERIFY were written assuming that ICEM Design/Drafting version 1.53 is stored as a direct access file named ICEMDDN on user name APPLLIB or that ICEMDDN has been sysedited into the system. If this assumption is incorrect, you must change three procedures to specify the file name and user name in use. Change lines 9 and 10 of procedure ICEMFAC in file ICEMFAC, lines 8 and 9 of procedure EXTRACE in file ICEMFAC and lines 13 and 14 in procedure VERIFY in file VERIFY. (Notes 2, 3 and 4 refer only to the drawings of the tablet overlays that are provided on permanent file (TABLET). o 2. The drawing of the HW PEN DRAWER (Rows 1 & 2, Col. 15 on overlay HAWl) is incorrect. The origin point of the pattern is at the center of the bottom line, not at the center of the rectangle as shown. The pattern name is DS3 in file FACPATI. 3. The dimensions shown for UNIVERSAL DESK (Row 6, Cols. 11 & 12 on overlay ROFFl) are incorrect. They are 30 x 60 not 36 x 60 as shown. The pattern names are DK3060 and DK3060C in file FACPAT2. 4. The drawing of overlay LAYI is missing text in one square. Row 5, Col. 4 should contain the text "DELTA S.P." 3070c -1- ', .... / CI G SOFTWARE RELEASE BULLETIN ICEM ENGINEERING DATA LIBRARY EDL VERSION 1.2 RELEASE NOS 2 LEVEL 617A SMD130799 ._-- ..... _._ ...................._ - - - - ...- - - - .. I o ICEM EDL Vl.2 Thi s rel ease is a maj or rewri te of the Engi neeri ng Data Library to correct outstanding PSR's and to provide the following enhancements: 1. User Interface o Reorganization of EDL menu tree. o Command interface. 2. Data Management o Management of multiple user defined attributes for a desi9n. o Design sel ection description fields. o A restructured set of standard reports. o Standard procedure to associate any file to a design. o Format revision of design retrieval lists. o Standardized sel ection released designs. o Use of IMF 2.1 (Information Management Facil ity) providing concurrency and database backup recovery. o Rel ease mechani sm requirements. o Ability to grant permission to a design by group. o More power to clean up EDL database. based on the of working, tai 1 orabl e to 3. Applications Supported o ICEM Design/Drafting/NC o ICEM Solid Modeler o UNIPLOT o RECLAIM user o -1-' . 1 abel ed pending site or specific ~\ o 0 Text Editor (fSE or XEDIT) 0 IGES 0 UNISTRUC 11 0 ICEM Schematics 0 ICEM TEKROUTE 0 PATRAN-G 4. Application lnterface Enhancements o Automatically attach defaul t fi 1 es for user when entering a new application. o A well defi ned and standard set of retrieval and update routines. o A common interface for transfers and translations, including IGES and site defined translators. 5. 'Customization o Creation of customized reports by the DBA using Query Update. o Util ities allowing other appl ications to invoke EDL Functions. o Abi 1 ity to specify a chain of mixed procedures and/or internal program segments for execution. o Ability to call procedures with parameters. o Easier menu modification. o Easier migration of customized menus and messages between database versions. o More internal documentation including: Improved installation Guidelines for adding Guidelines for EDL access by other ICEM programs. guide other applications uti 1 ities, EDL database applications and customer o _ .......... ... _...... _-- I \ I, ' ....... , ",' c' NOTES AND CAUTIONS u - 1. On entering EDL, if the user's logged in NOS user number is di fferent than the NOS username in the EDL user profile, a warning message is displayed. Any files created under this condition may not be accessib1 e to the user 1 ater un1 ess they are specifically permitted. 2. Updat; ng EDL for new fi 1 es requi res you to be logged on the NOS account where the file resides. EDL assumes that all new fi 1 es are pri vate fi 1 es. If the file is actually a NOS public file, use the EDL PERMIT function to change the EDL file category to PUBLIC. 3. To install data files on a system account such as APPLLIB or LIBRARY, where a SUI statement is used to access the account, use UPDATE EDL FOR ENGINEERING DATA to add the file information toEDL, then use CORRECT FILE INFORMATION to change ~he NOS username of the file to the right username. 4. An indirect -access permanent file named USER must exist on the user's NOS account if the user wishes to use Solid Modeler TRANSFER tasks. - The file USER contains the job card, user card, and accounting charge card image if needed. o 5. The DBA shou 1 d set up a di rect access fi 1 e named EDLRECL on the account where EDL is instal led and make it accessible in write mode to the users who will use the ARCHIVE/RECLAIM feature in EDL. Note that in previous versions of EDL, thi s fi 1 e was call ed RECLDB. Ei ther rename the 01 d rec1 aim database or change procedure RECL ;n E120PRC. 6. If two users attempt to update the same EDL record at nearly the same time, a concurrency conflict may occur for the second. An error message wi 11 be di sp1 ayed and EDL will return to the previous task menu. The user should re-obtain the data and try again. 7. If the user uses a Control T to abort EDL using IMF, occasionally the user job hangs and cannot be dropped. It may be necessary to do an override from the conso1 e to drop the job. 8. If the user changes his EDL password, he shou1 d immediately QUIT and reenter EDL before entering an application prog~am. o 9. The User's Guide and Data Base Administrator's Manuals w ill b e sup P 1 i e don mag net i c tap e _~ spa r t 0 f the released material •. Printed manuals will be available from LOS on March 29, 1985. c PSRls u The rewritten code in this release corrects the fol lowing PSRls. Ident ED1A008 ED10021 ED10036 E010039 £010045 ED10046 ED10048 ED10050 £010052 ED10061 () ED10062 E010063 ED10078 ED10079 ED10080 ED10081 ED10085 ED10087 ED10088 ED10090 o Description INSTALLATION PROCEDURE DEFINES FILES WITH INCORRECT PASSWORD WORKING COPY OF RELEASED DRAWING HAS STATUS RELEASED .• WASTED DISKSPACE,RELEASE PROCESS TIES UP TAPES3,REQUIRES A TAPE3 PER DRAWING WRONG HANDLING OF MODELS/DRAWINGS WITH SAME NAME ON DIFFERENT FILES. EDLPROC IS NOT DOCUMENTED WELL ENOUGH FOR ONSITE ANALYSTS DIRECTORY INFORMATION NOT ACCESSED PROPERLY BY EDL DATABASE REMOVE MODEL FUNCTION SHOULD LET THE USER CHOOSE TO REVIEW FIRST. MODEL NUMBER DESCRIPTION ONLY PROMPTS FOR UNIQUE NAMES SIMILAR PROBLE~l WITH CD2K INTERFACE REGARDING NA~1 I NG CON VEN TION S EDL DOES NOT ACCOMMODATE ICEM SOLID MODELER ELIMINATE COMMAND ED L CON FUSE SIC EMS 0 LID r~ 0DEL ER W0 RKSPA CE AND OBJECTS WITH MODELS. EDL IS INCONSISTENT WITH CD/2000,ICEM SOLID MODELER PROCEDURES. *DESTROYED EDL DATABASE AFTER EDL OR SYSTEMCRASH WITH NO POSSIBLE RECOVERY. *NO WAY OF CHANGING A PART NUMBER. *NO WAY OF DELETING RELEASED DRAWINGS. *DOES NOT ALLOW DRAWINGS OF THE SAME NAME. DESTROYED EDL DATABASE AFTER EDL OR SYSTEMCRASH WITH NO POSSIBLE RECOVERY ** MENU CONSTRUCTION PROBLEM ON NEW MENUS CONTAINING II/illS PERMIT INFORMATION IS LOST ON NOS WHEN A FILE IS OVERWRITTEN *** DRAWING REPORTS NEED COUNTERS TO SHOW IIREVIEW" STATUS. ED10091 ED10092 ED10094 ED10096 ED10098 ED10099 ED10101 EDL0102 ED10103 ED10104 ED10105 ED10107 ED10108 ED10109 ED10111 ED10112 ED10114 ED10115 -' C \ I ED10116 ED10117 ./ ED10118 ED10119 ED10121 ED10122 ED10123 ED10124 ED10125 ED10126 ED10127 ED10128 ED10130 *** DBA SHOULD NOT NEED DUPLICATE ENTRIES OF RELEASED FILES * * * REP 0 RTF 0 R~1 AT S H0 ULD BE CON SIS TEN T REGARDLESS OF ORIGIN OF ACCESS *** EDL REFERENCE MANUAL REVISION EDL 1.13 IMPOSES LIMITS ON FAMILY NUMBER W/OUT VALIDATING IT ON ENTRY AUTHORIZED REVIEWERS SHOULD BE ABLE TO LIST IIpENDING" DIRECTORIES. NEED IIMODIFIED II FIELD IN EDL DIRECTORIES. DUPLICATE DRAWING/SHEET ERROR EDLN300 MUST OCCUR IN OWNER'S DIRECTORY. REPORT OF PENDING RELEASE DRAWINGS NEEDED. *** REFER TO ANSWER TEXT ON ED10041 ON TERMINAL CHANGE IN EDL *** EDL DOES NOT ALLOW MULTIPLE IIGPARTS" AND 1IPATTERNII ACCESS LACK OF ABILITY TO HANDLE TABULATED DRAWINGS *UNABLE TO USE RELEASED DRAWING GEOMETRY. *DUAL REVISION CONTROL. *IN-PROCESS DRAWING SUPPORT. ARCHIVE RELEASED DRAWINGS. *PROBLEM WITH EDL RELEASE PROCESS. *AUTOMATIC UPDATING OF EDL BY ICEM MODELER EDL CHANGES MOD DATE FOR CD2000 FILE EVEN WHEN. USER FILES NO UPON EXIT EDL DBA DELETE MENU,-DOES NOT DELETE MENU EDL DBA MENU CONSTRUCTION, WAITS TO UPDATE MENUS EDL113 DOESN'T ALLOW USERS OTHER THAN EDLDBA TO ATTACH IT V1.13/CD2000 PROCEDURE HUNG WHEN CALLED W/L=O PARAMETER CANNOT LIST DRAWINGS IN PENDING RELEASE MODIFICATION OF DRAWING INFORMATION (INDEX CARD) IS UNCLEAR EDL- REQUEST ADDITIONAL DRAWING RETREVIAL KEYWORDS EDL - NEED CAPABILITY TO PUT SEVERAL DRAWINGS INTO PENDING RELEASE. EDL - TAPE3 LOCK-UP FOR PENDING RELEASE PARTS EDL - WANT EDL FILE CONTROL EXPANDED EDL - NEED ABILITY TO MODIFY DESCRIPTION KEYWORD CHANGING DESCRIPTION OF A RELEASED DRAWING TWO PEOPLE USING ONE EDL USERCODE CAN CAUSE LOSS OF DATA () -5- ,. "'" c (" "" .. ,. £D10132 u £010133 ED10134 ED10135 EDL REQUIRES A CARRIAGE RETURN TO COMPLETE THE RELEASE OF A DRAWING. CHANGING THE EDL INDEX CARD IS IMPOSSIBLE AFTER RELEASE. A DRAWING FILE WAS UNACCESSIBLE AFTER IAF LOST A USER. A NEED EXISTS TO BE ABLE TO EXIT IIACCESS CD/2000 fILES II C) -n '--, -6... _--_ _---_._ _-_ .. .. .• _- - - - - - - - - - - _.._------- ''''''-. ... - I • I i. 1 1985/12/31 CONTROL DATA CORPORATION ICEM ENGINEERING DATA LIBRARY /. 'Z. J Operating System Level: NOS 2 Level 642A Date: 12/31/85 INSTALLATION INSTRUCTIONS AND C) CUSTOMIZATION GUIDE DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Control Data Corporation reproduce this document. gives the user permission to SMD131013 -------------------- r-"\ ( ". I 1 1985/12/31 Table of Contents 1.0 1.1 1.2 1.3 1.4 ICEM EDL VERSION 1.2.3 RELEASE DESCRIPTION HARDWARE REQUIREMENTS DEPENDENCIES • • • • RELEASE MATERIALS • . • • 1-1 1-1 1-1 1-1 1-2 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.1 ESTABLISH NOS ACCOUNTS • . • • • • • . • 2.2 MINIMUM VALIDATIONS • • . • • • • • • • 2. 2 • 1 UN= IMF • • . • • • • • • • • . . . • 2.2.2 ALL OTHER USERS INCLUDING THE DATABASE ADMINISTRATOR 2.3 RUN THE INSTALLATION PROCEDURE • • . • • • • 2.4 EDIT THE EDL PROCEDURE FILES. • . . • . • • 2.5 ACTIVATE THE IMF2.1 SYSTEM CONTROL POINT. • • • . 2.6 INSTALLING EDL IN NON-CONCURRENT MODE • • • • 2.7 INSTALLATION VERIFICATION •••••• 2.8 UPGRADING EDL DATABASES • • • . • • • • • • 2.8.1 CONVERSION FROM EDL 1.1.3 •••• 2.8.2 CONVERSION FROM EDL 1.2.0 TO EDL 1.2.3 2.9 IMF DATABASE MAINTENANCE. 2.9.1 BACKUP AND RECOVERY . . • . 2.9.1.1 Backup Procedure . • • . • • • 2.9.1.2 Recovery Procedure • • • • • • 2.9.2 RUNNING WITHOUT JOURNAL LOGGING 2.10 IMF TUNING CONSIDERATIONS. 2.11 EDL AUTOSTART FOR. USERS • • • • • • 2. 12 PASSWORD MASKING • • • • • • . • • • 2.13 USING QUERY UPDATE • • . • • • • • • 2.14 USING ICEM DDN VERSION 1.53 OR 1.57 • o 2-1 2-1 2-1 2-1 2-2 2-3 2-4 2-4 2-5 2-6 2-11 2-12 2-13 2-14 2-14 2-14 2-15 2-15 2-16 2-16 2-16 2-17 2-18 3.0 3.1 3.2 3.3 CUSTOMIZATION • • • . • • DISCLAIMER •• .. • • • • • . INTRODUCTION • •.•. UPGRADING FROM EDL 1.2.0 TO EDL 1.2.3 3-1 3-1 3-1 3-2 4.0 4.1 4.2 4.3 CUSTOMIZING EDL PROCEDURES. SETTING UP THE EDL PROCEDURE. ALTERNATE PROCEDURES • • • • • ADDING A DIRECTORY TO E123PRC 4-1 4-1 4-2 4-2 5.0 CUSTOMIZING THE MESSAGE AND TASK DATABASE •• 5.1 CHANGING DIALOG TEXT. • • • • ••• 5.1.1 TASK MANAGEMENT • • . • 5.1.2 TASK INFORMATION HEADER 5.1.3 TASK MENUS AND COMMANDS 5.1.4 TASK SECURITY CATEGORIES 5.1.5 TASK MENU TREES 5.1.6 TASK PROCESSES • • • . 5.1.7 TASK PARAMETER VALUES • • • • •... __ _.__.. - - - - _.•.•._ _-_._,---"._.. _,. ... .. -". 5-1 5-1 5-2 5-2 5-2 5-2 5-3 5-3 5-4 - - - - - - - - - - - - - _.._-" .... '-_..... ..,_ ... 2 1985/12/31 5.2 EDL GLOBAL VARIABLES • • • • • 5.3 MESSAGE SUBSTITUTION • • • • . 5.4 MESSAGE AND TASK DATABASE REPORTS 5.4.1 TASK REPORT ••• 5.4.2 TASK MENU REPORT •• 5.4.3 PROMPT REPORT 5.4.4 OPTION MENU REPORT • 5.5 ORGANIZING EDL MDB TRANSACTIONS 5-4 5-6 5-7 5-7 5-7 5-8 5-8 5-8 6.0 CUSTOMIZING THE ENGINEERING DATA DATABASE • • • • 6.1 ENGINEERING CATEGORIES AND STANDARD ATTRIBUTES. 6.2 ADDING A NEW APPLICATION • • • • • • • • • • • 6.2.1 APPLICATION HEADER • • . • • . • • • • • • 6.2.2 NEW FILE TYPE AND DATA TYPE DEFINITIONS • • • • 6.3 TERMINAL CONFIGURATION •• 6.4 LOGGING PATTERNS INTO EDL 6-1 6-1 6-2 6-3 6-3 6-3 6-4 7.0 ADDING FORTRAN CODE TO EDL . • • • • • • • • • 7.1 DATABASE OPERATIONS 7.1.1 READING THE DATABASE • • • • • 7.1.2 STORING NEW RECORDS 7.1.3 DELETING RECORDS. 7.1.4 MODIFYING RECORDS 7.2 PROGRAMMING GUIDELINES. 7-1 7-1 7-1 7-2 7-2 7-2 7-2 8.0 ADDING TASKS TO EDL 8-1 9.0 SITE DEFINED RETRIEVALS 9.1 ROUTINE EXTSIT • • • . • • 9.1.1 EXPLANATION OF EXTSIT 9.1.2. EXPLANATION OF EXFSIT 9.2 THE MENU DATABASE TRANSACTION FILE 9.3 LOADING ROUTINES INTO EDL • • • • 9.4 UPDATE EDL FOR THE MENU DATABASE TRANSACTION FILE 10.0 10.1 10.2 10.3 INTERFACING APPLICATIONS ~ • EDL LOG FILE • • • • . • • • • . • • • EEEDLFN FILE . • • • • • • • •. • ••• RETRIEVAL TASKS • . • • • . • • . (--..... "-- .. " 9-1 9-1 9-7 9-9 9-10 9-11 9-12 10-1 10-1 10-1 10-2 11.0 CUSTOMIZING THE PLOTTING INTERFACE 11-1 12.0 PROGRAM AND USER INTERFACE 12.1 INFORMATION BASE (IB) ROUTINES 12.2 EDL UTILITY ROUTINES • • • • • • 12-1 12-1 12-2 13.0 UPDATE THE MESSAGE AND TASK DATABASE 13.1 INTRODUCTION • • • • • • • • 13.2 APPLYING TRANSACTION DATA •• 13.3 TRANSACTION FILE FORMAT ••• 13.3.1 MI (MESSAGE INFORMATION) 13.3.2 MH (MESSAGE HELP) • • • • 13.3.3 OM (OPTION MENU LINES) 13.3.4 OK (OPTION KEYWORDS) • • • • 13-1 13-1 13-1 13-2 13-3 13-3 13-3 13-4 c\ C) 3 1985/12/31 ·· · 13.3.5 OV (OPTION VALUES) 13.3.6 TI (TASK INFORMATION) 13.3.7 TC (TASK COMMANDS) 13.3.8 TM (TASK MENU LINES) 13.3.9 TP (TASK PROCESSES) 13.3.10 TV (TASK PARAMETER VALUES) ···· ··· ···· ···· ···· 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.1 SUMMARY OF CHANGES BETWEEN EDL 1.2.0 AND EDL 1.2.3 14.2 RECORDS USED TO CUSTOMIZE EDL • 14.2.1 AI APPLICATION INFORMATION 14.2.2 AC APPLICATION CONFIGURATION 14.2.3 ET ENGINEERING CATEGORIES • 14.2.4 EA ENGINEERING ATTRIBUTES 14.2.5 FT FILE TYPES • 14.2.6 AT APPLICATION DATA TYPE 14.2.7 TT TRANSFER AND TRANSLATION TASKS 14.2.8 RT RELEASE TRANSFERS 14.2.9 HI HOST INFORMATION . 14.2.10 CL COMMUNICATION· LINKS • 14.2.11 UM UNITS OF MEASURE CODES 14.3 RECORDS UPDATED BY EDL 14.3.1 UI USER INFORMATION. 14.3.2 UV USER VALIDATION 14.3.3 GI GROUP INFORMATION 14.3.4 GM GROUP MEMBERS 14.3.5 GS GROUP SECURITY AUTHORIZATION • 14.3.6 PI PART INFORMATION • 14.3.7 FM FAMILY INFORMATION. 14.3.8 PF PART FAMILY 14.3.9 VI VENDOR INFORMATION. 14.3.10 PV PART VENDORS 14.3.11 PR PART REVISION. 14.3.12 PS PART STRUCTURE 14.3.13 UC USER CONFIGURATION 14.3.14 DF DEFAULT FILES. 14.3.15 FI FILE INFORMATION 14.3.16 GP GROUP PERMITS. 14.3.17 UP USER PERMITS 14.3.18 FP FILE PERMITS · 14.3.19 PP PENDING PERMITS 14.3.20 DI DATA INFORMATION 14.3.21 DD DATA DESCRIPTOR 14.3.22 PD PARTS DATA 14.3.23 FD FAMILY DATA. 14.3.24 DR DATA REQUIRED . 14.3.25 DS DATA SOURCE • 14.3.26 RP RELEASE PROCEDURE • 14.3.27 RU RELEASERS • 14.3.28 RR REVIEW RESPONSIBILITY 14.3.29 RA RELEASE AUTHORIZATION 14.3.30 RS RELEASE SIGNATURE. 14.3.31 ME MESSAGES 14.3.32 MN MESSAGE INSTANCE ·· ········ ···· ····· ···· · · · ·· · ···· ···· ···· · 0 ···· ···· ···· ········· ···· · • . ······ ········ ······ ······ ·· ···· ···· ·· · ···· ··· ···· ····· ···· ···· · 0 ···· ···· · ······ ······· ···· ····· · · · · .···· 13-4 13-5 13-5 13-6 13-6 13-7 14-1 14-1 14-2 14-2 14-2 14-3 14-3 14-4 14-5 14-5 14-6 14-6 14-7 14-7 14-8 14-8 14-9 14-9 14-10 14-11 14-:-11 14-11 14-12 14-12 14-13 14-13 14-14 14-15 14-15 14-16 14-17 14-17 14-18 14-19 14-19 14-20 14-21 14-21 14-22 14-23 14-23 14-24 14-24 14-25 14-26 14-26 14-27 4" 1985/12/31 14.3.33 MN MESSAGE LINES • • • • • 15.0 EDL STANDARD OVERLAY CAPSULES • 15.1 GENERIC APPLICATION INTERFACE. 15.2 SPECIFIC APPLICATION INTERFACE 15.3 RETRIEVE • • • • • • • • • 15.4 TRANSFER ENGINEERING DATA. 15.5 RELEASE PROCEDURE • • • • • • • • • • • • 15.5.1 SUBMIT 15 •5 • 2 ACCEP T • • • • 15.5.3 REVIEW ••• ' •• 15.5.4 FINALIZE • • • • • • • • 15.5.5 RELEASE A PART STRUCTURE 15.6 "FILE MANAGEMENT. 15. 7 UPDATE • • • • • • • • • • 15.8 USER PROFILE • • • • • • • 15.9 REPORTS • • • • • • • • • • 15.10 PART STRUCTURE MANAGEMENT • • • • 15.11 MISCELLANEOUS USER TASKS. 15.12 ADMINISTRATOR TASKS • • • • 15.13 RESERVED OVCAPS • • • • • • • • • • • • 16.0 CREATING A NETWORK IN EDL •. 16.1 DEFINE HOSTS • • • • • • 16.2 DEFINE COMMUNICATION LINKS 16.3 QU DIRECTIVES TO DEFINE A NETWORK 16.4 E123PRC MODIFICATIONS • • • • • • • 16.4.1 PROCEDURES GETMAS AND GETSUB 16.4.2 PROCEDURE EDL • • • 16.4.3 EDL_LOG F~LES • • • • 16.5 NETWORK INITIALIZATION • .'. • • 14-27 15-1 15-1 15-2 15-3 15-4 15-5 15-5 15-6 15-6 15-7 15-8 15-8 15-9 15-10 15-10 15-10 15-10 15-11 15-11 16-1 16-1 16-2 16-2 16-3 16-3 16-3 16-4 16-4 c 1-1 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 1.0 ICEM EDL VERSION 1.2.3 1.0 ICEM EDL VERSION 1.2.3 1.1 RELEASE DESCRIPTION. ICEM Engineering Data Library (EDL) is an application designed to provide a user-friendly interface to Control Data's CAD/CAM products and to manage the engineering data produced by these products. The EDL system runs under the CDC Network Operating System (NOS) Version 2, and the CDC Network Access Method (NAM) and CDC Interactive Facility (IAF) communications packages. Information Management Facility (IMF) interfaces to the EDL database. A run-time subset of IMF is included with EDL. 1.2 HARDWARE REQUIREMENTS EDL requires the m1n1mum hardware configuration for NOS 2 and NAM/IAF. The user station can be a graphic or alphanumeric termina~. EDL requires a field length of 155000 octal words. 1.3 DEPENDENCIES EDL interfaces to the following application packages. ICEM DDN Version ICEM Solid Modeler Unistruc II ICBM Schematics PATRAN-G IGES V2 UNIPLOT XEDIT 1.57 or 1.60 1.1 15AUG84 1.15 1.5 2.1 ..........-._._. . . ---------- 1-2 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 1.0 ICEM EDL VERSION 1.2.3 1.3 DEPENDENCIES Full Screen Editor Reclaim 1.4 RELEASE MATERIALS EDL resides on the tape VSN=REL76A. The tape characteristics are 9-track, .1600 cpi (D=PE). Tape format is internal (F=I) and labeled EDL123. The following files are found on the EDL release tape. File File File File File File 1 2 3 4 5 6 INSTALL E123PRC E123ABS E123BIN E123LIB E123IBL File 7 File 8 File 9 E123NBL E120CNV EDLCOM File File File File File File 10 11 12 13 14 15 E123MMB E123DMB E123MDB E123DDB EDLSRB EDLSCH File 16 EDLCMAN File 17 File 18 File 19 EDLLIST EDLUMAN EDLDMAN File File File File File IMF2LIBV IMF2QU J MCSIMF:2 IMF2STF v' IMF2SCP/ 20 21 22 23 24 File 25 File 26 p EDL Installation Procedure EDL Version 1.2.3 Procedure file EDL Absolute Program EDL Main Overlay R~locatable Program EDL Relocatable Subroutine Library EDL Relocatable Information Base Subroutine Library EDL Networking Subroutine Library Conversion Program EDL 1.1.3 to EDL 1.2.0 EDL Information Base Common Block Text File Message and Task Metabase Engineering Data Metabase Message and Task Database Engineering Data Database EDL 1.2.3 Software Release Bulletin EDL 1.2.3 External Schema Charts (DDN Drawing File) EDL Installation and Customization Manuals Default Database Load List EDL 1.2.3 User's Reference Manual EDL 1.2.3 Database Administrator's Manual IMF Version 2.1 Enforcer Library Query Update with IMF 2.1 Interface Start-up Procedure for IMF2SCP IMF 2.1 System Tuning File IMF 2.1 System Control Point Absolute Program CLGABS Program to Associate Log File to Database IMF2RECI Offline Recovery Utility 1-3 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 1.0 ICEM EDL VERSION 1.2.3 1.4 RELEASE MATERIALS File 27 WMTUN52 File 28 File 29 IMF2LDU MOTHERN Program to Change Metabase Username for a Database IMF 2.1 Load/Unload/Validate Utility Metabase for Metabases, needed by IMF2LDU o - - _•.•.. __._ .•.._._.... _.. __ ._..._----_..__._--_.._. _..... _._. __ _._._ .. ......... __... _._._- , ........,-.,~..... 2-1 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.1 ESTABLISH NOS ACCOUNTS Establish a NOS account for the EDL programs, procedures, and data base files. This account may have any username and password. Establish a NOS account with username IMF on which the Information Management Facility will reside and run. This username must have the name IMF, and must have special validations. It must be able to run a system control point job, communicate with user control points, create unlimited dayfile messages, unlimited CP time, unlimited MS, create direct and indirect files, etc. All usernames from which EDL will be run must have validation to communicate to system control point jobs. Otherwise, they will be automatically logged off when they try to execute EDL. 2.2 MINIMUM VALIDATIONS 2.2.1 UN=IMF o AP=MCS AP=RBF Message Control System. Remote Batch Facility. AW=CLPF AW=CSPF AW=CCNR AW=CUCP Create direct access files. Create indirect access files. Enter system'without charge number. Access system control point facility. ,._,,- ..,_.,_... _-- ..__..._.,-.,_._-_._.......... ,.,_ .. _,,_ .. ,-,- _.,.,--",..- - - - - - - - _._,_._,.",_ .... .. - - - , ................... .. If· ~~' 2-2 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.2.1 UN=IMF CC=77B CM=77B CS=7 DB=7 DF=77B DS=7 FC=7 FS=7 MS=77B PW=pw Max number of batch commands. Max central memory space used. Cumulative size of all indirect access files. Max number of executing jobs and queue files. Max number of MESSAGE requests to system and job dayfile. File size allowed for an individual direct access permanent file. File count. File size allowed for an individual indirect access permanent file. Max number of additional mass storage PRU's the user is allowed to allocate to a job. Password for both batch and interactive 2.2.2 ALL OTHER USERS INCLUDING THE DATABASE ADMINISTRATOR AP=IAF AP=RBF Interactive Facility Remote Batch Facility AW=CLPF AW=CSPF AW=CCNR AW=CAND AW=CUCP Create direct access files. Create indirect access files. Enter system without charge number. (note 1) Request nonallocatable devices (magnetic uni ts) • (note 2) Access system control point facility. CC=77B CM=77B CS=7 Max number of batch commands. (note 2) Max central memory space used. (note 2) Cumulative size of all indirect access files. tape (note 2) DB=7 Max number of executing jobs and queue files. (note 2) DF=77B DS=7 FC=7 FS=7 MS=77B PW=pw Max number of MESSAGE requests to system and job dayfile. (note 2) File size allowed for an individual direct access permanent file. (note 2) File count. (note 2) File size allowed for an individual indirect access permanent file. (note 2) Max number of additional mass storage PRU's the user is allowed to allocate to a job.' (note 2) Password for both batch and interactive 2-3 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.2.2 ALL OTHER USERS INCLUDING THE DATABASE ADMINISTRATOR note 1 - The EDL installation procedure does not enter a CHARGE statement after the secondary USER commands when the procedure moves to UN=IMF and back to the D~Ats account. note 2 - Required for Database other users. administrator, may vary for the following 2.3 RUN THE INSTALLATION PROCEDURE Run the tape control cards. installation procedure using LABEL,TAPE,VSN=REL76A,F=I,D=PE,L=EDL123. COPYBF,TAPE,INSTALL. BEGIN,INSTALL,INSTALL. The installation procedure password of the EDL account, IMF. will prompt for the us'ername and and the password of username If you already have the IMF2.1 files on username IMF and you do not wish to re-install it, answer NONE when prompted for the password of username IMF. For sites currently using EDL 1.2.0, It is recommended that the IMF files be reinstalled, since the IMF released with EDL 1.2.3 has been updated. It is also possible to install the IMF files without installing the EDL files. Be sure that you are logged into the UN=IMF account and type the following commands. LABEL,TAPE,VSN=REL76A,F=I,D=PE,L=EDL123. COPYBF,TAPE,INSTALL. BEGIN,INSTIMF,INSTALL. More information about starting and tuning IMF can be 'found in following sections. o 2-4 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.4 EDIT THE EDL PROCEDURE FILES. 2.4 EDIT THE EDL PROCEDURE FILES. The installation procedure creates the startup file EDL. It is a single CCL proc which gets procedure file E123PRC from the NOS username where EDL is installed and passes that username as the value of the AUN parameter on the BEGIN statement for EDL. No changes to the file EDL should be necessary. The proc header of procedure EDL in E123PRC should be. editedJf~ to change the default value of t~e. alternate username parameter (AUN) to the username on which the EDL programs and databases were installed. This will ensure that EDL will run correctly even when started directly from E123PRC instead of from file EDL. The procedures in E123PRC should be checked to ensure that the correct versions of the application programs are obtained from the correct usernames. The standard procedure file assumes that all application programs and procedures are' on UN=APPLLIB. If this is not the case at your site, E123PRC should be changed. If an application such as ICEM DDN is sysedited into your system so that it can be used as a system command, simply remove the attach statements and the statement that checks to see if the application program has been assigned. 2.5 ACTIVATE THE IMF2.1 SYSTEM CONTROL POINT. Edit file MCSIMF2/UN=IMF to change the commented out USER statement to a valid USER statement for the IMF account. Move this small procedure file to, username SYSTEMX (UI=377777B). Note that the user statement, in MCSIMF2 is mandatory and cannot be replaced by a SUI statement. The IMF system control point program, IMFSCP, is started like all subsystems by a DSD entry, starting the execution of the procedure file saved under username SYSTEMX. That is, from the console, MCSIMF2. e ..// l' 2-5 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.5 ACTIVATE THE IMF2.1 SYSTEM CONTROL POINT. IMF2SCP can run at any control point. To force it to run at a specific control point, use the following CHR/DSD entry before the MCSIMF2 command. ENABLE, MCS , cptl. To avoid changes to the operating system, the EDL version of IMF2SCP uses the same system identification as the Message Control System, and cannot run when the Message Control System is active. IMF2SCP is idled through the DSD entry IDLE,MCS. When idled-down, IMF2SCP will complete all processing needed to keep the databases in a consistent state. Idle-down can thus be done without damaging the databases, even if there are users active. 2.6 INSTALLING EDL IN NON-CONCURRENT MODE If you do not need to allow more than one ICEM user at the same time using the same EDL database , you can install EDL so that it will run in mono-user mode without the system control point job being active. To do this, follow the following steps. 1. Define an empty direct access file named EDLLOCK on the username where the EDL Engineering Database is installed. This file should be Public in Write mode. EDL will use this file to ensure that only one person tries to use EDL at a time. Otherwise, EDL may abort when the database is busy. DEFINE,EDLLOCK/CT=PU,M=W. 2. Edit Procedure EDL in E123PRC to change the statement $IF,$MONO$=$TRUE$,Ll. to $IF,$MONO$=$MONO$,Ll. and put the AC=l paramete~ on the E123ABS statement. o 2-6 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION 2.7 INSTALLATION VERIFICATION To. verify the installation of EDL, do the following steps: Log in to the NOS system using the username established ·for the database administrator. Initiate EDL by entering: -,EDL The terminal session below shows how to update the DBA's user profile. User responses are indicated by lower case letters. 85/09/12. ICEM ENGINEERING DATA LIBRARY VERSION 1.2.3 COPYRIGHT CONTROL DATA CORP., 1984, 1985 ALL RIGHTS RESERVED C, ~"",.. ENTER EDL USER IDENTIFICATION ? edlid ENTER EDL PASSWORD ? dba CURRENT TERMINAL CONFIGURATION GRAPHICS TERMINAL CDC VIKING 721 DIALOG AREA ON GRAPHICS TERMINAL COMMUNICATIONS RATE 9600 BAUD COMMUNICATIONS TYPE ASYNCHRONOUS TABLET NO LOCAL ASSIST DEFAULT LOCAL DISPLAY DEFAULT EGM NO BIT PLANES 4 EDLU0037 YOU ARE NOT RUNNING UNDER YOUR OWN NOS USERNAME 1. 2. 3. 4. ADMINISTRATOR TASKS EXIT USER MANAGEMENT GROUP ADMINISTRATION RELEASE ADMINISTRATION E,EXIT USERMGMT GROUP ADMIN RELADMIN C' ) 2-7 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION 5 • PAR T, FAMIL Y, AND VENDOR MANAGEMENT ENTER TASK ? usermgmt USER MANAGEMENT 1. EXIT 2. LIST USERS 3. ADD USERS 4. DELETE USERS 5. CHANGE A USER'S PROFILE 6. REACTIVATE A USER SELECT OPTION ? c PARTM E,EXIT L,LIST A,ADD D,DELETE C,CHANGE R,REACTIVATE ENTER THE -EDL ID OF THE USER, LIST, OR CR TO EXIT ? edlid CHANGE USER DATA 1. EXIT 2. PROMPT FOR ALL 3. EDL PASSWORD 4. NOS USER NAME 5. LAST NAME 6. FIRST NAME 7 • MIDDLE NAME 8. DEP AR THENT 9. TITLE 10. STREET ADDRESS 11. CITY, STATE, Z"IP 12. PHONE 13. FIRST COMMAND 14. DIALOG DELIMITER 15. STRING DELIMITER 16. EDITOR 17. HOST SELECT OPTION ? p ENTER A NEW EDL PASSWORD OR CR FOR SAME ? dbapw o THE USER'S NOS USER NAME IS EDLDBA ENTER A NEW NOS USER NAME OR CR FOR SAME ? edldba E,EXIT P,PROMPT PSW,PW U,UN L,LNM F,FNM MI,MNM D,DEPT T,TITLE A,ADDR C,CITY PH,PHONE CMD,COMMAND DIALOG STRING EDITOR HOST 2-8 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A --------------------------------------~--------------- -------------- 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION THE USER'S LAST NAME IS ENTER A NEW LAST NAME OR CR FOR SAME ? smith THE USER'S FIRST NAME IS ENTER A NEW FIRST NAME OR CR FOR SAME ? john THE USER'S MIDDLE NAME IS ENTER A NEW MIDDLE NAME OR CR FOR SAME C" ? a THE USER'S DEPARTMENT IS ENTER A NEW DEPARTMENT OR CR FOR SAME ? 2210 THE USER'S TITLE IS DATABASE ADMINISTRATOR ENTER A NEW TITLE OR CR FOR SAME ? THE USER'S STREET ADDRESS IS ENTER A NEW STREET ADDRESS OR CR FOR SAME ? 123 main street THE USER'S CITY, STATE, AND ZIP ARE ENTER A NEW CITY, STATE, AND ZIP OR CR FOR SAME ? minneapolis, mn 55000 THE USER'S PHONE NUMBER IS C, 2-9 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION ENTER A NEW PHONE NUMBER OR CR FOR SAME ? (612) 555-2345 THE USER'S FIRST COMMAND IS ADMIN ENTER A NEW FIRST COMMAND OR CR FOR SAME ? THE USER'S DIALOG DELIMITER IS / ENTER THE NEW DIALOG DELIMITER OR CR FOR SAME ? THE USER'S STRING DELIMITER IS c) " ENTER THE NEW STRING DELIMITER OR CR FOR SAME ? THE USER'S DEFAULT EDITOR IS FSE ENTER THE NEW EDITOR OR CR FOR SAME ? C) CHANGE USER DATA 1. EXIT 2. PROMPT FOR ALL 3. EDL PASSWORD 4. NOS USER NAME 5. LAST NAME 6. FIRST NAME 7. MIDDLE NAME 8. DEPARTMENT 9. TITLE . 10. STREET ADDRESS 11. CITY, STATE, ZIP 12. PHONE 13. FIRST COMMAND 14. DIALOG DELIMITER 15. STRING DELIMITER 16. EDITOR 17. HOST SELECT OPTION -_..._...- .........-..--..- - - - - - - - - - ..... _....- _... _.. _... E,EXIT P,PROMPT PSW,PW U,UN L,LNM F,FNM MI,MNM D,DEPT T,TITLE A,ADDR C,CITY PH,PHONE CMD,COMMAND DIALOG STRING EDITOR HOST _.. _ .. - ----------_. __.- 2-10 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A -"" C .....'/ 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION ------------------------------------------------------ -------~------ ? e *** THE USER'S PROFILE HAS BEEN CHANGED *** ENTER THE EDL ID OF THE USER, LIST, OR CR TO EXIT ? USER MANAGEMENT 1. EXIT 2. LIST USERS 3. ADD USERS 4. DELETE USERS 5. CHANGE A USER'S PROFILE 6. REACTIVATE A USER SELECT OPTION ? list E,EXIT L,LIST ~,ADD D,DELETE C,CHANGE R,REACTIVATE ENTER THE EDL ID OF THE USER, LIST, OR CR TO EXIT ? list 2 SELECTIONS EDL ID NAME 1. EDLCOM 2. EDLID SMITH, JOHN A. *** END OF LIST *** ENTER A NUMBER, E OR EXIT, OR CR FOR MORE ? 2 EDL USER ID NAME NOS USER NAME DEPARTMENT TITLE STREET ADDRESS CITY, STATE, ZIP PHONE FIRST COMMAND STATUS DIALOG DELIMITER STRING DELIMITER EDITOR ENTER CR TO CONTINUE ? EDLID SMITH, JOHN A. 2210 DATABASE ADMINISTRATOR 123 MAIN STREET MINNEAPOLIS,MN 55000 (612) 555-2345 ADMIN ACTIVE / " FSE c; 2-11 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION 2 SELECTIONS EDL ID NAME 1. EDLCOM 2. EDLID SMITH, JOHN A. *** *** END OF LIST ENTER A NUMBER, E OR EXIT, OR CR FOR MORE ? e ENTER THE EDL ID OF THE USER, LIST, OR CR TO EXIT ? o USER MANAGEMENT 1. EXIT 2. LIST USERS 3. ADD USERS 4. DELETE USERS 5. CHANGE A USER'S PROFILE 6. REACTIVATE A USER SELECT OPTION ? e E,EXIT L,LIST A,ADD D,DELETE C,CHANGE R,REACTIVATE ADMINISTRATOR TASKS 1. EXIT 2. USER MANAGEMENT 3. GROUP ADMINISTRATION 4. RELEASE ADMINISTRATION 5. PART, FAMILY, AND VENDOR MANAGEMENT ENTER TASK ? quit E,EXIT USERMGMT GROUP ADMIN RELADMIN PARTM 2.8 UPGRADING EDL DATABASES If your site is currently running a previous version of EDL, you must move the information to the new databases. o If you have customized EDL for your site, also read the section in the customization manual about upgrading site customizations. ,--------_._------- --,_.. _._.... .. __._..-.- - - - - - - - - - - - - ' - ,_ ,. .... _----._.- 2-12 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A CI 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.1 CONVERSION FROM EDL 1.1.3 2.8.1 CONVERSION FROM EDL 1.1.3 To move from EDL 1.1.3 the data must first be moved to an EDL 1.2.0 database, then moved to the EDL 1.2.3 database. All conversion programs and procedures are available on the EDL 1.2.3 release tape. However, you will need to install a default EDL 1.2.0 database from an EDL 1.2.0 release tape. In order to convert the information on an EDL 1.13 database to your EDL 1.2 database, you need to run a procedure called CONVl13. This procedure must be run from the NOS account where the EDL 1.2 database resides. The EDL1.13 database need not be on the same NOS account. Begin the conversion procedure by typing: BEGIN ,·CONV113, E123PRC, UNl13=username. Where username is replaced EDL1.13 database resides. with the NOS account where the This procedure will submit a job.~o convert the data from the EDL1.13 database to the EDL1.2 database. There should be no one else using the EDL 1.2 database during this time. After CONV113 has run, the output from the job, and the dayfile, will be on file CONVOUT. CONVOUT will contain details of any records which the program was unable to translate. If the conversion program is unable to complete, the output and dayfile from the job will be on a file called CONVERR. Possible causes and solutions are: Problem Solution Misspecified UN113 Time Limit Re-run the CONV113 procedure Edit E123PRC, changing the time limit from 1200 on the CONVERT procedure. ReI-nstall an empty default 1.2 databas before attempting to rerun the procedu c' 2-13 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.2 CONVERSION FROM EDL 1.2.0 TO EDL 1.2.3 2.8.2 CONVERSION FROM EDL 1.2.0 TO EDL 1.2.3 Before moving engineering data into the EDL 1.2.3 database, you must reapply any Query Update Transactions which you used to customize the EDL 1.2.0 database. Otherwise, site defined file types, data types, engineering categories, etc., will not be in the new database, and any engineering data information that uses them will be rejected with constraint violations. You should also delete the user EDLID and the group DBA from the default EDL 1.2.3 database before attempting to convert the old database. This will avoid uniqueness constraint violations as that user and group are moved from theEDL 1.2.0 database. Use the user and group management functions of EDL 1.2.3 or Query Update to accomplish the deletion. o To move engineering data from an EDL 1.2.0 database to an EDL 1.2.3 database, type-the following command. BEGIN,CONV120,E123PRC,UN120=username. Where username is replaced with the NOS account where the 1.2.0 database resides. EDL This procedure runs the IMF unload-reload utility and a special program to convert data that cannot be handled properly by the unload-reload utility. - If you have a very large database, you may wish to begin the procedure in a batch job. In some cases, the reload utility may find constraint violations which will cause the new database to be marked invalid. You should look at the error report and lists to determine which records caused the problem. Then use Query Update in repair mode to correct the errors and rerun the validate utility. c ATTACH,IMF2QU/UN=IMF. IMF2QU. -h ~ INVOKE EDLDATAW OF EDLDATA KEyrEDLORDBA + USING E123DDB REPAIR EDLPW (enter QU directives to DISPLAY and correct the database) END ATTACH,IMF2LDU/UN=IMF. 2-14 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.2 CONVERSION FROM EDL 1.2.0 TO EDL 1.2.3 -------------------------------------------------------------------IMF2LDU. ? VALIDATE THROUGH EDLDATAW OF EDLDATA ? KEY EDLORDBA ? USING El23DDB ? REPAIR EDLPW ? TERM ? If you have customized EDL 1.2.0 please read the customization guide before attempting to convert database. It is necessary to adapt and reapply your QU HOB directives before converting the engineering data. new the and 2.9 IMF DATABASE MAINTENANCE 2.9.1 BACKUP AND RECOVERY IMF 2.1 provides utilities for database journal logging and offline database recovery. There are two procedures in EDL that make these utilities easy to use to backup and recover the EDL database. These procedures must be run from the NOS account on which the EDL database resides. They should be run only when there are no EDL users on the system. 2.9.1.1 Backup Procedure BEGIN,BACKUP,E123PRC This procedure copies the EDL database file E123DDB to a backup file named E123BAK. It also creates a journal log file named E123LOG which will automatically capture a record of all changes to the EDL Engineering Data Database. You should run this procedure periodically depending on the amount of EDL activity at your site. Be careful that the database is good before you run the BACKUP procedure since it ':" ~ i:; ...... '';'" 2-15 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.9.1.1 Backup Procedure Before will overwrite any previous backup and log files. running BACKUP, you may wish to copy E123DDB, E123BAK and E123LOG to magnetic tape. 2.9.1.2 Recovery Procedure BEGIN,RECOVER,E123PRC,DBN=username. This procedure is to be used only in the unlikely event that a system crash occurs when the database is open and the EDL database is destroyed. o RECOVER copies the backup file E123BAK over the current database file E123DDB and runs the offline recovery utility to update the database with the journal entries from file E123LOG. This restores tha database to a consistent state as it appeared just before the database was destroyed. Then ~his procedure causes the BACKUP procedure described above to be run, ensuring that any subsequent changes are logged. 2.9.2 RUNNING WITHOUT JOURNAL LOGGING To . turn journal logging off for the EDL database, execute the following p~ocedure. BEGIN,CHLOG,E123PRC, FUNC=OFF, FN=E123DDB ,AFN=E123LOG. Substantial improvements in resource utilization can be achieved by turning journal logging off. However, without journal logging, it is impossible to use the RECOVER procedure to reestablish the database to the point of failure in case the system crashes while a user has the EDL database open. Instead, the file E123DDB must be restored from the last system file backup. o It is unlikely that the database will be corrupted by anything other than a operating system or hardware failure, since IMF performs reprieve processing to close the database gracefully if an program fails or a user uses control T to abort the program. The risk of losing a day or half day of EDL information may be acceptable at your site. The application ._----_.. __._._... _..... -._--_ .. - - - - - - - - - - - - - 2-16 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.9.2 RUNNING WITHOUT JOURNAL LOGGING data such as drawings and journal logging. models are not affected by IMF 2.10 IMF TUNING CONSIDERATIONS The IMF System Tuning File, IMF2STF/UN=IMF, determines certain parameters that IMF 2.1 uses to control it's operation at the system control point. These parameters can affect resource utilization of EDL, response time, and overall system throughput. The tuning parameters are read from the file every time the IMF (MCS) subsystem is started. To some extent,. the optimal settings depend on the type of load on your system. The parameters on the tuning file provided on the EDL release tape are set to reasonable values for an ICEM environment. They are set to minimize the impact of IMF and EDL on system throughput at the possible expense of EDL response time. 2.11 EDL AUTOSTART FOR USERS If a user wishes to log in to EDL without typi~g his EDL user id and password, create an indirect file called EDLUSER on the user's NOS username. This file should have a single line with the user id in columns 1-10 and the EDL password in columns 11-20. EDL will attempt to read this file and will prompt the user only if the file does not exist or if the information on the file is invalid. 2.12 PASSWORD MASKING If all terminals at your site are communicating in full duplex mode, you may cause EDL to temporarily disable echoplex mode while the users are entering passwords so that the password characters do not appear on the terminal screen. This is accomplished by changing the title of the message c 2-17 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.12 PASSWORD MASKING named "DUPLEX" to "FULL", using a MOB transaction file or query update. See the customization guide section "CUSTOMIZING THE MESSAGE AND TASK DATABASE" f~r an explanation of how to change EDL messages. 2.13 USING QUERY UPDATE For the most part, IMF2QU function~ as described in the Update Version 3 Reference Manual 60498300. Query The Invoke clause used to open an IMF 2.1 database schema, is different than the one documented for IMF Version 1. o INVOKE external-schema-name OF conceptual-schema-name [ KEY use-literal] USING database-file-name [ nos-username ] [ REPAIR repair-literal] [ CONCURRENT ] To query the EDL Engineering Database, INVOKE EDL OF EDLDATA USING E123DDB nos-username CONCURRENT To query the EDL Message and Task Database, INVOKE EDLMENUR OR EDLMENU USING E123MOB nos-un To query or update the Engineering Database, INVOKE EDLDATAW OF EDLDATA KEY '$EDLORDBA$ + USING E123DDB nos-un CONCURRENT To query or update the Message and Task Database, INVOKE EDLMENUW OF EDLMENU KEY $EDLORDBA$ + USING E123MOB nos-un Sometimes Query Update will not display data for all records of a record type unless a FOLLOW directive is entered to specify the access path or coset to be used to retrieve the records. See the Query Update manual and the EDL record layout section of the customization guide. o - - - - - _.....,,-,,-_.. _-,,_..._----_._-- -_._---_._--_._----".- ._._.._..... -..- ..---.-- 2-18 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 642A 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.14 USING ICEM DDN VERSION 1.53 OR 1.57 2.14 USING ICEM DDN VERSION 1.53 OR 1.57 EDL 1.2.3 is set by default to interface to DDN 1.6. However, it can be used with DDN 1.53 or 1.57 by simply making 1.6 inactive and making 1.53 active. DDN 1.53 Interfaces to EDL exactly like DDN 1.57, so ~here is no separate Application Information (AI) record for 1.57. Use the following QU directives. MODIFY USING AIAPN AIAPV SETTING AISTA $ICEM DDN$ $1.6$ $INACTIVE$ $ICEM DDN$ $1.53$ $ACTIVE$ *END Also check procedure ICEMDDN in E123PRC to be sure correct file for the DDN absolute is attached. that the C, _/ 3-1 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 3.0 CUSTOMIZATION 3.0 CUSTOMIZATION 3.1 DISCLAIMER The ICEM Engineering Data Library is a flexible can be modified in many different ways. system that To successfully customize EDL you must understand EDL usage, EDL's database structure, the application programs, database management, NOS usage, Cyber Control Language, and Fortran 5. All customizations must be well designed and tested. Serious damage can be done to the information in the EDL database or to application data by customizations that work incorrectly or do not consider all potential situations and user errors. Control Data cannot guarantee that customizations for one version of EDL will be transparently upward compatible to subsequent versions of EDL or to future products. CDC will consider the impact of changes to customizations and will provide conversion procedures to upgra~e data which is maintained by standard code. However, normal enhancement, bug fixes, and evolution will inevitably result in changes to the database structure and the function of CDC supplied code. These normal changes will require that site specific code, transaction files, QU directives, and procedures be readapted and retested at every EDL release. o 3.2 INTRODUCTION There are several ways to customize EDL to fit your site. 3-2 CONTROL DATA CORPORAT+ON 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 3.0 CUSTOMIZATION 3.2 INTRODUCTION 1. Change the text which is displayed by prompts, messages, and menus. 2. Reorganize the EDL Task menu structure. 3. Add new applications, file types, and data types. 4. Add or change engineering categories and their standard attributes. 5. Create new reports, or modify the standard ones. 6. Create new Fortran ovcaps to perform site-specific functions. 7. Create new procedures to be invoked by EDL The following sections explain in detail how to perform these customization functions. The EDL System consists of four basic files. You ability to modify each of them to fit your needs. E123PRC E123ABS E123HDB E123DDB The The The The have the standard EDL Procedure File. EDL Absolute Program. Message and Task Database. Engineering Data Database. 3.3 UPGRADING FROM EDL 1.2.0 TO EDL 1.2.3 Sites that have customized EDL 1.2.0 and want to apply their customizations to EDL 1.2.3 should follow this outline: 1. Install the default EDL 1.2.3 database according to the installation instructions in the beginning of this manual. 2. Rerun all Message and task database transactions using the MENUMGMT task. The structure of the HDB has not changed. However, the field TITYP is now being used to control whether the task can be allowed to run on a subordinate host in a network. Set this field to "MASTER" on any site defined administrative tasks that can only run on the master machine. 3. Edit all QU directive files as needed. A few records in the Engineering Database have changed, as documented in a the ENGINEERING DATABASE RECORD DEFINITION section. Rerun the QU directives files using the QUBATCH task. 3-3 C) CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS -2 Level 642A 3.0 CUSTOMIZATION 3.3 UPGRADING FROM EDL 1.2.0 TO EDL 1.2.3 4. Run the EDL Database Conversion procedure. 5. Edit the source programs for any site defined OVCAPS. It is necessary to replace the common block definitions of all DDB records with the new definitions found on the EDLCOM file. Several common blocks have changed format and names. 6. Recompile and procedure. load the OVCAPS with the LOADEDL 7. Test everything. o . -_._..._._..._._--_ ... _..__ . _ - - - - - - - - - - - 4-1 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 4.0 CUSTOMIZING EDL PROCEDURES. 4.0 CUSTOMIZING EDL PROCEDURES. 4.1 SETTING UP THE EDL PROCEDURE. The procedure EDL in E123PRC is the base procedure for all EDL operations. Its basic purpose is to attach the EDL program file, execute it, execute the procedure calls written on EEEEDL2, and loop until the user chooses to quit EDL. The procedure header has several parameters, which are all passed to the E123ABS execution statement • • PROC,EDL,I=INPUT/INPUT,IT=O/IT,OT=O/OT,HOST=,AUN=. I o Alternate input file. Default is INPUT. IT Input Trace file name. If this parameter is specified, a trace of all input entered by the user is written to the file, or to file IT by default. If not specified or IT=O, no input trace is created. OT Output Trace file name. If this parameter is specified, a trace of all output EDL prints at the terminal and all input the user enters is written to the file, or to file OT by default. If not specified, or OT=O, no output trace is created. HOST The host identification code of the mainframe where this version of EDL resides. Default is blank. AUN Alternate user name. This is the username where the EDL procedure file E123PRC and the absolute E123ABS are to be found. If not specified, EDL assumes they are to be found on the user's own account. It is good practice to edit the proc header to include a default value here so that users do not need to include the AUN parameter on the BEGIN statement. -------'----'---'-'------'----'--- - - - - - - - - - - - - - - - - - - - - - 4-2 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 4.0 CUSTOMIZING EDL PROCEDURES. 4.1 SETTING UP THE EDL PROCEDURE. Other parameters can be included on the E123ABS statement, desired. L Alternate output file. if Default is OUTPUT. DUN Database Username. This is the username where Engineering Data Database is to be found. If specified, EDL assumes the same value as the parameter. MUN Message Database Username. This is the username where the Message and Task Database is to be found. If not specified, EDL assumes the same value as the AUN parameter. ECHO Echo user input to the output file. Used only for debugging purposes when the output file is renamed. the not AUN rl ----.../' 4.2 ALTERNATE PROCEDURES You may write your own procedures to be invoked by EDL. It is suggested that you put them on a separate procedure file other than E123PRC. To allow the user to invoke them, you need to set up EDL tasks and task processes as explained later. 4.3 ADDING A DIRECTORY TO E123PRC The system will find procedures from a proc file faster if the file has a random access directory. We' recommend that you use LIBEDIT to build a directory on E123PRC after you edit it for any reason. See the NOS Version 2 reference manual, Volume 3 for more explanation. GET,E123PRC. GTR,E123PRC,TEMP.PROC/* FSE,TEMP. (enter full screen editor commands) (exit the editor) LIBEDIT,P=TEMP,N=NEW. *BUILD DIR 4-3 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 4.0 CUSTOMIZING EDL PROCEDURES. 4.3 ADDING A DIRECTORY TO E123PRC REPLACE,NEW=E123PRC. ,r-- L) o 5-1 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 5.0 CUSTOMIZING THE MESSAGE AND TASK DATABASE. 5.0 CUSTOMIZING THE MESSAGE AND TASK DATABASE. The overall control and user dialog in EDL is defined by the message and task .database (MOB). It contains defini tions of all messages, prompts, menus, and tasks used by EDL. To modify this database, prepare a MOB Transaction Data file with a standard text editor, update EDL for the transaction file, and i~voke the system administrator task MOBMGMT. EDL uses the standard data retrieval to select the transaction file, updates the message database, and writes a processing report on local file MOBLIST. The Database Administrator's Manual describes the MOB Transaction Data. the format. of The file EDLLIST contains the output from the Query Update job used to load the default Engineering Data and the output from the MOB Transaction program used to load the default tasks and messages. 5.1 CHANGING DIALOG TEXT Dialog text can be changed by changing records in the MOB for the following types of data, without effecting the operation of EDL. 0 * * * * * * * * * Task Menu Headers Task Menu Lines Task Commands Prompts Error Messages Informative Messages Option Menus Headers Option Menu Lines Option Menu Keywords ------------ -----_.•. __._ ...... -....... -..... . ------- ._._-_.._-_...._--- - - - - - - - - 5-2 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 ,CUSTOMIZATION GUIDE NOS 2 Level 642A , 5.0 CUSTOMIZING THE MESSAGE AND TASK DATABASE. 5.1.1 TASK MANAGEMENT 5.1.1 TASK MANAGEMENT A Task is a single function which may be invoked by the user. A task is completely defined by the Task Information (TI) , Task Process (TP) , and Task Parameter Value (TV) records. 5.1.2 TASK INFORMATION HEADER The TI records define the task name and description. 5.1.3 TASK MENUS AND COMMANDS There are two ind'ependent ways for a user to invoke a task, task commands and task menu lines. These paths are specified by the TC and TM records, respectively. Any number of commands. or prompts may invoke the same task, or a task may have no direct path at all if it is intended to be used.only as a subtask. 5.1.4 TASK SECURITY CATEGORIES To prevent certain users from using a group of tasks, update the TI records in the message and task database to give each task in the restricted category a non-blank task security category code (TISEC). Then only users who belong to a group which is authorized to that security category may invoke any tasks in the category. The groups are authorized for security categories with the TASK ACCESS MANAGEMENT (GROUPTASKS) command. For example, in the default database there are three different values in the TISEC fields: blank Unsecure tasks which may be entered by any user. ADMIN Administrator tasks for part user, group, and manag emen t • SYSADMIN System adminstrator tasks for customizing the EDL ('I \~ 5-3 --·, C----) CONTROL DATA CORPORATION ~985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 5.0 CUSTOMIZING THE MESSAGE AND TASK DATABASE. 5.1.4 TASK SECURITY CATEGORIES databsae. There is only one group in the default database, DBA. The DBA group is authorized to enter both ADMIN and SYSADMIN tasks. Therefore, any user in the group DBA can execute any task in EDL. You may wish to establish a separate group which has only ADMIN privileges. Another possibilities is making some applications secure by putting non-blank values in the TISEC fields of the appropriate task information (TI) records. 5.1.5 TASK MENU TREES (-"\ You may set up as many task menu structures as you need. commonly, a task menu needs Most '-.-/ 1. A TI record (Task Information) 2. A TP record (Task Process) with TPTYP="TASK MENU" 3. A MI record (Menu Header) with MIMNA set the same as the TPNAM field 4. Several TM records' (Task Menu Lines). The TMTNA field defines which task is invoked when the user picks the line number. The task to be invoked must have already been defined in a previous TI record before the TM record is added. This means that Subtasks are defined before the Task Menus that call them. 5.1.6 TASK PROCESSES Each which Task types o task consists of one or more Task Processes or steps are executed sequentially when the user invokes a task. Processes are defined by the TP record. There are five of processes, differentiated by the TPTYP field. OVCAP CCL PROC TASK MENU TASK FUNCTION Overlay capsules from file E123ABS. Cyber Control Language procedures from E123PRC or any other procedure file. Display a task menu Execute a different Task as a subtask. Perform short EDL functions, such as EXIT-TASK ---'---'" .... _.. -_ .... -_._---_."' _... ._- . --_....... ..... _- " - - ' , tT/: ~,~. 5-4 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 5.0 CUSTOMIZING THE MESSAGE AND TASK DATABASE. 5.1.7 TASK PARAMETER VALUES 5.1.7 TASK PARAMETER VALUES Parameters may be passed to overlay capsule or CCL which are set up to accept the parameters. name=value syntax to pass parameters, not parameters. The parameter name is defined in field. procedures EDL uses positional the TVPRM In some EDL overlay capsules, there are hard coded calls to the GETPRM subroutine. The value of the task parameter is then returned to the EDL program. There are field. 4 types of parameters, differentiated by the TVTYP CONSTANT EDL passes a constant to the process. PROMPT The user is prompted for the value of the parameter to be passed to the process. The TVVAL field should contain the message name of the prompt or option menu to be displayed to the user. NULL The process is passed a null value. a carriage return. VARIABLE The value of an EDL global variable is passed to the process •. An EDL global variable. must be previously set by an overlay capsule which- uses the PUTVAR subroutine. CONFIG This simulates • EDL Passes a parameter value based on the contents of the Application Configuration (AC) records, Application Information (AI) status (must be and the user's current terminal ACTIVE), configuration. 5.2 EDL GLOBAL VARIABLES A gobal variable is a mechanism that EDL uses to pass values ,through the EDL session, for example, from overlay capsules to procedures. The 10 character variable name and 40 character value are stored in an array while the EDL absolute program is 5-5 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 5.0 CUSTOMIZING THE MESSAGE·AND TASK DATABASE. 5.2 EDL GLOBAL VARIABLES running, and on a local file application program is active. while a CCL procedure or To establish a variable, an EDL ovcap must use the PUTVAR subroutine. The value of the global variable stays in effect until the variable is redefined or EDL ends. To retrieve a global variable, an EDL ovcap uses the GETVAR subroutine. Global Variables may also be passed to CCL PROC or OVCAP task processes via task parameter value (TV) records with TVTYP=VARIABLE. Several EDL global variables are defined by EDL as soon as the user starts. USR The EDL id of the running user. HOST The Host code of the computer system on which the user is running. AUN The value of the AUN parameter passed to the EDL absolute program. DDB PFN of the Engineering database. DUN NOS UN of the Engineering database. MDB PFN of the Message Database. HUN NOS UN of the message database. EDITOR The user's preferred editor from the user profile. DDNVER The version number of the active version of ICEM DDN Some global variables are set by capsule when an engineering data set standard retrieval list. EDN HOS OS PFN UN NAME! NAME 2 SHEET o The The The The The The The The the' XRETREV or DISPLAY is selected from the internal Engineering Data Number selected data. Host Identifier of the data. Operating System of the host data. Permanent file name where the data resides. NOS (or other OS) Username of the data. first 38 characters of the data name. last 32 characters of the data name. secondary ide Some global variables are set by the XTRANSF capsule when user is transferring data. the EDN2 The Engineering Data Number of the new destination data. HOS2 The host identifier of the destination data. 5-6 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 5.0 CUSTOMIZING THE MESSAGE AND TASK DATABASE. 5.2 EDL GLOBAL VARIABLES OS2 PFN2 UN2 RENAME THE Operating System of the destination data. The Permanent file name of the destination file. The NOS Username of the destination file. "Y" If the user wants to give the transferred data a different name, otherwise "N". NAME12 The first 38 characters of the new data name. NAME22 The last 32 characters of the new data name. SHEET2 The new secondary ide For data transfers between variables are established. hosts, the following global BID Username of the user on the source host. BPW Batch Password of the user on the source host. CHR Character code format of the source data for MFLINK. BID2 Username of the user on the destination host. BPW2 Batch Password of the user on the destination host. CHR2 Character code format of the destination data MFLINK. for Other parts of the EDL system use other global variables to communicate data between ovcaps and procedures. They are described further in the section on EDL STANDARD OVERLAY CAPSULES. 5.3 MESSAGE SUBSTITUTION One special and useful capability is Message Substitution. The DBA can cause EDL to use a different method to determine a value returned to the program rather than prompting with the standard message or menu. This is accomplished simply by defining a task parameter value (TV) for the ovcap task process with the same name (TVPRM) as the message name (MIMNA) of the prompt or option menu that you want to change in the ovcap. The parameter can be of any type. If it's a NULL, CONSTANT, or VARIABLE, the user will not be prompted at all. If it's a PROMPT, the user will be prompted with the message whose name is in the TVVAL field instead of the standard message. The substitution is effective only when the ovcap is used by the single task process. Other usages of the message in 5-7 c:) CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 5.0 CUSTOMIZING THE MESSAGE AND TASK DATABASE. 5.3 MESSAGE SUBSTITUTION different proceses are not affected. On the other hand, if the text of a message is changed, it is changed the same everywhe~e the prompt is used. The following example set of HOB Transactions will null out the prompts that ask the user on which host a file resides and cause EDL to assume that all files are on the local machine. If you are running with a single CAD/CAM system, you may wish to apply these to your EDL. A TV A TV A TV C> UPDATA DELETE CORRECT 10 1 1 1UP DATA 1 IFIDEL1 1FICORRl NULL NULL NULL 5.4 MESSAGE AND TASK DATABASE REPORTS There are 4 report procedures in E123PRC to aid you in determining the contents of the HOB. You may modify them or create others using the Query Update report writer. 5.4.1 TASK REPORT This report prints all tasks (TI) , their processes their parameters (TV). (TP) , and BEGIN,RTASKS,E123PRC,MUN=mdb username. 5.4.2 TASK MENU REPORT This report prints all task (TM) • o headers (MI) , and their lines BEGIN,RTMENU,E123PRC,MUN=mdb username. - - - - - _ . _.. _.. - - - - - - ._ .. _. --_. 5-8 CONTROL DATA CORPORATION 1985/12/31 r~ ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A ............ ,....,' 5.0 CUSTOMIZING THE MESSAGE AND TASK DATABASE. 5.4.3 PROMPT REPORT 5.4.3 PROMPT REPORT This report prints all.single line prompts (MI). BEGIN,RPROMPT,E123PRC,MUN=mdb username. 5.4.4 OPTION MENU REPORT This report prints all option menu headers (MI) , their option menu lines (OM), option variables (OV) and option keywords (OK) • BEGIN,RMENU,E123PRC,MUN=mdb username. 5.5 ORGANIZING EDL MOB TRANSACTIONS The order in which tasks and menus are defined on the transaction file is critical to satisfy database constraints properly. In a sense, tasks should be defined in a top-down order, with the most major tasks first, while task menus should be defined in a bottom-up order to be sure that the tasks referenced in the Task Menu Line records (TMTNA) already have Task Information records defined. Start defining each section of the task menu tree with the task definition of the most major task, and end the section with the menu definition of the major task. Subtasks and submenus are defined between the task and menu of the major task. The EDLLIST file shows how the structure of the default task and message database was defined. A TI A TC A TP MAINTASK MAINTASK MAINTASK MAIN MAJOR TASK A TI A TC A TP SUBTASKA SUBTASKA SUBTASKA A 1TASK MENU MAINMENU SUBORDINATE TASK A 1TASK MENU SUBMENUA C:: 5-9 CONTROL DATA CORPORATION C) 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 5.0 CUSTOMIZING THE MESSAGE AND TASK DATABASE. 5.5 ORGANIZING EDL MDB TRANSACTIONS C) A TI A TC A TP SUBTASKA1 SUBTASKA1 Al SUBTASKA1 A TI A TC A TP SUBTASKA2 SUBTASKA2 A2 SUBTASKA2 A MI A TM A TM A TM SUBMENUA SUBMENUA SUBMENUA SUBMENUA A A A A TI TC TP TV SUBTASKB SUBTASKB SUBTASKB SUBTASKB A A A A MI TM TM TM MAINMENU MAINMENU MAINMENU MAINMENU TASK MENU SUBORDINATE TASK Al 10VCAP SUBA1 SUORDINATE TASK A2 10VCAP SUBA2 SUBORDINATE TASK MENU A 1EXIT 2SUBORDINATE TASK Al 3SUBORDINATE TASK A2 SUBORDINATE TASK B B 1CCL PROC SUBB 1 2P1 CONSTANT XYZ TASK MENU MAJOR TASK 1EXIT 2EXECUTE SUBORDINATE MENU A 2EXECUTE SUBORDINATE TASK B o - - - - - _ . _ - _.. _-_.._....__._..._. __.,--,,-,.._----,,- 6-1 CONTROL DATA CORPORATION C '~' 1985/12/31 \ / \ ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 6.0 CUSTOMIZING THE ENGINEERING DATA DATABASE 6.0 CUSTOMIZING THE ENGINEERING DATA DATABASE The Engineering Data Database (DDB) contains all the information about users, applications, files, and data. It is changed in two ways: updated by the EDL user or administrator performing EDL tasks, or customized by the EDL system administrator using Query Update. The file EDLLIST contains the output from the Query Update job used to load the default Engineering Data and the output from the MDB Transaction program used to load the default tasks and messages. EDLLIST can be used as an example and documentation of how MDB Transactions and Query Update are used to customize EDL. Format definitions of the records updated in EDLLIST are found in later sections of the customization guide. 6.1 ENGINEERING CATEGORIES AND STANDARD ATTRIBUTES When a user creates data in EDL, it must be given an These 20 character codes are Engineering Category code. application site-defined. The EDL system or completely programs function the same regardless of what category the and Their only purpose is description data is given. retrieval. o The user can also set up data descriptors to aid in describing and retrieving the data. A descriptor is a pair of character strings associated to the data, an attribute name (20 For characters) and an attribute value (40 characters). example, the user may ask for attribute name = PROJECT CODE and attribute value = T110 to retrieve all permitted data for the T110 project. You (the DBA) may associate one or more standard attribute names to a Category. Then, when the user updates EDL data descriptors, he may ask EDL to prompt for the values for each 6-2 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 6.0 CUSTOMIZING THE ENGINEERING DATA DATABASE 6.1 ENGINEERING CATEGORIES AND STANDARD ATTRIBUTES of these attributes. Setting up standard attributes does not restrict the user in any way. That is, he or she can still enter- a descriptor with a non-standard attribute name if desired for a special purpose. However, users should be encouraged to use the standard attribute prompting feature and to take some care to use consistent attribute values. Engineering Categories and standard attributes are set up by using QU to update the ET and EA records in the database. For example, those in the released database were set up in the following way. STORE SETTING ETEDT $ $ $EDL SYSTEMS $PREPRODUCTION$ $PRODUCTION$ $TOOLING$ *END STORE SETTING EAEDT EAATR $PREPRODUCTION$ $PROJECT CODES $PRODUCTION$ $PRODUCT LINE$ $TOOLING$ $TOOL TYPE$ *END These trivial categories and attributes should be customized to fit the environment at your site. 6.2 ADDING A NEW APPLICATION Adding a new application to EDL involves modifying nearly every part of the EDL system. You need an application header record in the database, CCL procedures, tasks, menus and commands to invoke the application, tasks to retrieve application data, tasks to perform data transfers and translations, new file type and data type definitions,and perhaps application terminal configuration records to pass parameters to the application. - - - - - - - - - - - - ---------- - - - 6-3 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 6.0 CUSTOMIZING THE ENGINEERING DATA DATABASE 6.2.1 APPLICATION HEADER 6.2.1 APPLICATION HEADER The application header is simply entered with QU. Application Name, Application Version, and Status required. The are STORE SETTING AIAPN AIAPV AISTA $DATA ANALYZER$ $1.0$ $ACTIVE$ *END 6.2.2 NEW FILE TYPE AND DATA TYPE DEFINITIONS C) To add new types of data to EDL, you must define the new file types (FT) on which the data resides, and then define the application data types. For example, here is how ICEM DDN drawing files and drawing data is defined in the default EDL database. Each field is described in the ENGINEERING DATABASE RECORD DEFINITION section. STORE SETTING FTFTC,FTNAM,+ FTLFN, FTLFNR, FTAPN, FTMUL, FTCHR, FTPRT $DRAWING FILE $ $DRAWING FILE $TAPE3 $ $T$ $ICEM DDN$ $T$ $B$ $F$ *END STORE SETTING ATADT ATNAM + ATFTC ATSIDR ATTNA $DRAWING $ $DRAWING $DRAWING FILE $ $T$ $RET-DRW$ *END $ + $ + 6.3 TERMINAL CONFIGURATION EDL stores terminal configuration data for each user in the User Configuration (UC) records. By matching the user's configuration with the Application Configuration (AC) records, and the Application Information (AI) records, EDL decides what configuration parameter value to pass to the CCL procedures ---------_. __._-_ ..__ ............ _..... _ . _ . _ - - - - - - - - - - - - _._--_ ..•................• --_._-_ ...- - - - - - - 6-4 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A \ ....... / 6.0 CUSTOMIZING THE ENGINEERING DATA DATABASE 6.3 TERMINAL CONFIGURATION which execute application programs. Like all parameters, They are controlled ~y Task Parameter Value (TV) records for the CCL PROC Task process. If the TVTYP field is CONFIG, EDL looks for all the AC records with ACPRM fields that match the TVVAL field of, the TV record. If the ACATR and ACSTA fields match the user's current UCATR and UCSTA fields, the application name and version in ACATR and ACAPV are used to key to the AI record, and if the AISTA field is "ACTIVE", the value in ACVAL is passed to the CCL procedure. See the EDLLIST file for examples of AC records for the default ICEM applications and the UC records for user EDLID. 6.4 LOGGING PATTERNS INTO EDL The default EDL configuration automatically updates EDL for any adds, changes, or deletions of DRAWINGS and GLOBAL DRAWINGS which occur to permanent files in ICEM DDN. Your site can choose to cause information about PATTERNS to be updated in the same way. ICEM DDN V1~6 already puts logging transactions for PATTERNS on ,the EDLLOG file. However, the application data type (ATADT) in EDL is GLOBAL PATTERN, while the ADT field on the EDLLOG file is PATTERN. Since PATTERN is not a valid data type, EDL ignores the log transactions. If you wish to log PATTERNs, simply with the following QU transactions. r change the ATADT field MODIFY USING ATADT SETTING ATADT ATNAM $GLOBAL PATTERN$ $PATTERN$ $PATTERN$ *END This will work only if there are no Data Information (01) records with DIADT=GLOBAL PATTERN. Otherwise, it is necesary to add a new AT record as follows: STORE SETTING ATADT ATNAM ATFTC ATSIDR ATTNA $PATTERN$ $PATTERN$ $GLOBAL PATTERN FILE$ $F$ $ $ *END 6-5 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 6.0 CUSTOMIZING THE ENGINEERING DATA DATABASE 6.4 LOGGING PATTERNS INTO EDL MODIFY USING DIADT SETTING DIADT $GLOBAL PATTERN$ $PATTERN$ *END REMOVE USING ATADT $GLOBAL PATTERN$ *END o 7-1 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 7.0 ADDING FORTRAN CODE TO EDL 7.0 ADDING FORTRAN CODE TO EDL You can create your own overlay capsules and integrate them into EDL tasks. These can inquire the EDL database, update the database, use EDL menus and prompts, or perform any other function desired at your site. The first line of each new overlay capsule must be the OVCAP. statement starting in column 7. The rest of the code is merely a set of Fortran subroutines. You may call any of the subroutines in the EDL library documented in the following section EDL UTILITY ROUTINES These can be used to display messages, prompts, menus, or selection lists exactly as the standard EDL ovcaps do. 7.1 DATABASE OPERATIONS If you ne~d to access the EDL database, include the common block definitions found on file EDLCOM for each record type you will be using. 7.1.1 READING THE DATABASE o The database is read by filling the key common block variables with the appropriate value and calling an EDL Information Base routine such as IBOFI1 (obtain the FI record for a file). If the record is found, the status code is returned as logical true, the common block variables are set to the values for the record, and the current position for the record 1S established. You must know the access path for the particular kind of keyed access you desire, since there may be more than one index for a record type. For example, path FIl is keyed by FIHOS, . --_._---_. __ ._-_.__.__ ........ _-_ ... __ ._._ ... _---_._-_ .. -._-.-----_. __ ..._-_ .. _._-_. _...._._._-------- - - - - - 7-2 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 7.0 ADDING FORTRAN CODE TO EDL 7.101 READING THE DATABASE ------------------------------------------------------ ----------~--- FIPFN, FIFUN, and FILNA. id of the file's owner. Path FI2 is keyed by FIUSR, the edl 7.1.2 STORING NEW RECORDS To store records, fill all the fields in the record's common block with legal values, and call the IBSxx routine for the record. If the store worked, the status code returned will be logical true. 7.1.3 DELETING RECORDS To delete records, first obtain the record to establish. the correct current position, then call the appropriate IBDxx routine. C,: -,' 7.1.4 MODIFYING RECORDS To modify a record, first obtain the record to establish the current position, change .the desired fields, then call the IBMxx routine to update the database. You cannot modify the same record twice in a row without reobtaining the record. 7.2 PROGRAMMING GUIDELINES Do not use the following unit numbers for I/O. They are used by the standard EDL code and are kept open for the duration of the EDL program execution. 5 6 3 4 INPUT (I) OUTPUT (L) Input Trace (IT) Output Trace (OT) c' 7-3 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 7.0 ADDING FORTRAN CODE TO EDL 7.2 PROGRAMMING GUIDELINES Other unit numbers are opened temporarily by EDL, but are closed before exiting the OVCAP. Whenever your ovcaps open files, be sure to close them before returning from the ovcap. Do not use local file names beginning FSE, or EDL. with EEE, ZZZ, E123, Do not use the local file name DATA. Do not use subroutine names which conflict with routines in the EDL relocatable libraries. You may CATALOG or ITEMIZE files E123LIB, E123IBL, and E123NBL if you suspect a conflict. Do not use routine names which start with IB, RB, or WB. '· '·' CJ ., o Do not depend upon the contents of database common blocks from one ovcap to another. If a CCL proc is called between the ovcaps, the contents of the common block will be lost. Use the PUTVAR and GETVAR routines to pass global variable values between ovcaps. 8-1 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA' LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 8.0 ADDING TASKS TO EDL 8.0 ADDING TASKS TO EDL The procedure for adding TASKS to EDL is different depending on whether you want to execute a ccl procedure, code, or both. The following example shows a TASK which contains both a procedure and code. 1. Create a Menu Database transaction file which the task to the Menu database. A TI A TC A TP A TP A TV MYTASK . MYTASK MYTASK MYTASK MYTASK will add CUSTOMIZED TASK MYCOMMAND lOVCAP 2CCL PROC 2 XMYCODE MYPROC 1MYPARM MYPROCF VARIABLE MYPARM This transaction file creates a task called MYTASK, which is called with the command MYCOMMAND. The task consists of two parts. First, an OVCAP called XMYCODE is run, ·-then a procedure called MYPROC is executed from file MYPROCF. EDL passes a parameter called MYPARM to procedure MYPROC. 2. Create the OVCAP file OVCAP. SUBROUTINE XMYCODE CALL MYCODE RETURN END The OVCAP could actually contain the code for the subroutine, but we recommend that the code be kept separate in a library, for ease of modification, testing, and maintenance. 3. o C C C Create the routine(s) SUBROUTINE MYCODE THIS ROUTINE PROMPTS THE USER FOR A MESSAGE, AND WRITES IT IN A NOTE TO THE TERMINAL WITH CCL PROCEDURE MYPROC ON FILE MYPROCF. CHARACTER MSG*30 'ENTER THE MESSAGE FOR A NOTE OR CR TO RETURN' .. _-_.__..._.. _.. _... _.. _------_ ..- . _ - - - - - - - - - - - - - - - - - ' - - - 8-2 CONTROL DATA CORPORATION 1985/12/31 ICEK ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 8.0 ADDING TASKS TO EDL CALL INTXT('MYCODEl',MSG,ICH) IF(ICH.NE.O)THEN CALL PUTVAR ( 'MYP ARM' ,MSG) ENDIF RETURN END This routine prompts the user for a character string to be put into variable MSG. If the user enters a string, the routine PUTVAR is called to put string MSG into a variable called MYPARM. The value in MYPARM is then available to any CCL procedure. Remember that CCL can only handle a parameter of up to 40 characters. As with the code for a customized retrieval, this code should be put into a library. You must also remember to copy the corresponding common blocks from file EDLCOM if you use any of the Information Base (IB) routines. 4. Create routine A MI AMH AMH MYCODEI MYCODEI MYCODEI 5. the Menu PROMPT Databas~ transactions needed for'the ENTER THE MESSAGE FOR A NOTE OR CR TO RETURN lWHAT YOU ENTER HERE-WILL BE DISPLAYED IN A 2NOTE ON YOUR TERMINAL AND IN YOUR DAYFILE. Create the CCL procedure .PROC,MYPROC,MYPARM. NOTE"NR./MYPARM REVERT. MYPROC EXIT. REVERT ,ABORT. MYPROC Save the procedure in the file named in the menu database transaction file created in step 1. The file should be permitted in the same manner as the file EI20PRC. 6. Load the routines. If the OVCAP from step 2 had been written onto a file called MYOVCAP, and the routine from step 3 had been put on library MYLIB, the call to LOADEDL would look like this: BEGIN, LOADEDL, EI20PRC, F=MYOVCAP ,ULIB=MYLIB. C-~, 8-3 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 8.0 ADDING TASKS TO EDL LOADEDL will create a new E120ABS absolute by combining the OVCAPs and routines from your original release of EDL with the OVCAPs in file MYOYCAP and the routines in library MYLIB. Please note that any routines and OVCAPs which you may have added before wil not be in this load, unless they are in the OVCAP and library files loaded here. 7. Update EDL for the Menu Database transaction file Put the transactions created in steps 1 and 4 into the same file, and update EDL for those transactions in the following manner: Enter EDl using an ID with SYSADMIN privileges (like EDLID). A. Choose ADD INFORMATION FOR ENGINEERING DATA task (task command ADDINFO. o 1. The APPLICATION DATA TYPE is EDl MDB TRANSACTIONS. 2. Give the data a meaningful name, like MDB TRANSACTIONS TO ADD A MYTASK B. Enter the task command MENUMGMT. 1. Retrieve the data which you just entered into EDl. 2. Select that data, and the changes will be automatically entered into EDl. If you are entering a task which contains procedure, you can omit steps 2, 3, 4, and 6. only a CCl If you are entering a task which contains only an OVCAP, you can omit step 5. o - - - - - - _.. --"--"-",-,-,,,--,,,-,_._., "'._-_. __ ..._- .... _--,,--._._--,- - ---------------- -" -"._---._._-- -" ,--- - - - - - - - - - - ---_._._---_.- .__ . --- -- _... _-----------_._-- -- ._---------,---------- SOFTWARE RELEASE BULLETIN ICEM Facilities 1.3 (NOS 2.4.2 LV 642A) SMD131035 C) ........ o , , \ J CONTROL DATA CORPORATION ICEM Facilities 1.3 Software Release Bulletin Page 1 December 20.1985 ----------------------------------------------------------------- 1. Procedure files ICEMFAC and VERIFY were written assuming that ICEM Design/Drafting version 1.60 is stored as a direct access file named ICEMDDN on user name APPLLIB. It is also assumed that a direct access file named GOLIB is stored on APPLLIB. If these assumptions are incorrect. change lines 10 through 12 of the procedure ICEMFAC in file ICEMFAC. lines 7 through 9 of procedure EXTRACE in file ICEMFAC and lines 12 through 14 in procedure VERIFY in file VERIFY. 2. ICEM Facilities version 1.3 can be run using the ICEM Design/Drafting feature FEET and INCHES. When doing a facilities layout using the BEGING LAYOUT tablet pick of tablet overlay LAY1. all prompts must be answered in inches. o , ...... ·t o I c l C 9-1 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 9.0 SITE DEFINED RETRIEVALS 9.0 SITE DEFINED RETRIEVALS A special provision has been made to allow you to put site written code into EDL for adding a site defined retrieval method. This change to EDL does not involve adding OVCAPS, but rather only adding subroutines and menu lines. The retrieval selection routine in EDL has been written so that it will process an additional option value of SITE in option menus EXTRAC and EXFRAC. If this value is encountered, EDL will call a routine called EXTSIT. The procedure for' adding this routine consists of 4 steps: 1. Write and compile a routine named EXTSIT. Put, this routine on a library using the LIBGEN utility. 2. Create a Menu Database Transaction file, containing the desired menu changes, prompts, error messages, and help information. 3. Use the procedure LOADEDL to create a new EDL absolute, with the additional routine. 4. Update EDL for the file of Menu Database transactions. Apply the transactions to the EDL Menu Database. 9.1 ROUTINE EXTSIT The routine must be named EXTSIT. After the routine is compiled, it should be placed in a library using the LIBGEN utility. o Here is an example of a retrieval routine, to retrieve based on the type of the file which the data resides on. 1 2 3 data SUBROUTINE EXTSIT(NUM) CXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX CXX 9-2 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 9.0 SITE DEFINED RETRIEVALS 9.1 ROUTINE EXTSIT 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 '44 45 46 47 48 49 CXX CXX CXX CXX CXX CXX CXX CXX CXX CXX CXX PURPOSE - RETRIEVE BY FILE TYPE CODE CALL PARAMETERS ARQUMENT TYPE NUM I I/O o DESCRIPTION NUMBER OF RECORDS RETRIEVED DATABASE USAGE 01 DATA INFORMATION RECORD FT FILE TYPE RECORDS FILE INFO RECORDS FI CXXXXXXXXXXXXXXXX.~~~nAI~Afl.j~~~~~~XXXXXXXXXXXXXXXXXXXXXXX C ENTER FILE TYPE C IF 'LIST' CALL LISFTC C SET FIFTC TO THE FILE TYPE C OBTAIN AN FI RECORD C WHILE THERE ARE FI RECORDS C USE THE FIDI COSET TO GET A 01 RECORD C WHILE THERE ARE 01 RECORDS C CALL EXTWRI(NUM) TO WRITE THE RECORD TO EEEDL9 IF C THE DATA IS PERMITTED C GET ANOTHER 01 RECORD C GET ANOTHER FI RECORD . . CXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX C C EDL- COMMON . C EDL PRIMARY COMMON BLOCK COMMON /ECOM!/ HOST, USR, PWD, MDISP, SCLOCK, +CHELP, ~LIST, CEXIT, CMENU, CCLEAR, +CWORK, CREL, CSUBM, CPEND, COBS, +CPAUSEl, CPAUSE2, CINOPTl, CEXTH1, +CYES, CNO, +NOSUN, STRDEL, INPDEL, +AUN, DUN, DDB, MUN, MOB, AC, IT, OT CHARACTER*10 HOST, USR, PWD, MOISP, SCLOCK CHARACTER*10 CHELP, CLIST, CEXIT, CMENU, CCLEAR CHARACTER*10 CWORK, CREL, CSUBM, CPEND, COBS CHARACTER*70 CPAUSEl, CPAUSE2, CINOPTl, CEXTM1 CHARACTER*3 CYES,CNO CHARACTER*7 NOSUN CHARACTER*1 STRDEL, INPDEL CHARACTER*7AUN, DUN, DDB, HUN, MOB CHARACTER*2 AC CHARACTER*7 IT,OT COMMON /ECOM2/ NSYNC, PW, PL, NL, SCROLL, ECHO INTEGER NSYNC, PW, PL, NL 09-3 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 9.0 SITE DEFINED RETRIEVALS 9.1 ROUTINE EXTSIT 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 c 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 090 o 91 92 93 94 95 LOGICAL SCROLL, ECHO C *i. * C *i. * USE DI STATEMENTS GENERATED BY IMF2 COMMON / DI / DIEDN COMMON / R600701 / DINAH COMMON / R600702 / DISID ,DIFloL COMMON / R600703 / DIREV ,DIEDT ,DIADT ,DIUSR ,DITTL *,DIDATC ,DIDATM ,DIDATR ,DITIMC ,DITIMM ,DITIMR INTEGER DIEDN ,DISID ,DIFIL CHARACTER DINAH *70,DIREV *10,DIEDT *20,DIADT *20 *,DIUSR *10,DITTL *lOO,DISTA *10,DIDATC *lO,DIDATM *10 * ,DIDATR *lO,DITIMC ~"lO,DITIMM *10,DITIMR *10 USE FI STATEMENTS GENERATED BY IMF2 COMMON / FI / FIFIL COMMON / R601601'/ FIHOS ,FIFUN ,FIPFN ,FIFTC ,FISTA *,FIVSN ,FICT ,FIMOD INTEGER FIFIL CHARACTER FIHOS * 10 "FIFUN *31, FIPFN ,., 100, FIFTC *20 *,FISTA *lO,FIUSR *lO,FIVSN *6,FICT *2,FIMOD *1 ,DISTA ,FIUSR C C *i. * USE FT STATEMENTS GENERATED BY IMF2 COMMON / FT / FTFTC ,FTNAH ,FTAPN ,FTLFN COMMON / R602201 / FTLFNR ,FTMUL ,FTPRT COMMON / R602202 / FTCHR LOGICAL FTLFNR ,FTMUL ,FTPRT CHARACTER FTFTC *20,FTNAH *21,FTAPN *20,FTLFN *,FTCHR *1 *7 C 100 C C C C LOGICAL OK CHARACTER FTC*20 CONTINUE NUM=O GET THE FILE TYPE 'ENTER THE FILE TYPE TO BE RETRIEVED OR LIST OR CR TO RETURN' CALL INTXT('EXTSIT1',FTC,ICH) IF(ICH.NE.O) THEN IF(FTC.EQ.CLIST) THEN CALL LISFTC(FTC,OK) FTFTC=FTC 9-4 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 9.0 SITE DEFINED RETRIEVALS 9.1 ROUTINE EXTSIT 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 1-36 137 138 139 140 141 ELSE FTNAM=FTC CALL IBOFT1 (OK) IF(:NOT.OK) THEN C 'THE FILE TYPE IS NOT RECOGNIZED BY EDL' CALL ERR('EXTSIT2') ENDIF ENDIF IF (OK) THEN FIFTC=FTFTC CALL IBOFI4(OK) 200 IF (OK) THEN CALL IBFFIDI(OK) IF (OK) THEN 300 CALL EXTWRI(NUM) CALL IBNFIDI(OK) GO TO 300 ENDIF CALL IBEFI4 (OK) GO TO 200 ENDIF ENDIF ENDIF 900 CONTINUE RETURN END SUBROUTINE EXFSIT(NUM) CXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX CXX CXX PURPOSE - FURTHER RETRIEVE BY FILE TYPE CODE CXX CXX CALL PARAMETERS CXX ARQUMENT TYPE I/O DESCRIPTION CXX NUM I o NUMBER OF RECORDS RETRIEVED CXX CXX DATABASE USAGE CXX DI DATA INFORMATION RECORD CXX FI ~ILE INFO RECORD CXX FT FILE TYPE RECORD CXX CXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX C ENTER FILE TYPE C IF 'LIST' CALL LISFTC C SET FIFTC TO THE FILE TYPE C READ A RECORD OFF EEEDL9 C GET THE CORRESPONDING DI RECORD C~I 9-5 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 9.0 SITE DEFINED RETRIEVALS 9.1 ROUTINE EXTSIT o o 142 C GET THE CORRESPONDING FI RECORD IF THE FTC'S MATCH 143 C 144 C WRITE THE RECORD TO EEEDL10 145 C READ ANOTHER RECORD FROM EEEDL9 146 CXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 147 C 148 C EDL COMMON 149 C EDL PRIMARY COMMON BLOCK 150 COMMON /ECOM1/ HOST, USR, PWD, MDISP, SCLOCK, 151 +CHELP, CLIST, CEXIT, CMENU, CCLEAR, 152 +CWORK, CREL, CSUBM, CPEND, COBS, 153 +CPAUSE1, CPAUSE2, CINOPT1, CEXTM1, 154 +CYES, CNO, 155 +NOSUN, STRDEL, INPDEL, 156 +AUN, DUN, DDB, MUN, HOB, AC, IT, aT 157 CHARACTER*10 HOST, USR, PWD, MDISP, SCLOCK 158 CHARACTER*10 CHELP, CLIST, CEXIT, CMENU, CCLEAR 159 CHARACTER*10 CWORK, CREL, CSUBM, CPEND, COBS 160 CHARACTER*70 CPAUSE1, CPAUSE2, CINOPT1, CEXTM1 161 CHARACTER*3 CYES,CNO 162 CHARACTER*7 NOSUN 163 CHARACTER*l STRDEL, INPDEL 164 CHARACTER*7 AUN, DUN, DDB, MUN, MDB 165 CHARACTER*2 AC 166 CHARACTER*7 IT,OT 167 COMMON /ECOM2/ NSYNC, PW, PL, NL, SCROLL, ECHO 168 INTEGER NSYNC, PW, PL, NL 169 LOGICAL SCROLL, ECHO 170 C 171 *i. USE DI 172 * STATEMENTS GENERATED BY IMF2 173 COMMON / DI / DIEDN 174 COMMON / R600701 / DINAH 175 COMMON / R600702 / DISID ,DIFIL 176 COMMON / R600703 / DIREV ,DIEDT ,DIADT ,DIUSR ,DITTL ,DISTA 177 *,DIDATC ,DIDATM ,DIDATR ,DITIMC ,DITIMM ,DITIMR 178 INTEGER DIEDN ,DISID ,DIFIL 179 CHARACTER DINAH *70,DIREV *10,DIEDT *20,DIADT *20 180 *,DIUSR *10,DITTL *100,DISTA *10,DIDATC *10,DIDATM *10 181 *,DIDATR *10,DITIMC *10,DITIMM *10,DITIMR *10 182 C 183 *i. USE FI 184 * STATEMENTS GENERATED BY IMF2 185 COMMON / FI / FIFIL 186 COMMON / R601601 / FIHOS ,FIFUN ,FIPFN ,FIFTC ,FISTA ,FIUSR 187 ,FIHOD *,FIVSN ,FICT -----_ .._. __._ .. _-_ _._ __._._---_ _ - - - - - - - - - - - - - - - - - - - - - .. ... _.. .• 9-6 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 9.0 SITE DEFINED RETRIEVALS 9.1 ROUTINE EXTSIT INTEGER FIFIL CHARACTER FIHOS *10,FIFUN *31,FIPFN *,FISTA *10,FIUSR *10,FIVSN *6,FICT 188 189 190 191 192 C C 193 *i. 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 21.? 216 217 218 219 220 221 222 223 224 225 226 227 2.28 229 230 231 232 233 * *100,FIFTC *20 *2,FIMOD *1 USE FT STATEMENTS GENERATED BY IMF2 COMMON / FT / FTFTC ,FTNAM ,FTAPN ,FTLFN COMMON / R602201 / FTLFNR ,FTMUL ,FTPRT COMMON / R602202 / FTCHR LOGICAL FTLFNR ,FTMUL ,FTPRT CHARACTER FTFTC *20,FTNAM *21,FTAPN *20,FTLFN *,FTCHR *1 *7 C 100 LOGICAL OK CHARACTER FTC*20,LINE*80 CONTINUE NUM=O C C C C GET THE FILE TYPE C 200 5000 'ENTER THE FILE TYPE TO BE RETRIEVED OR LIST OR CR TO RETURN' CALL INTXT (' EXFSITI ' ,FTC, ICH) IF (ICH.NE. 0) THEN IF(FTC.EQ.CLIST) THEN CALL LISFTC(FTC,OK) FTFTC=FTC. ELSE FTNAM=FTC CALL IBOFTI (OK) IF (. NOT. OK) THEN 'THE FILE TYPE IS NOT RECOGNIZED BY EDL' CALL ERR('EXFSIT2') ENDIF ENDIF IF (OK) THEN REWIND 9 READ (9, 5000, END=900) DIEDN, LINE FORMAT (I10,A) CALL IBODIO(OK) IF(.NOT.OK)CALL ERRIB FIFIL=DIFIL CALL IBOFIO(OK) IF(.NOT.OK)CALL ERRIB IF(FIFTC.EQ.FTFTC) THEN WRITE(10,5000)DIEDN,LINE 9-7 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 9.0 SITE DEFINED RETRIEVALS 9.1 ROUTINE EXTSIT 234 235 236 237 238 239 240 241 900 NUM=NUM+1 ENDIF GO TO 200 ENDIF ENDIF CONTINUE RETURN END 9.1.1 EXPLANATION OF EXTSIT o o Lines Explanation 1 EDL is coded to look for the routine EXTSIT, with the parameter NUM where NUM is the riumber of records found. This counter wil be incremented by the routine EXTWRI, so is not changed by this routine. 2-15 Prologue. The database usage area is the names of the database records used in this routine. These record types correspond to the common blocks which need to be copied from the file EDLCOM. 16-27 Explanation of how the routine processes. 28-82 Common Blocks. These should be copied from file EDLCOM. Blocks DI, FI, and FT are used by the IB (Information Base) routines. The corresponding block should be copied for each record type used. EDL COMMON is the primary common block in EDL and contains constants used throughout EDL. In this case, the block is used only to provide the constant CLIST. 83 The logical variable OK will be used to monitor the status of the calls to the IB routines. 84 Character variable FTC will be used to store the user's choice of File Type Code 86 NUM is the count of records found. If NUM is returned to the calling routine as 0, the routine will display the message that no records were found. This count is ........ _._.•.._.... _-_.._._._.. _ - - - - - 9-8 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2. Level 642A 9.0 SITE DEFINED RETRIEVALS 9.1.1 EXPLANATION OF EXTSIT updated by routine EXTWRI. 91 Prompt for input. The routine INTXT finds the message named 'EXTSIT1' in the message database, and prompts with that message, putting the response in variable FTC. ICH is the length in characters of the response. 92 If the response was a carriage return, ICH will be O. In that case, this routine skips to the ENDIF on line 118, and returns. 93-100 An explanation of File Type (FT) records: There are two identification fields in the FT record--FTFTC and FTNAK. When EDL is released, these fields contain identical information. FTFTe is the File Type Code which EDL uses internally. This field should not be changed. FTNAK is the external name which the user will see. This can be customized to anything which will be better understood by the user, dependant on·.the site. LISFTC is a routine which lists all FTNAK fields. When the user makes a choice, the value of the corresponding FTFTC field is returned for EDL to use. 93-95 If the response is equal to the constant CLIST (which is set to LIST when EDL is released, but can be changed), then the routine LISFTC is called. LISFTC lists the available FTNAK values, and prompts the user to choose one. If the user chooses to EXIT, the variable OK is set to FALSE. If the user chooses one of the file names, OK is set to TRUE, and the FTFTC value corresponding to the FTNAK chosen by the user is put into variable FTC. 97-102 If the response is not CLIST, FTNAM is set equal to the response, IBOFT1 is called to obtain the FT record via access path FT1. If there is no FT record found, the error message EXTSIT2 is displayed. If the matching FT record is found, all fields in the common block FT are filled with information from the matching record. 104 If OK was set to false, either because the FT record was not found, or the user chose to EXIT from routine LISFTC, processing skips to the ENDIF in line 117, and returns to the calling routine. c c 9-9 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 9.0 SITE DEFINED RETRIEVALS 9.1.1 EXPLANATION OF EXTSIT C) 105 FIFTC (a key for the FI record) is set equal value of FTFTC which was determined above. to the 106 IBOFI4 is called to obtain the first FI record via access path FI4 (FIFTC). If there are none, OK is set to FALSE. If one is found, OK is set to TRUE. 107 If OK is FALSE, control goes to the ENDIF in line 116, . and returns to the calling routine. 108 IBFFIDI is called to obtain the first DI record corresponding to the FI record which was just obtained (either in line 106 or 114). If there are none, OK 1S set to FALSE. If one is found OK is set to TRUE. 109 If OK is 110 EXTWRI is called with the parameter NUM. EXTWRI checks the DI record to see if the data should be in the user's retrieval list. File permissions are checked, application data types, and engineering categories, depending on if there were any ADT or EDT task parameters on the task which called this routine. If the record is acceptable, data information is written to file EEEDL9, and NUM is incremented. 111-112 IBNFIDI is called to obtain the next DI record corresponding to the current FI record. If one is found, OK is set to TRUE. If none are found, OK is set to FALSE. Control then goes to line 109 (statement number 300). 114-115 Once all of the corresponding DI records are found for an FI record, IBEFI4 is called to find another FI record which has the same FIFTC field. If one is found, OK is set to TRUE. If not, OK is set to FALSE. Control then goes to line 107 (statement number 200). false, control goes to the ENDIF in line 113. 9.1.2 EXPLANATION OF EXFSIT o The second routine listed will do further extractions (option 5 of the RETRIEVAL OPTION menu). It is basically the same as EXTSIT with a few exceptions: 9-10 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 9.0 SITE DEFINED RETRIEVALS 9.1.2 EXPLANATION OF EXFSIT Lines Explanation 224-226 Rather than obtaining data records based on criteria, further extractions read the current list of data records, and compare them against the criteria given. All retrievals write records to the file EEEDL9. This routine reads record information off the EEEDL9 file. 227 EDL obtains the DI record based on the DIEDN read from EEEDL90 The only reason the record would not ·be there is if it had been purged, or there was something wrong with the database. If the record cannot be found, OK is set to FALSE by the IBODIO routine. 228 If OK was set to FALSE, the routine ERRIB is called to display the reason that the error occurred. ERRIB is used to display errors which occurred in the IB routines. ERRIB is used in EDL when there should. not be an error, but the information may be of use in tracking down problems in code, or in the database. 232-235 If ~he FIFTC record for the file which the data is on is the same as FTFTC entered by the user, the record is written to file EEEDLI0 and NOM is incremented. 240 When the routine terminates, if NOM is returned to the calling routine as greater than 0, file EEEDLlO is copied over EEEDL9, giving a new selection list. If NUM is zero, meaning that no records met the new criteria, the original EEEDL9 file is left alone. 9.2 THE MENU DATABASE TRANSACTION FILE The menu data base transaction file shown below will update the EDL Menu database by: 1. Adding another line to the retrieval option menu. Note that the option value (OV) is SITE. EDL checks for this value when processing the retrieval menu. 2. Adding the prompt ENTER THE FILE TYPE CODE, LIST, OR CR TO RETURN and associated HELP messages, should the user c 9-11 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY CUSTOMIZATION GUIDE NOS 2 Level 642A 1~2.3 9.0 SITE DEFINED RETRIEVALS 9.2 THE MENU DATABASE TRANSACTION FILE enter HELP for this prompt. 3. Adding the error message THE FILE TYPE IS NOT EDL. KNOWN TO 4. The same is done for secondary retrievals. 0 A OM A OK A OV EXTRAC EXTRAC EXTRAC A MI AMH AMH AMH AMH EXTSIT1 EXTSIT1 EXTSIT1 EXTSIT1 EXTSIT1 PROMPT A MI EXTSIT2 ERROR A OM A OK A OV EXFRAC EXFRAC EXFRAC A MI AMH AMH AMH AMH EXFSIT1 EXFSIT1 EXFSIT1 EXFSIT1 EXFSIT1 PROMPT A MI EXFSIT2 ERROR 13FILE TYPE CODE 13FTC 13 1SITE ENTER THE FILE TYPE CODE, LIST, OR CR TO RETURN 1THE FILE TYPE 'CODE IS DEFINED BY THE SITE TO DESCRI 2USE OF A PARTICULAR TYPE OF FILE. ENTER "LIST" TO 3A LIST OF POSSIBLE FILE TYPES. 4A CARRIAGE RETURN WILL RETURN TO THE RETRIEVAL METH THE FILE TYPE IS NOT KNOWN TO EDL 13FILE TYPE CODE 13FTC 13 1SITE ENTER THE FILE TYPE CODE, LIST, OR CR TO RETURN 1THE FILE TYPE CODE IS DEFINED BY THE SITE TO DESCRI 2USE OF A PARTICULAR TYPE OF FILE. ENTER "LIST" TO 3A LIST OF POSSIBLE FILE TYPES. 4A CARRIAGE RETURN WILL RETURN TO THE RETRIEVAL METH THE FILE TYPE IS NOT KNOWN TO EDL 9.3 LOADING ROUTINES INTO EDL Create a new EDL absolute by entering: BEGIN,LOADEDL,E120PRC,F=ovfil,ULIB=library. o OVFIL is the file containing OVCAPs to be added to EDL. LIBRARY is the name of library containing routines to be loaded into EDL. In this case, there have been no OVCAPs added. If the routine had been put onto a library called EDLLIB, the procedure would be run as follows: -_._--_._-_._._-_.. _... _ - - - - - - - - - - - - - 9-12 CONTROL DATA CORPORATION 1985/12/31 . ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 9.0 SITE DEFINED RETRIEVALS 9.3 LOADING ROUTINES INTO EDL BEGIN,LOADEDL,E120PRC,F=NONE,ULIB=EDLLIB. This procedure takes the current file E120ABS, changes E12XABS, and creates a new E120ABS. it to 9.4 UPDATE EDL FOR THE MENU DATABASE TRANSACTION FILE Enter EDL using an ID with SYSADMIN privileges (Like EDLID). 1. Choose ADD ENINFORMATION FOR ENGINEERING DATA (task command ADDINFO. a. The APPLICATION DATA TYPE is EDL MDB TRANSACTIONS. b. Give the data a meaningful name, like MDB TRANSACTIONS TO ADD A SITE DEFINED RETRIEVAL 2. Enter the task command MENUMGMT. a. Retrieve the data which you just entered into EDL. b. Select that data, and the changes will be automatically entered into EDL. 10-1 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE ' NOS 2 Level 642A 10.0 INTERFACING APPLICATIONS 10.0 INTERFACING APPLICATIONS 10.1 EDL LOG FILE () When a standard ICEM application creates, modifies, or deletes data, it creates a log entry on local file EDLLOG, to inform EDL that it should update' the EDL database and prompt the user for additional descriptive information. You may wish to interface other applications at your site to EDL in the same manner. 1. Modify the application program to create the EDLLOG file. 2. In each task that executes your application, include a task process record (TP} for the ovcap XLOG. Pos 1 Len 1 Type Description (changed), (added) , C Action code, A C (deleted) , F (file copied), P (purged file), 2 9 16 7 7 20 20 70 10 C C C C C 110 D R (retrieved)~ 36 56 126 Permanent file name NOS User name of the file File Type Code Application Data Type Code Data Name Secondary Identifier (e. g. Sheet Number) 10.2 EEEDLFN FILE o On local file EEEDLFN, EDL which EDL has attached. files for EDL can use this data it writes to attached maintains a list of all local files An application program creating log file to determine PFN's and UN's of permanent files. Within EDL ovcaps, you should use the utility routines LOCATT, 10-2 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 10.0 INTERFACING APPLICATIONS 10.2 EEEDLFN FILE LOCINQ, and LOCRET to manipulate this file. These subroutines are documented in the EDL UTILITY ROUTINES section. col col col col col col 1-7 8-14 15-21 22 23-42 43 L9~al File Name. Permanent File Name. NOS Username of the permanent file. Mode, "R" for read, "w" for write. File Type Code Defaul t .flag, "T" if EDL attached the user's default file, "F" otherwise. file as a 10.3 RETRIEVAL ,TASKS For each type of data processed by your application, you should write a retrieval ,task for that application data type. Include the name of the task in, the ATTNA field when the Data Type is defined, so that EDL will be able to retrieve that type of data with the RETRIEVE task. C 1 ,I A retrieval task's function is to bring up data selected from a standard EDL retrieval list in an appropriate application program in a mode that allows the user to view the data, and to modify it if the user has write permission. An example of the' standard EDL retrieval task for retrieving an ICEM DDN drawing is task RET-DRW, which is in the EDLLIST file. STORE SETTING ATADT ATNAM ATFTC ATSIDR ATTNA $DRAWING$ $DRAWING$ $DRAWING FILE$ $T$ $RET-DRW$ *END A A A A A A A A A A A TI TP TP TV TV TP TV TV TV TP TP RET-DRW RET-DRW RET-DRW RET-DRW RET-DRW RET-DRW RET-DRW RET-DRW RET-DRW RET-DRW RET-DRW 20VCAP 40VCAP 4 4 5CCL PROC 5 5 5 6TASK 8TASK XDDNPRE XATTACH lAPPNAME 2REQFILE RETDDN 1NAME 1 3NAME 2 5SHEET DDNPROC DDNPOST CONSTANT CONSTANT IC DR VARIABLE VARIABLE VARIABLE NA NA SH C\! 11-1 CONTROL DATA CORPORATION (" 1985/12/31 .,-.," ~) ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 11.0 CUSTOMIZING THE PLOTTING INTERFACE 11.0 CUSTOMIZING THE PLOTTING INTERFACE The plotting interface supplied on the EDL release tape must be modified to work correctly at your site. The option menu named PLOTN1 shows the user which plotters are available at the site. Use MDB transactions to update this menu. The OVVAL field should contain a site defined destination code which is eventually passed to procedure PLOTN as the DEST parameter when the user chooses a particular plot destination. C) o Procedure PLOTN in E120PRC is designed to convert a Neutral Picture File (NPFILE) to plotter specific representation and route it to the plotter. It should be edited to execute UNIPOST with the correct directives for the specific plotters at your site, and to route the plot file to the correct plotter depending on the value of the DEST parameter. See the UNIPLOT manual for details about which directives are appropriate for your plotters. 12-1 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.0 PROGRAM "AND USER INTERFACE This section describes the standard first level interface routines to the EDL database and the user for EDL programs and customized site-developed FORTRAN code. These routines work within EDL overlay capsules. Calling them from other external programs may not work because common "blocks need to be initialized by EDL. 12.1 INFORMATION BASE (IB) ROUTINES The Information Base routines allow EDL overlay capsules perform database accesses and updates at the record level. IBSxx IBMxx IBDxx IBOxxn ~BAxxn IBExxn IBFxxn IBNxxn IBFxxyy IBNxxyy IBCPRC IBCCMT IBCDRP c Argument STATOK Type Logical to Store record xx. Modify record xx. Delete record xx. Obtain record xx via access path xxn. (Approximate) Obtain record xx or next higher via access path xxn. (Equivalent) Obtain the next duplicate record xx via access path xxn. Obtain the first xx record ordered by access path xxn. Obtain the next xx record ordered by access path xxn. Obtain the first member within coset xxyy. Obtain the next member within coset xxyy. Start a concurrency parcel. Commit a concurrency parcel. Drop a concurrency parcel. I/O o Description Status of the operation TRUE - operation was successful. FALSE - operation failed. 12-2 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES 12.2 EDL UTILITY ROUTINES SUBROUTINE ACQUIR ( LFN, PFN, UN, MODE, STAT ) Call parameters Argument Type I/O Description C*(*) LFN Local File Name I C*(*) PFN Permanent File Name I C*(*) UN NOS Username I C*(*) MODE I Mode, R or W The routine ACQUIR is used to attach or get a file. The file is tracked in the EDL local file list. If the file is already attached to the job with a different local name, it is returned and reattached. Error messages are printed if the file is busy, has been archived, cannot be attached, or if a PF error occurs. SUBROUTINE ACQUIX ( PFN, UN, EXIST) Call parameters Arg~ment Type I/O Description PFN C* (*) I Permanent File Name UN C*(*) I NOS Username EXISTS L o True if the file is found False if the file is not on the system or is not permitted. c This routine attempts to attach and return a file to see if it exists. It exists if it can be attached in read mode or if it is busy. SUBROUTINE CHKPER ( MODE ) Call parameters Argument Type I/O MODE C*(*) o Description mode the user is permitted to the f i Ie •. (I, R, W, N) Routine CHKPER checks whether the running user is permitted to the file in the FI record common block. SUBROUTINE COPYF (I,J) Call parameters Argument Type I/O Description c' 12-3 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES I J I I I o Unit to be copied from Unit to be copied to Routine COPYF rewinds both file I and J, and copies the contents of file I to file J. EDL then rewinds both files, and writes an End-of-file mark on file J. Both units I and J must be open text files with line lengths of no more than 140 characters. (FO=SQ,RT=Z,BT=C,FL<=140) SUBROUTINE CSCRN No Parameters Routine CSCRN is used to clear the screen of a non-scrolling terminal or to reset the number of lines available for a scrolling terminal. FUNCTION CUTNAM(NAME) Call parameters Argument Type I/O NAME C*U') I CUTNAM C* (*) o Description EDL Data Name Partial drawing name / sheet # Function CUTNAM returns as many characters as possible of the drawing name, followed by a space, a slash, a space, and the sheet number, into a field of the size specified in the calling routine.. For example, if CUTNAM is declared as 20 characters long in the calling program, and the sheet name consists of 2 characters, CUTNAM will return the first 15 characters of the drawing name~ followed by , / and then the sheet number. If the drawing name does not have 15 significant characters, CUTNAM will compress the result. SUBROUTINE CUTSTR ( INSTR, REMSTR, LENGTH, ALIGN ) Call parameters Argument Type I/O Description INSTR C* (*) I/O Input string REMSTR C* (*) o Remainder of the string LENGTH I I Length input string should be cut to ALIGN I I Leftmost position to check for a blank o Routine CUTSTR cuts the input string (INSTR) at a blank so the resulting input string is less than the specified length. The remainder of the string is returned in (REMSTR). Align is farthest position to left to check for a blank. If no blank ._--.- ------ 12-4 ' CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES is found, the line is split at the specified length. EXAMPLE INSTR = 'THIS IS A SAMPLE OF AN INPUT STRING' ALIGN = 10 LENGTH = 26 RESULTING INSTR = 'THIS IS A SAMPLE OF AN' RESULTING REMSTR = 'INPUT STRING' SUBROUTINE ERR ( MNA ) Call parameters Argument . Type I/O MNA C*(*) I Description Message name of the error message The routine ERR displays an error message on the user's terminal. If no error message with the given message name is found in the menu database, the following message is printed. EDLDOOO EDL INTERNAL ERROR CODE sys SUBROUTINE ERRIB No parameters Subroutine ERRIB prints an error message corresponding to the IMF diagnostic for the error which occured on the last database operation. If the last database operation was a constraint violation, ERRIB returns the last diagnostic code. If the last database operation was not a constraint violation, EDBE prints the message for error "EDLxxOOO", where xx is the IMF status code. Example: CALL IBSDI ( OK ) IF ( .NOT. OK ) THEN CALL ERRIB ENDIF SUBROUTINE ERR IBM No Parameters Subroutine ERRIBM functions like ERRIB for the Message and Task database operations. 12-5 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES SUBROUTINE ERRSTR ( MNA ) Call parameters Argument Type I/O MNA C*(*) I MSG. C*(*) o Description Message name of the error External error message string The routine ERRSTR returns a character string containing an external error code and message. If no error message with the given system code is found in the menu database, the following message is printed. EDLDOOO EDL INTERNAL ERROR CODE sys c) SUBROUTINE EXFSIT ( NUM ) Call parameters Argument Type I/O NUM, I o Description Number of records retrieved. Subroutine EXFSIT is a dummy routine. A site may replace this routine with their own routine to refine data lists based on their own further selection criteria. SUBROUTINE EXTSIT Call parameters Argument Type NUM I I/O o Description Number of records retrieved. Subroutine EXTSIT is a dummy routine. A site may replace this routine with their own routine to extract data lists based on their own criteria. SUBROUTINE EXTLIM No parameters C) Subroutine EXTLIM initializes a common block which holds the TV parameter engineering data selection criteria limits which are checked by subroutine EXTWRI before writing data on the data retrieval list. The TV parameters used by this subroutine are documented with ovcap XEXTRAC in the section EDL Standard Overlay Capsules. If you write your own extraction ovcap to prepare a retrieval list to be passed to the XDISPLA ovcap, you will need to call 12-6 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES EXTLIM once before any calls to EXTWRI. SUBROUTINE EXTWRI ( MNA ) Call parameters Argument Type I/O NUM I I/O Description Incremented if info is written on the retrieval list. Subroutine EXTWRI writes data information to the data retrieval list if the data in the DI record matches the limits specified by TV parameters and if the data is permitted to the user. It is intended to be used to create site defined retrieval lists. FUNCTION FULLNM ( USR ) Call parameters Argument Type ,I/O USR C,., (*) I FULLNM C*(*) o Description EDL ID first, middle and last name Function FULLNM reads the UI record of the specified EDL ID, and returns the corresponding last, first and middle name in the form: ADAMS, JOHN QUINCY If the first or middle name consists of only one, character (that is, an initial) FULLNM places a period after that character: ADAMS, JOHN Q. FUNCTION FULPER (MODE) Call parameters Argument Type I/O MODE C*(*) I FULPER C* (*) o Description one character file permission spelled uut file permi~sion Function FULPER spells out a single character permission (W, R, I, or N) to (WRITE, READ, INFO or NONE). SUBROUTINE GETPRM ( PRM, VAL, OK ) Call parameters Argument Type I/O Description PRM C* (,'t) I Task process parameter name mode 12-7 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES VAL OK c*(*) L o o Value of the parameter true - parameter returned false - parameter not found Routine GETPRM gets the value of a task process parameter and returns it to the program. The parameter ( from the TV record ) may be a constant, variable, or prompt. SUBROUTINE GETPRN ( VAL, OK ) Call parameters Argument Type Description I/O VAL C*(*) o Value of the parameter OK L o true - parameter returned false - parameter not found Routine GETPRN gets the next value of the task process parameter defined by GETPRM and returns it to the program. The parameter ( from the TV record ) may be a const~nt, variable, or prompt. SUBROUTINE GETUN ( UN ) Call parameters Argument Type I/O C*(*) UN 0 Description Running Nos Username Subroutine GETUN returns the NOS Username currently running. SUBROUTINE GETVAR ( NAME, VALUE, FOUND ) Call Parameters Argument Type I/O Description NAME C*(*) Parameter name I VALUE C*(*) o Parameter value o FOUND L True - the global was found variabl~ Subroutine GETVAR returns the value of the EDL global variable to the program. C) SUBROUTINE INFNA ( MNA, HOS, SAMEUN, PFN, FUN, OK ) Call parameters Argument Type I/O Description MNA C* (*) I Message Name 12-8 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A ........" .. ' 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES HOS SAMEUN C*(*) L I I PFN FUN C*(*) C*(*) o o Host Id True - the file must be on the running Username False - INFNA should prompt for UN Permanent File Name Username of the file Routine INFNA prompts for a syntactically valid file 'name the host. for SUBROUTINE ININT ( MNA, IRESP, OK ) Call parameters Argument Type I/O Description MNA C*(*) Message name for the prompt I IRESP I o Integer response from the user OK L o Status Code True - user entered a positive integer False - user entered a null response. The routine ININT displays a prompting message, asks the user to enter an integer number, and returns the value the user enters. If the parameter MNA is not the message name of a valid Prompt in the menu database, an error message is displayed on the user's terminal instead of the prompt, but the user is still asked to enter an integer. If the user enters anything but an integer or null carriage return, an error message is printed and the user is asked to reenter his response. SUBROUTINE INOPT ( MNA, OK ) Call parameters Argument Type I/O MNA C*(*) I OK L o (" Description Name of the option menu to be displayed Return status True- OK, user selected an option False-User entered a null return or the menu could not be displayed --------------------- 12-9 C) CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES Routine INOPT displays an option menu and prompts the user for his selection. If the user enters a null response, the first line of the menu is chosen by default. This routine positions the option menu line record to the line selected by the user. The variable values corresponding to the chosen option can be retrieved by the routine OPTVAL after INOPT has been called successfully. If the option menu has only one set of variables ( parameters ), it is recommended that INTXT be used instead of INOPT and OPTVAL to display the menu and return the single variable value. SUBROUTINE INP ( TXT, ICH ) Call parameters Argument Type I/O TXT C* (*) o o ICH I Description Next user response Number of characters in response Routine INP Returns the user's input to the program. It manages The EDL type-ahead buffer, by returning only a single delimited response per call, and by issuing a read request when the input buffer is empty. INP will not prompt the user. Usually a routine such as INTXT, INYN or ININT is used to prompt the user as well as return the response. SUBROUTINE INREAL ( MNA, XRESP, OK ) Call parameters Argument Type I/O Description MNA C.,'r <"~) Message number I o XRESP Real Real Number Value o OK L True - the user entered a real False - Null response The routine INREAL displays a prompting message, asks the user to enter a real number, and returns the value the user enters. If the parameter MNA is not the message name of a valid Prompt in the menu database, an error message is displayed on the user's terminal instead of the prompt, but the user is still asked to enter an integer. If the user enters anything but an valid real number or null carriage return, an error message is printed and the user is asked to reenter his response. 12-10 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES SUBROUTINE INTXT ( MNA, TXT, ICH ) Call parameters Argument Type I/O Description . MNA C*(*) Message name of the prompt I TXT C*(*) o User response string o Number of characters ICH I Routine INTXT is used to prompt the user and return a text string to the calling program. MNA may be the name of either a prompt or an option menu. If MNA is a prompt, the user enters a text string. If an option menu, the first variable value of the menu line the user picks is returned in TXT. ICH will indicate the number of characters returned in TXT. If the user enters a null carriage return, TXT will be blanked and ICH will be O. If the user enters a blank line, ICH will be 1. If MNA is not a valid prompt or option menu, an error message will be printed but the user will still be required to enter a text response. The·following example subroutine will prompt the user with the message M1, and write the user's responses to lfn TAPE30. c 10 SUBROUTINE A CHARACTER * 50 RESP INTEGER ICH OPEN(30,FILE='TAPE30') enter text or cr to return CALL INTXT ( 'M1', RESP, ICH) IF ( ICH .GT. 0 ) THEN WRITE(30,11) RESP GO TO 10 ENDIF CLOSE (30) RETURN END SUBROUTINE INYN ( MNA, YES ) Call parameters Argument Type I/O MNA C*(*) I YES L o Description Message name of the prompt Response True - "Y" or "YES" Fa1se- "N", "NO" or null cr - -------------------- - - - 12-11 CONTROL DATA CORPORATION 1985/12/31 ICEK ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES The routine INYN prompts the user to enter a YES or NO response. If MNA is not a valid prompt message, an error message is displayed, but the user is still prompted to enter "y" or "N". If the user enters anything but a null carriage return, j,y", "YES", "N", or "NO", an error message is displayed and the user is reprompted. CHARACTER FUNCTION LEFTJ(NUMBER) Call Parameters Argument Type I/O Description NUMBER I Number to be left justified I LEFTJ C* (*) Resulting left justified string o Function LEFTJ converts character string. a number into a left justified SUBROUTINE LFSTAT ( LFN, OK ) Call parameters Argument Typ"e I/O Description LFN C* (*) Local File Name I OK C* (*) o true if the file is local The routine LFSTAT determines whether a file is local. SijBROUTINE LIST ( MNA, INFO ) Call parameters ARQUMENT TYPE I/O Description MNA C*(*) Name of message menu for title I INFO C* (*) Text to be concatenated to message I Routine LIST concatenates a title (from the menu database, just give it the menu name) and its description and print it as a list. It only lists one line each time it is called. The position of the alignment is determined by the end of the title in the menu database. EXAMPLE of list created with calls to "LIST" o code segment CALL LIST ( 'LSTUSR1', UIUSR) CALL LIST ( 'LSTUSR4', UVOUN) CALL LIST ( 'LSTUSR5', UIDPT) 12-12 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES resulting terminal output EDL USER ID CADDATDEV NOS USER NAME GL0234F DEP AR THENT 9087 .. SUBROUTINE LOCATT ( LFN, PFN, FUN, MODE, DEF ) Call parameters I/O Description Argument Type C,'t (*) I Local File Name LFN C*(*) I Permanent File Name PFN C*(*) FUN Username of File I C*(*) MODE Mode, R or W I I DEF L TRUE if the file was attached as a default file, or should be automatically returned by the XLOG ovcap • . Routine LOCATT adds a local file to the list of EDL l-qcal files. It should be called every time a file is attached. It is probably more convenient to call the ACQUIR routine to attach the file. ACQUIR calls the ATTLOC routine after it attaches the file. SUBROUTINE LOCINQ ( LFN, PFN, FUN, MODE, FTD, DEF ) Call parameters Argument Type ~/O Description LFN C*(*) I Local File Name PFN C* (*) o Permanent File Name FUN C*(*) o Username of File MODE C* ("') o Mode, R or W FTD C,'t (,'t) o File Type Name DEF L o True if the file was attached as a default file or will be returned by the XLOG ovcap. Routine LOCINQ returns information about a local file. SUBROUTINE LOCRET ( LFN ) Call parameters Argument Type I/O C*(*) LFN I Routine Description Local File Name LOCRET removes the information about a returned local , ..... oa. _ _ .. .' 12-13 (~~.\ "-.j CONTROL DATA CORPORATION 1985/12/31 ICBM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES file from the EDL list of local files. called every time a file is returned. FUNCTION LSTCHR ( STR ) Call parameters Argument Type I/O STR C* (*) I LSTCHR I o LOCRET should be Description String to be examined Position of the last non-blank character in STR Function LSTCHR works backwards from the end of a string to find the last non-blank character. This function can be used when you need to concatenate strings. SUBROUTINE MSG ( MNA ) Call parameters Argument Type I/O MNA C*(*) I Description Message name of desired message. The routine MSG displays a message on the user's terminal. If MNA is not the message name of a valid message in the database, an error message is printed. SUBROUTINE MSGSTR ( ~A, MSG ) Call parameters Argument Type I/O Description MNA C* (*) I Menu name of desired message MSG C* (*) o Message Text Routine MSGSTR returns the message text string. If MNA is not a valid message name, an error message is returned in MSG. This routine can be used to obtain a customizable "constant" from the message and task database. 0 SUBROUTINE NXTEDN ( HOS, EDN, OK ) Call parameters Argument Type I/O Description C*(*) HOS I Host identifier EDN I 0 Next unused data identifier for the host OK L 0 Status Code, True if,no error 12-14 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES Subroutine NXTEDN finds the next available data identifier for the host. It is used to find the correct DIEDN value before adding a new DI record. The code sequence from calling NXTEDN to storing the new DI record should be enclosed in a parcel to prevent a different job from creating a DI record with the same EDN. SUBROUTINE NXTFIL ( HOS, FIL, OK ) Call parameters Argument Type I/O Description HOS C* (*) I Host identifier FIL I o Next unused file identifier for the host OK L o Status Code, True if no error Subroutine NXTFIL finds the next available file identifier for the host. It is used to find the correct FIFIL value before adding a new FI record. The code sequence from calling NXTFIL to storing the new FI record should be enclosed in a parcel to prevent a different job from creating a FI record with the same EDN. SUBROUTINE OPTVAL ( POS, VAL, OK ) Call parameters Argument Type I/O Description POS I I Option variable position VAL C*(*) o Value of the option variable OK L o Status True - A value was returned False- No variable in the position Routine OPTVAL returns the value of an option variable which is associated to an option menu line selected by the user. The routine INOPT should have been successfully called before OPTVAL. If no option variable in the indicated position exists, VAL unchanged and OK is set to False. SUBROUTINE PAUSE No Parameters Routine PAUSE displays the message ENTER CR TO CONTINUE, and - ----------------- - -- --- ---------------- ---- -- -------- - ------------------------------------------------- -- - - - - - --------------- 12-15 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES waits for the user to enter something. Any input is ignored. This routine can be used to allow a user to read a list of information before the next group of information scrolls it off the screen. SUBROUTINE POPT No Parameters Routine POPT pops and discards all rema1n1ng processes of the current task from the execution stack. It is used to inhibit processing of succeeding processes when an error or condition is found that makes subsequent task processing meaningless. (--, ~ ) SUBROUTINE PUTNAM ( DINAM, DISID ) Call Parameters I/O Description Argument Type C*(*) Data name I DINAM Sheet number DISID I I Subroutine PUTNAM user PUTVAR to store the name in DINAM in parameters NAMEI and NAME2, and DISID in parameter SHEET. This routine is used because a parameter value is limited to 40 characters, and the sheet number must be converted to a character string and left justified. This routine takes care of all that. SUBROUTINE PUTNA2 ( DINAH, DISID ) Subroutine PUTNA2 acts like PUTNAM except it sets parameters NAMEI2,NAME22, and SHEET2. SUBROUTINE PUTVAR ( NAME, VALUE ) Call Parameters Argument Type I/O Description NAME C,'t (1") Variable name to set I VALUE C*(*) Variable value to set I Subroutine PUTVAR stores variable NAME. VALUE is VARIABLE type parameter, used. the value VALUE in EDL global returned when EDL looks for a or when the GETVAR subroutine is "12-16 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES The NAME parameter should be a character string 10 characters or less. Only 40 characters of the VALUE parameter are stored. SUBROUTINE RETLIS(N,HEADER,VALUE,OK) Call Parameters Argument Type I/O Description N I The number of records on EEEDL12 I HEADER C* (*) I The message identifier for the table header C*(*) VALUE The value chosen by the user o OK o TRUE if the user made a choice L FALSE if the user chose EXIT Subroutine RETLIS displays a selection list to asks for a choice. the user and The selection list must be prepared by the calling program on Fortran unit 12 in a special way. The following example "code displays a list of all part numbers in the database. Note that this is an unrealistic example, since in a production environment, such a list would be too long to use effectively. C (include the PI common blocks from EDLCOM) LOGICAL OK, OKPI OPEN (12, F'ILE=EEELIS ,RECL=202, BUFL=65) CRECL must be at least the length of parameter VALUE + 132 C in this case, length of PIPRT + 132 = 202. C BUFL should usually be kept as small as possible to C conserve memory, especially for short lists. C =0 CALL IBPIO ( OKPI ) CONTINUE IF ( OKPI ) THEN N=N+ 1 WRITE(12,20) PIPRT, PIPRT(1:30),PITTL FORMAT (A,A,A) CALL IBNPIO ( OKPI ) GO TO 10 ENDIF N 10 20 C CALL RETLIS (N, 'HEADER1', PIPRT, OK) C · -.- ..-... - _._._- .._.. _.... - _•.. _-._... _-_. --- 12-17 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES C C C C C C C o o IF ( OK ) THEN The user chose the line containing the first 30 characters and the title of the part number returned in PIPRT. ELSE The user exited without a choice ENDIF CLOSE (12) Be sure to close unit 12 to release the file buffer. Otherwise memory fragmentation will occur and EDL may abort later because of insufficient MFL. Subroutine RETLIS processes the information on file EEEDL12 in the following manner: 1. The message 'N SELECTIONS' is printed, where N is the parameter above. 2. The message specified by HEADER is printed. 3. Each record on unit 12 is read. 4. The first I characters on each line (where I=len(VALUE» are ignored. 5. The next 132 characters on the line are printed with a sequence. number in front. i. e. "1. ADAMS, JOHN Q" 6. After NL lines are displayed (where NL is the number of lines on a screen), or the end of the list is reached, EDL prints the message: "ENTER A NUMBER, E OR EXIT TO EXIT,. OR CR FOR MORE" 7. If the user: A. Enters a number J EDL rewinds EEEDL12 and reads VALUE from the Jth line of the file. B. Enters a null response EDL prints more of the list. If the list was ended, it is started over. C. Enters "E" OK is set to FALSE and control returns to the calling routine. 8. However, if the list contains only one possible selection, a null carriage return will select that single item. SUBROUTINE USRPERM ( FIL, USR, MODE) Call Parameters Argument Type I/O Description FIL I I File Identifier USR C* (*) User id I 12-18 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 12.0 PROGRAM AND USER INTERFACE 12.2 EDL UTILITY ROUTINES MODE C*(*) I Mode R,W,I Routine USRPERM issues a permit for the file and user in the indicated mode. The combinations of group permits and file categories are considered before issuing the appropriate file permit to the operating system. c 13-1 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A' 13.0 UPDATE THE MESSAGE AND TASK DATABASE ---------~-------------------------------------------- -------------- 13.0 UPDATE THE MESSAGE AND TASK DATABASE 13.1 INTRODUCTION 0'" \ This task allows the administrator to perform task and message customizations to EDL. It operates by reading transaction records from a sequential input file which has been prepared by the administrator using a text editor such as FSE. The administrator should save all transaction files which have been applied to the default menu database, so that they may be re-applied when a new version of EDL is installed at the site. There have been no changes to the message and task database structure between EDL 1.2.0 and EDL 1.2.3. Previous transaction files should work without major changes. However, some standard tasks have been reorganized, so if you have added task processes into existing EDL tasks, you should inve~tigate whether the changes can still be applied correctly. Another change is that the TITYP field is now being used to restrict tasks in a multi-host network. Set TITYP to "MASTER" if the new tasks are administrative tasks which should be run only on the master host. 13.2 APPLYING TRANSACTION DATA o The standard data selection task is used to select the transaction file which is to be applied to the current running database. The transaction data must have been previously saved in EDL with file type "UPPER CASE TEXT FILE" and application data type "EDL MDB TRANSACTIONS" data. If the user exits without selecting a transaction data set, control returns to the previous task. Otherwise, the menu database is updated, and EDL displays the following 13-2 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 13.0 UPDATE THE MESSAGE AND TASK DATABASE 13.2 APPLYING TRANSACTION DATA confirmation message *** FINISHED PROCESSING MDB TRANSACTIONS *** *** PROCESSING DETAILS ARE ON LOCAL FILE MDBLIST *** The user should check the messages on the MDBLIST file by routing it to a printer or by examining it with a text editor. 13.3 TRANSACTION FILE FORMAT The format of the transaction file or the schema of the message and task database has not changed between EDL 1.2.0 and EDL 1.2.3. All transaction records have a transaction code in column 1. The code is "A" for adding new records, "c" for changing records which already exist, or "D" for deleting records. Columns 3-4 contain the two character· record identifier. Columns 11-120 contain the data items. In general, character fields are left justified on 10 character boundaries, and integer fields are right justified in 10 character fields. Tab settings of 3,11,21,31,41,51,61,71 will facilitate entering the data correctly using the full screen editor. Comment lines are indicated with a blank or asterisk in column 1. The information below describes what should appear on the transaction file for each type of record. The field column shows the name used by the EDLMENUW external schema. The Type column is C for character fields, I for integers, or L for logical. The Constraints column shows what may legally appear in the field. There are several kinds of constraints. Unique More than one record may not exist with the same value in the field. in the database Subset The record may not exist unless the field value matches another field value in another type of record. 13-3 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 13.0 UPDATE THE MESSAGE AND TASK DATABASE 13.3 TRANSACTION FILE FORMAT Value One of the values within quotation marks the field. must be in 13.3.1 MI (MESSAGE INFORMATION) This record is the header record for all prompts, error messages. Field Action MIMNA MITYP Type Length C 1 blank 1 C 2 blank 6 C 10 C 10 MITTL C ID menus, and Description Action Code Constraints "A","C","D" Record Id. "MI" Message Name Type Unique "PROMPT", "MESSAGE", "ERROR", "OPTION", "TASK MENU" Title Text 70 13.3.2 MH (MESSAGE HELP) These records specify the help text for the message. Field Action C Type ID C blank blank Length 1 1 2 6 MHMNA C MHLIN MHTXT I 10 10 C 70 Description Action Code Constraints "A","C","D" Record Id. "MH" Message Name Line Number Text MIMNA Unique within the menu. 13.3.3 OM (OPTION MENU LINES) o These records menu lines. specify the text which is displayed on option 13-4 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 13.0 UPDATE THE MESSAGE AND TASK DATABASE 13.3.3 OM (OPTION MENU LINES) Field Action ID OMMNA OMMLN OMTXT Type C blank C blank C I .C Length 1 1 2 6 10 10 40 Description Action Code Constraints "A","C","D" Record Id. "OM" Message Name MIMNA Menu Line Number Text 13.3.4 OK (OPTION KEYWORDS) These records specify the keywords which may be used to choose .an option menu line. Field Action ID OKMNA OKMLN OKKEY Type C blank C blank C I C Length 1 1 2 6 10 10 10 Description Action Code Constraints "A","C","D" Record Id. "OK" Message Name Menu Line Keyword OMMNA OMMLN Unique within the menu 13.3.5 OV (OPTION VALUES) These records specify the value which is returned to the program when the user picks an option from an option menu. Field Action Type Length 1 blank 1 ID C C blank 2 6 OVMNA OVMLN OVPOS C I I 10 10 10 OVVAL C 40 Description Action Code Constraints "A", "C","D" Record Id. "OV" Message Name OMMNA Menu Line OMMLN Value Position Usua11y=1, except when the option menu must return two or more values to the program. Value C~: - - - - - - - - - -..-.- ..- ....--....... - .....•..._.._._ ..• 13-5 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 13.0 UPDATE THE MESSAGE AND TASK DATABASE 13.3.6 TI (TASK INFORMATION) 13.3.6 TI (TASK INFORMATION) This record is the header for EDL Tasks. For reasons of upward compatibility, it is recommended that new, similar tasks be created when customizing EDL rather than changing the standard tasks created by CDC. TITNA TISEC Type Length C 1 blank 1 C 2 blank 6 10 C C 10 TITYP C 10 TIDSC C 70 Field Action ID C) Description Action Code Constraints "A","C","D" Record Id. "TI" Unique Site Defined Security Category Code. "MASTER" for tasks which Task Type cannot be run on subordinate hosts in an EDL database network. Otherwise, blank. Description of the Task Task Name Sec. Cat 13.3.7 TC (TASK COMMANDS) This record specifies the commands which may be used to invoke tasks. Note that the unique key field for change and delete is TCCMD, the second field, not the first. Field Action ID TCTNA TCCMD o Type Length C 1 blank 1 C 2 blank 6 C 10 C 10 Description Action Code Constraints "A","C","D" Record Id. "TC" Task Name Command TITNA Unique 13-6 CONTROL DATA CORPORATION 1985/12/31 ICEH ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 13.0 UPDATE THE MESSAGE AND TASK DATABASE 13.3.8 TM (TASK MENU LINES) 13.3.8 TM (TASK MENU LINES) This record specifies invoke tasks. Field Action ID TMMNA TMMLN TMTXT TMTNA Type C blank C blank C I C C Length 1 1 2 6 10 10 40 10 th'e menu lines which can be used to Description Action Code Constraints "A", "C","D" Record Id. "TM" Message Name Menu Line Text Task Name MIMNA Unique within the menu TITNA 13.3.9 TP (TASK PROCESSES) These records specify the parts of tasks, called processes, which are executed sequentially when a task is invoked. Field Action Length 1 1 TPTNA TPSEQ TPTYP Type C blank C blank C I C TPNAM TPFNA C C 10 unused TPFUN C ID 2 6 10 10 10 7 3 7 Description Action Code Constraints "A","C","D" Record Id. "TP" Task Name TITNA Sequence NumberUnique within the task P~ocess Type "TASK MENU", "OVCAP" , "CCL PROC", or "TASK" Name of Process File Name For CCL procedures only, PFN of the Procedure file. File Username For CCL procedures only, NOS Username of the procedure file. c.: 13-7 C--") ~/ CONTROL DATA CORPORATION 1985/12/31 IeEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 13.0 UPDATE THE MESSAGE AND TASK DATABASE 13.3.10 TV (TASK PARAMETER VALUES) 13.3.10 TV (TASK PARAMETER VALUES) These records specify the param,eters which are passed to eCL Procedures and EDL overlay capsules when they are executed as EDL task processes. Task parameters can also be used to answer prompts issued by EDL ovcaps. Task parameters are one of 5 types. CONSTANT The constant in the TV VAL field process. NULL A null response is passed to the process. This is equivalent to a carriage return with no other characters on the line. PROMPT A menu or prompt with message name ~VVAL is used to 'prompt the user for the value of the parameter. passed to the VARIABLE The value of an EDL global variable with name TVVAL is passed to the process. The variable must have been previously initialized by an EDL ovcap. CONFIG The parameter value passed to upon the user's terminal procedures only) TRANSFER All of the standard variable parameters for transfer tasks are passed to the process. (CCL procedures only) Field Action TVTNA TVSEQ TVPOS TVPRM Type C blank C blank C I I C Length 1 1 2 6 10 10 10 10 TVTYP C 10 ID o is the process depends configuration. (eCL Description Action Code Constraints "A","C","D" Record Id. "TV" Task Name Sequence Nr. Parameter POSe Parameter Name TPTNA TPSEQ Unique within the process Must be an existing parameter or message name. "NULL","CONSTANT", "PROMPT" , "VARIABLE" , "eONFIG", or "TRANSFER". Type 13-8 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 13.0 UPDATE THE MESSAGE AND TASK DATABASE 13.3.10 TV (TASK PARAMETER VALUES) TVVAL C 40 Parameter Value C) 14-1 CONTROL DATA CORPORATION c~, 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.1 SUMMARY OF CHANGES BETWEEN EDL 1.2.0 AND EDL 1.2.3 Added fields HIEDL and HIHOSS and access path HI4 to the Host Information (HI) record to implement networking. Added the Communication Link (CL) record links available between hosts. to define the RHF Added the User Validation (UV) record to define which users are validated on each host. Removed the User's NOS Username field (UlUUN) from the UI record. This information is now found on the User Validation (UV) record. Added the Part Revision (PR) , Part Structure (PS) , and Units of Measure Code (UM) records to implement the Part Structure List feature of EDL 1.2.3. Added the Part Revision (PDREV) field to the Part Data Relationship (PD) record, and made the PD record dependent upon the Part Revision (PR) record instead of the Part Information (PI) record. Removed the Long File Name (FILNA) from the File Information (FI) record. Increased the length of the FIPFN field to 100 characters. Increased the length of the FIFUN field to 31 characters. These changes allow identifiers for files on any type of operating system to be stored in the same fields. o Added the Message (ME), Message Line (ML) , and Instance (MN) records to implement the Note Facility. Message 14-2 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A' \ \.. ........ " 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.2 RECORDS USED TO CUSTOMIZE EDL 14.2 RECORDS USED TO CUSTOMIZE EDL. The following subsection describes all types of Engineering Data Database (DDB) records which are used to customize EDL. These records can be updated only via Query Update. There are many other record types in the DDB which are updated while users run EDL. They are described in the next subsection. 14.2.1 AI APPLICATION INFORMATION These records define the application indicate which version is active. Field AIAPN AIAPV AISTA Type C C C Length 20 10 10 systems under EDL and Description Application Name Application Version Status, ACTIVE or INACTIVE Constraints AIAPN,AIAPV is unique Access Paths AIO by'AIAPN,AIAPV All by AIAPN, duplicates sorted by AIAPV 14.2.2 AC APPLICATION CONFIGURATION These records define parameters to be passed to the application depending on the user's terminal configuration. Field ACAPN ACAPV ACATR ACSTA ACPRM ACVAL Type C C C C C C Length 20 10 20 20 10 40 Description Application Applic. Version Terminal Attribute Terminal State Parameter Name Parameter Value ..... . - - - - - - - . --------------- 14-3 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.2.2 AC APPLICATION CONFIGURATION Constraints ACAPN,ACAPV,ACATR,ACSTA,ACPRM is unique ACAPN,ACAPV is a subset of AIAPN,AIAPV Access Paths ACO by ACAPN,ACAPV,ACATR,ACSTA,ACPRM AC 1 by ACAPN, ACAPV AC2 by ACAPN,ACAPV,ACATR AC3 by ACPRM A~4 by ACAPN,ACAPV,ACATR,ACSTA, duplicates sorted by ACPRM 14.2.3 ET ENGINEERING CATEGORIES C) These records define the engineering categories which are established by each site. Engineering Categories provide a way to describe and separate data based on how it is used in the engineering organization. Field ETEDT C Type Length 20 ETDSC C 70 Description Engineering Category Code (formerly Engineering Data Type) Description of the category (not used) Constraints ETEDT is unique. Access Paths ETO by ETEDT 14.2.4 EA ENGINEERING ATTRIBUTES These records specify which standard attributes the user will be prompted for if he or she chooses to be prompted for descriptors when updating EDL information for engineering data. o Field EAEDT EAATR Type C C Length 20 20 Description Engineering Category Attribute 14-4 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A \............. ' 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.2.4 EA ENGINEERING ATTRIBUTES Constraints EAEDT,EAATR is unique. EAEDT is subset of ETEDT Access EAO by EA1 by EA2 by Paths EAEDT, EAATR EAEDT, duplicates sorted by EAATR EAATR Cosets ETEA joins ETEDT and EAEDT, duplicates sorted by EAATR 14.2.5 FT FILE TYPES These records describe the types of files managed by EDL. Field FTFTC FTNAM FTAPN FTLFN FTLFNR "FTCHR Type C C C C Length 20 20 20 7 L C FTPRT L FTMUL L 1 "0 Description File Type Code (internal) "File Type Name (external) Application which uses this file Default Local File Name True if the default LFN is Required Character Code, D-Display Code, A-Ascii, 8-8 Bit Ascii, B-Binary Printable, True if the file has printer carriage control in column 1. Multiple Data, True if more than one data set can be on the file. Constraints FTFTC is unique FTNAM is unique Access FTO by FTI by FT2 by FT3 by Paths FTFTC FTNAM FTLFN FTAPN, duplicates sorted by FTNAM CI 14-5 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOHIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.2.6 AT APPLICATION DATA TYPE 14.2.6 AT APPLICATION DATA TYPE These records describe the types of data managed by EDL. o Field ATADT ATNAH ATFTC Type C C C Length 20 20 20 ATTNA C 10 ATSIDR L Description Application Data Type Code (internal) Application Data Type Name (external) File Type Code where this type of data resides Task Name used to retrieve this type of data (sheet) True if a secondary id is required to identify the data Constraints ATADT is unique ATNAH is unique ATFTC is a subset of FTFTC Access ATO by AT1 by AT2 by Paths ATADT ATNAH ATFTC 14.2.7 TT TRANSFER AND TRANSLATION TASKS These records specify which data tranfers are possible and the tasks used to perform the transfer. o Field TTADT1 Type C Length 20 TTADT2 C 20 TTTNA C 10 Description Application Data Type Code of the source data Application Data Type Code of the destination data Task Name which performs the transfer Constraints TTADTl,TTADT2 is unique TTADT1 is subset of ATADT TTADT2 is subset of ATADT Access Paths 14-6 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.2.7 TT TRANSFER AND TRANSLATION TASKS TTO by TTADTl,TTADT2 TTl by TTADTI TT2 by TTADT2 Cosets ATTI joins ATADT and TTADTI ATT2 joins ATADT and TTADT2 14.2.8 RT RELEASE TRANSFERS These records specify which transfers are possible during the process of releasing Engineering Data. Field RTADTI RTADT2 Type C C Length 20 20 Description Application Data Type of the source data Application Data Type of the destination data c Constraints RTADTl,RTADT2 is unique RTADTl,RTADT2 is subset of'TTADTl,TTADT2 Access Paths RTO by RTADTl,RTADT2 14.2.9 HI HOST INFORMATION These records specify the host family codes of the computer systems at your site where data resides that you want to record in EDL. Field HIHOS Type C HIOFF I HIOS HIEDL C L Length 10 10 Description Host Family ID. This field must be the logical host identifier (LID) for RHF. Identifier Offset. All File and Data ids will be offset by this number to group all data for a single host together. Operating System, NOS, NOS/VE, etc. True if the host runs EDL. C 14-7 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A -------------------------------------------------------------------14.0 ENGINEERING DATABASE RECORD DEFINITION 14.2.9 HI HOST INFORMATION HIHOSS C 10 Superordinate or master host. host for this Constraints HIHOS is unique HIOFF is unique HOHOSS is a subset of HIHOS Access HIO by Hl1 by HI2 by Paths HIHOS HIOFF HIOS duplicates sorted by HIHOS 14.2.10 CL COMMUNICATION LINKS ·0 These records specify RHF communication links. Field CLHOSS CLHOSR Type C C Length 10 10 Description Host Family Sending. Host Family Receiving. Constraints CLHOSS,CLHOSR is unique CLHOSS is a subset of HIHOS CLHOSR is a subset of HIHOS Access CLO by CL1 by CL2 by Paths CLHOSS,CLHOSR CLHOSS duplicates sorted by CLHOSR CLHOSR duplicates sorted by CLHOSS 14.2.11 UM UNITS OF MEASURE CODES These records define the valid codes or abbreviations for the units of measure field in the PS record. o Field UMUMC Type C Length 10 Description Units of Measure Code Constraints --------- __ .._._.......... __. _ - - - - ... 14-8 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A c' 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.2.11 UM UNITS OF MEASURE CODES UMUMC is unique UMO by UMUMC 14.3 RECORDS UPDATED BY EDL This subsections describes the records in the Engineering Data Database that are updated as the EDL users and administrators use EDL functions. They are described here for reference. You may wish to write Query Update reports that use these fields, or write custom~zed EDL code to read and manipulate them. 14.3.1 UI USER INFORMATION These records establish EDL usets and all relevant information about them. Field UIUSR UIPWD UISTA UIDPT UPCMD UIFIN UIMIN UILNF UITTL UIDELS UIDELD UISTR UICTY UIPHO UIEDT Type C C C C C C C C C C C C C C C Length 10 10 10 20 10 10 10 20 40 1 1 70 70 20 10 Constraints UIUSR is unique Access Paths UIO by UIUSR Description EDL Id of the User EDL Password of the user Status·, "ACTIVE" or "INACTIVE" Department First Task Command First Name or Initial Middle Name or Initial Last Name Title String Delimiter Dialogue Delimiter Street Address City,State,Zip Phone Number Editor c\ ------------------ -- ----- - -- - ----~--------------- -- - - - - 14-9 - o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.1 UI USER INFORMATION Ul1 by UILNA,UIFIN,UIMIN 14.3.2 UV USER VALIDATION These records each host. Field UVHOS UVUSR UVOUN o Type C C C track Length 10 10 31 which users are validated to use EDL on Description Host Id. EDL User Id. Operating System Username on on the Host. the user runs Constraints UVHOS,UVUSR is unique UVHOS is subset of HIHOS UVUSR is subset of UIUSR Access Paths UVO by UVHOS,UVUSR UV1 by UVHOS,UVUSR,UVOUN UV2 by UVHOS,UVOUN UV3 by UVUSR duplicates sorted by UVHOS UV4 by UVHOS duplicates sorted by UVUSR Cosets. UIUV joins UIUSR and UVUSR HIUV joins HIHOS and UVHOS 14.3.3 GI GROUP INFORMATION These records define groups of EDL users. o Field GIGRP GIGRPO GIUSRA GITTL Type C C C C Constraints Length 20 20 10 70 Description Group Id Id of the Owning Group EDL Id of the Group Administrator Group Title 14-10 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.3 GI GROUP INFORMATION GIGRP is unique GIGRPO is subset of GIGRPO GIUSRA is subset of UIUSR Access Paths GIO by GIGRP GIl by GIGRPO, duplicates sorted by GIGRP GI2 by GIUSRA Cosets GIGI joins GIGRP and GIGRP UIGI joins UIUSR and GIUSR 14.3.4 GM GROUP MEMBERS These records establish members for groups that been defined in EDL. Field GMGRP GMUSR Type C C Length 20 10 CI have Description Group Id EDL Id of the Member Constraints GMGRP, GMUSR. is unique GMGRP is subset of GIGRP GMUSR is subset of UIUSR Access Paths GMO by GMGRP, GMUSR GM1 by GMGRP, duplicates sorted by GMUSR GM2 by GMUSR, duplicated sorted by GMGRP Cosets GIGM joins GIGRP and GMGRP, duplicates sorted by GMUSR UIGM joins UIUSR and GMUSR, duplicates sorted by GMGRP already 14-11 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.5 GS GROUP SECURITY AUTHORIZATION 14.3.5 GS GROUP SECURITY AUTHORIZATION These records specify which task categories the members of the group are authorized to invoke. Field GSGRP GSSEC Type C C Length 20 10 Description Group Id Task Security Category Constraints GSGRP, GSSEC is unique GSGRP is subset of GIGRP o Access Paths GSO by GSSEC, GSGRP GS1 by GSGRP Cosets GIGS joins GIGRP and GSGRP 14.3.6 PI PART INFORMATION These· records establish the part numbers to be used in EDL. Field PIPRT PITTL Type C C Length 70 100 Description Part Number Part Title Constraints PIPRT is unique Access Paths PIO by PIPRT 14.3.7 FM FAMILY INFORMATION o These records establish the family codes to be associated with part numbers. 14-12 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.7 FM 'FAMILY INFORMATION Field FMFAM FMTTL Type C C Length 40 70 Description Family Code Family Title Constraints FMFAM is unique Access Paths FMO by FMFAM 14.3.8 PF PART FAMILY These records establish the relationships between part numbers and family codes. Field PFPRT PFFAM Type C C Length 70 40 Description Part Number Family Code o Constraints PFPRT, PFFAM is unique PFPRT is subset of PIPRT PFFAM is subset of FMFAM Access PFO by PF1 by PF2 by Paths PFPRT, PFFAM PFFAM, duplicates sorted by PFPRT PFPRT, duplicates sorted by PFFAM Cosets FMPF joins FMFAM and PFFAM PIPF joins PIPRT and PFPRT 14.3.9 VI VENDOR INFORMATION These records establish the vendor names and vendor codes to be associated with part numbers in EDL. Field VIVEN' Type C Length 20 Description Vendor Code c' !4-13 0- CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.9 VI VENDOR INFORMATION VINAM VISTR VICTY VIPHO C C C C 70 70 70 20 Vendor Name Street Address City, State, Zip Phone Number Constraints VIVEN is unique VINAM is unique Access Paths VIO by VIVEN VII by VINAM o 14.3.10 PV PART VENDORS These records establish the relationships between part numbers and vendor codes. Field PVPRT PVVEN Type Length C C 70 20 Description Part Number Vendor Code Constraints PVPRT, PVVEN is unique PVPRT is subset of PIPRT PVVEN is subset of VIVEN Access PVO by PVl by PV2 by Paths PVPRT, PVVEN PVPRT, duplicates sorted by PVVEN PVVEN, duplicates sorted by PVPRT Cosets PIPV joins PIPRT and PVPRT VIPV joins VIVEN and PVVEN o 14.3.11 PR PART REVISION These records define the revision levels for each part. 14-14 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.11 PR PART REVISION Field PRPRT PRREV PRECO PRSTA Type C C C C Length 70 10 20 10 PRAUX C 100 Description Part Number Revision Level Engineering Change Order number Revision Part Status of the (WORKING,RELEASED) Auxiliary field for site customization, not used by EDL.' Constraints PRPRT,PRREV is unique. PRPRT is subset of PIPRT Access PRO by PR1 by PR2 by Paths PRPRT,PRREV PRPRT duplicates sorted by PRREV PRECO duplicates sorted by PRPRT,PRREV Cosets PIPR joins PIPRT and PRPRT c 14.3.12 PS PART STRUCTURE These records define the structure of part assemblies. Field PSPRTP PSREV PSPRTC PSSEQ PSUMC PSQTY PSAUX Type C C C I C F C Length 70 10 70 10 100 Description Parent Part Number Revision Level of Parent Part Component Part Number Part List Sequence Number Units of Measure Quantity Auxiliary field for site customization, not used by EDL. Constraints PSPRTP,PSREV,PSPRTC is unique. PSPRTP,PSREV,PSSEQ is unique. PSPRTP,PSREV is subset of PSPRT,PSREV PSPRTC is subset of PIPRT PSUMC is subset of UMUMC Access Paths c 14-15 C,' CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.12 PS PART STRUCTURE PSO PSI PS2 PS3 PS4 PS4 by by by by by by PSPRTS,PSREV,PSPRTC PSPRTC duplicates sorted by PSPRTP,PSREV PSPRTP,PSREV duplicates sorted by PSPRTC PSPRTP duplicates sorted by PSREV PSPRTP,PSREV,PSSEQ PSPRTP,PSREV duplicates sorted by PSSEQ Cosets PRPS joins PSPRTP,PSREV and PRPRT,PRREV duplicates sorted by PS PIPS joins PIPRT and PSPRTC 14.3.13 UC USER CONFIGURATION These records define the configuration attributes. Field UCUSR UCATR UCSTA Type C C C Length 10 20 20 states for a user's terminal Description Edl Id of the User Attribute State Constraints UCUSR, UCATR is unique UCUSR is' subset of UIUSR Access Paths UCO by UCUSR, UCATR UCI by UCUSR Cosets UIUC joins UIUSR and UCUSR 14.3.14 DF DEFAULT FILES These records establish which files will be automatically attached when a user enters a specific application. Field DFUSR DFAPN Type C C Length 10 20 Description EDL Id of the User Application Name 14-16 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.14 DF DEFAULT FILES -------------------------------------~------------------------------ DFFIL DFLFN DFMOD I C C 7 1 File Number of the File Local File Name NOS Mode for the File Constraints DFUSR, DFAPN, DFFIL is unique DFUSR, DFAPN, DFLFN is unique DFUSR is subset of UIUSR DFAPN is subset of ACAPN DFFIL is subset of FIFIL Access DFO by DF1 by DF2 by DF3 by DF4 by Paths DFUSR, DFUSR, DFUSR, DFUSR, DFFIL DFAPN, DFLFN DFAPN, DFFIL DFAPN, duplicates sorted by DFLFN duplicates. sorted by DFAPN and then by DFLFN CJ 14.3.15 FI FILE INFORMATION These records establish files to be managed by EDL. Field FIFIL FIHOS FIFUN FIPFN FIFTC FIUSR FICT FIMOD FISTA FIVSN Type I C C C C C C C C C Length 10 31 100 20 10 2 1 10 6 Description File Number File Host Operating System Username Permanent File Name File Type Code EDL Id of the Owner NOS Category, "PR" or "PU" Permission Mode, "R", "W", or "I" File Status Volume Serial Number of Archive Tape Constraints FIFIL is unique FIHOS, FIFUN, FIPFN is unique FIHOS is subset of HIHOS FIFTC is subset of FTFTC FIUSR is subset of UIUSR Access Paths FlO by FIFIL 14-17 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE 'RECORD DEFINITION 14.3.15 FI FILE INFORMATION FI1 FI2 FI3 FI4 FI5 by by by by by FIHOS, FIFUN, FIPFN FIUSR, duplicates sorted by FIHOS,FIFUN,FIPFN,FILNA FIHOS, FIFUN FIFTC FIHOS Cosets UIFI joins UIUSR and FIUSR HIFI joins HIHOS and FIHOS 14.3.16 GP GROUP PERMITS These records establish file permits for groups. o Field GPFIL GPGRP GPMOD Type I C C Length 20 1 Description File Number Group Id Permission Mode, "R", "W", or "I" Constraints GPFIL, GPGRP is unique GPFIL is subset of FIFIL GPGRP is subset of GIGRP Access GPO by GP1 by GP2 by Paths GPFIL, GPGRP GPFIL, duplicates sorted by GPGRP GPGRP Cosets FIGP joins FIFIL and GPFIL GIGP joins GIGRP and GPGRP 14.3.17 UP USER PERMITS These records establish individual user file permits. Field UPFIL UPUSR Type I C Length 10 Description File Number EDL Id of the User 14-18 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.17 UP USER PERMITS UPMOD C 1 Permission Mode, "R", "W", or "I" Constraints UPFIL, UPUSR is unique UPFIL is subset of FIFIL UPUSR is subset of UIUSR Access UPO by UPI by UP2 by Paths UPFIL, UPUSR UPFIL, duplicates sorted by UPUSR UPUSR Cosets FIUP joins FIFIL and UPFIL UIUP joins UPUSR and UPUSR C:· 14.3.18 FP FILE PERMITS These records are Permit records. Field FPFIL FPUSR FPMOD Type Length I C C 10 1 the of the Group Permit and User Description File Number EDL Id of User Permission Mode, "R", "W", or "I" Constraints FPFIL, FPUSR is unique FPFIL is subset of FIFIL FPUSR is subset of UIUSR Access FPO by FPl by FP2 by result Paths FPFIL, FPUSR FPFIL FPUSR Cosets FIFP joins FIFIL and FPFIL UIFP joins UIUSR and FPUSR 14-19 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.19 PP PENDING PERMITS 14.3.19 PP PENDING PERMITS These records contain information about files for which NOS permits will be issued as soon as the owner of the file logs into EDL. Field PPFIL PPUUN PPMOD PPFUN Type Length I C C C 7 1 7 Description File Number NOS Username of the user to be permitted Permission Mode, "R", "W", or "I" NOS Username of the owner of tne file Constraints PPFIL, PPUUN is unique PPFIL is subset of FIFIL o Ac;cess PPO by PP1 by PP2 by PP3 by Paths PPFIL, PPUUN PPUUN PPFUN PPFIL 14.3.20 DI DATA INFORMATION These records establish the data that EDL manages. o Field DIEDN DIFIL DINAH DISID DIADT DlEDT DIUSR DIREV DISTA DIDATC DIDATM DIDATR DITTL DITIMC DITIMM Type Length I I C 70 I C C C C C C C C C C C 20 20 10 10 10 10 10 10 100 10 10 Description Engineering Data Number File Number Data Name Secondary Id Application Data Type Engineering Category EDL Id of the Creator Revision Level Status Date of Creation Date Last Modified Date Last Retrieved Title Time of Creation Time of Modification 14-20 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A \ ..... 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.20 DI DATA INFORMATION DITIMR C Time Retrieved 10 Constraints DIEDN is unique DIFIL, DINAH, DISID is unique DIFIL is subset of FIFIL DIADT is subset of ATADT DIEDT is subset of ETEDT DIUSR is subset of UIUS'R Access DIO by Dl1 by DI2 by DI3 by DI4 by DI5 by DI6 by Paths DIEDN DINAH, duplicates sorted by DISID and then by DIREV DIFIL, duplicates sorted by DINAH, DISID, and DIREV DINAH ,DISID, DIFIL DIEDT DIADT DIUSR Cosets FIDI joins FIFIL and DIFIL ETDI joins ETEDT and DIEDT ATDI joins ATADT and DIADT 14.3.21 DD DATA DESCRIPTOR These EDL. records Field DDEDN DDATR DDVAL Type establish Length I C C 20 20 attribute/value Description Engineering Data Number Attribute Value Constraints DDEDN, DDATR, DDVAL is unique DDEDN is subset of DIEDN Access DDO by DD1 by DD2 by DD3 by Paths DDEDN, DDEDN, DDATR, DDEDN, pairs DDATR, DDVAL duplicates sorted by DDATR DDVAL DDATR for data in - - - - - - - .-.--. _ _ _.. __ - - - _ _._-_._._._ .. ... .. .. ...... _.- .. ---------_. 14-21 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0' ENGINEERING DATABASE RECORD DEFINITION 14.3.21 DD DATA DESCRIPTOR Cosets DIDD joins DIEDN and DDEDN 14.3.22 PD PARTS DATA These records establish the relationships between engineering data and part revisions. Field PDPRT PDREV PDEDN Type Length C 70 C 10 I Description Part Number Part Revision Level Engineering Data Number Constrairits PDPRT, PDEDN is unique PDPRT,PDREV is subset to PRPRT,PRREV PDEDN is subset to DIEDN Access PDO by PD1 by PD2 by PD3 by Paths . PDEDN, PDPRT PDPRT, duplicates sorted by PDREV PDPRT,PDREV PDEDN, duplicates sorted by PDPRT,PDREV Cosets PIPD joins PIPRT and PDPRT PRPD joins PRPRT and PDPRT DIPD joins DIEDN and PDEDN 14.3.23 FD FAMILY DATA These records establish the relationship between family and engineering data. o Field FDFAM FDEDN Type C I Constraints Length 40 Description Family Code Engineering Data Number codes 14-22 CONTROL DATA CORPORATION 1985/12/31 ICEK ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.23 FD FAMILY DATA FDFAM, FDEDN is unique FDFAM is subset of FMFAM FDEDN is subset of DIEDN Access FDO by FD1 by FD2 by Paths FDFAM, FDEDN FDFAM FDEDN Cosets FMFD joins FMFAM and FDFAM DIFD joins DIEDN and FDEDN 14.3.24 DR DATA REQUIRED These records establish relationships between one data set and any other data sets which must be available for the current data to be complete. FieJ.d DREDN DREDNR Type Length I I Description Engineering Data Number Engineering Data Number of Required Data Constraints ·DREDN, DREDNR is unique DREDN is subset of DIEDN DREDNR is subset of DIEDN Access DRO by DR1 by DR2 by Paths DREDN, DREDNR DREDN DREDNR Cosets DDR1 joins DIEDN and DREDN DDR2 joins DIEDN and DREDR _.. __ .._----_. __._------ - - - - - - - - - - - - - - ; - - . 14-23 CONTROL DATA CORPORATION 1985/12/31 ICEK ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A '14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.25 DS DATA SOURCE 14.3.25 DS DATA SOURCE These records establis~ relationships between one data set and any other data sets from which the current data was derived. Field DSEDN DSEDNS Type Length I I Description Engineering Data Number Engineering Data Number of Source Data Constraints DSEDN, DSEDNS is unique 'DSEDN is subset of DIEDN DSEDNS is subset of DIEDN o Access DSO by DSI by DS2 by Paths DSEDN, DSEDNS DSEDN DSEDNS Cosets DDS1 joins DIEDN and DSEDN DDS2 joins DIEDN and DSEDNS 14.3.26 RP RELEASE PROCEDURE These records establish the release procedures to be used for releasing engineering data. The release procedures are uniquely defined at the site. Field RPREL Type C Length 20 Constraints RPREL is unique Access Paths RPO by RPREL o Description Release Procedure Name 14-24 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.27 RU RELEASERS 14.3.27 RU RELEASERS These records procedure. Field RUREL RUUSR Type C C define Length 20 10 the releasers for each release Description Release Procedure Name EDL Id of the Releaser Constraints RUREL, RUUSR is unique RUREL is subset of RPREL RUUSR is subset of UIUSR Access RUO by RU1 by RU2 by Paths RUREL, RUUSR RUREL RUUSR Cosets RPRU joins RPREL and RUREL UIRU joins UIUSR and RUUSR 14.3.28 RR REVIEW RESPONSIBILITY These records define the reviewers for each release and the order in which they are to review the data. Field RRREL RRUSR RRTTL RRSEQ RRPRI Type C C C Length 20 10 20 I C 10 Description Release Procedure Name EDL Id of the Reviewer Review Title Review Sequence Review Priority Constraints RRREL, RRUSR, RRTTL is unique RRREL is subset of RPREL RRUSR is subset of UIUSR Access Paths procedure C) 14-25 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.28 RR REVIEW RESPONSIBILITY RRO RR1 RR2 RR3 by by by by RRREL, RRUSR, RRTTL RRREL, duplicates sorted by RRSEQ RRREL, RRSEQ, duplicates sort~d by RRTTL RRUSR Cosets RPRR joins RPREL and RRREL UIRR joins UIUSR and RRUSR 14.3.29 RA RELEASE AUTHORIZATION These records establish engineering data sets. C) Field RAREL RAEDN Type C I Length 20 RAEDNC I RAUSR C 10 RASTA RADAT C C 10 10 o release information about Description Release ·Procedure Name of the Engineering Data Number Releaser's Copy of the Engineering Data Number Designer's-Copy EDL Id of the Releaser who accepted the data Status Date on which the data was released or rejected Constraints RAREL, RAEDN is unique RAREL is subset of RPREL RAEDN is subset of DIEDN RAEDNC is subset of DIEDN RAUSR is subset of UIUSR Access RAO by RA1 by RA2 by RA3 by RA4 by all Paths RAREL, RAEDN RAEDN RAREL RAUSR RAEDNC Cosets DIRA joins DIEDN and RAEDN RPRA joins RPREL and RARE·L 14-26 CONTROL DATA CORPORATION 1985/12/31 ICEK ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A (' ''----- ' 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.29 RA RELEASE AUTHORIZATION UIRA joins UIUSR and RAUSR D2RA joins DIEDN and RAEDNC 14.3.30-RS RELEASE SIGNATURE These records establish the stamp that each reviewer data once he has reviewed it. Length Field RSEDN RSREL RSUSR RSTTL RSDAT Type I C C C C 20 10 20 10 RSSTP C 10 puts Description Engineering Data Number Release Procedure Name EDL Id of the reviewer signing Review Title of the reviewer signing Date on which the reviewer signed the data Stamp that the reviewer gave the data Constraints RSEDN, RSREL, RSUSR, RSTTL is unique RSEDN, RSREL is subse~ of RAEDN, RAREL RSUSR is subset of UIUSR Access RSO by RS1 by RS2 by Paths RSEDN, RSREL, RSUSR, RSTTL RSEDN, RSREL, duplieates sorted by RSDAT RSUSR Cosets UIRS joins UIUSR and RSUSR RARS joins RAREL,RAEDN and RSREL,RSEDN 14.3.31 ME MESSAGES These records define messages sent by a user. Field MEMSG MEUSR MEDAT METIM Type I C C c Length 10 10 10 on Description Message Number User Sending the Message. System Date the Message Was Created. System Time the Message Was Created. C: 14-27 c) CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.31 ME MESSAGES Constraints MEMSG is unique MEUSR is subset of UIUSR Access Paths MEO by MEMSG MEl by MEUSR duplicates sorted by MEUSR Coset UIME joins UIUSR and MEUSR 14.3.32 MN MESSAGE INSTANCE These records define each user receiving a whether the message has been read by that user. Field MNMSG MNUSR MNSTA Type Length I C L 10 Description Message Number User Receiving the Message Status. True if the user has message. Constraints MNMSG,MNUSR is unique MNMSG is subset of MEMSG MNUSR is subset of UIUSR Access MNO by MN1 by MN2 by MN3 by Paths MMMSG, MNUSR MNUSR duplicates ordered by MNMSG MNUSR,MNSTA duplicates ordered by MNMSG MNMSG duplicates ordered, by MNUSR Coset MEMN joins MEMSG and MMMSG o message, 14.3.33 MN MESSAGE LINES These records define the text of each message. read and the ,:,' ii; ~:;. 14-28 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 14.0 ENGINEERING DATABASE RECORD DEFINITION 14.3.33 MN MESSAGE LINES Field MLMSG MLLIN MLTXT Type Length I I C 79 Description Message Number Line Number Text Constraints MLMSG,MLLIN is unique MLMSG is subset of MEMSG Access Paths MLO by MLMSG,MLLIN ML1 by MLMSG duplicates ordered by MLLIN Coset MEML joins MEMSG and MLMSG c 15-1 CONTROL DATA CORPORATION 1985/12/31 ICEK ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 15.0 EDL STANDARD OVERLAY CAPSULES 15.0 EDL STANDARD OVERLAY CAPSULES 15.1 GENERIC APPLICATION INTERFACE XATTACH Attach Files Before Entering an Application. APPNAME REQFILE Name of the Application. File Type Code of required file. There may be up to 10 TV records with this name. Attach default files. Check for and attach required files. Allow user to attach alternate files. XLOG Process the information database. XNEWDAT Create New Data. ADT standard EDL log about engineering Application Data Type (required) file data of the to update in the EDL new data. Determine the file for the new data. Prompts for the name of the data with prompt NEWDAT4 and secondary id with prompt NEWDAT5. Creates a generic EDL log file entry to be processed later by subroutine XLOG if the data is successfully created. Sets EDL global variables PFN, UN, NAME 1 , NAME 2 , SHEET. XPUTLOG Create a log file entry for Retrieved Data. ACTION o Action code. If absent, "A" is assumed. The data must have been selected by XRETREV. XATTDAT Attach the file with the last engineering data. 15-2 CONTROL DATA CORPORATION 1985/12/31 ICBM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 15.0 EDL STANDARD OVERLAY CAPSULES 15.1 GENERIC APPLICATION INTERFACE Attaches the current file specified by the PFN and UN Task Parameter Value records. Updates the EDL list of local files. 15.2 SPECIFIC APPLICATION INTERFACE XEDITF Prepare to Edit a XRETREV or XDISPLA. data file that was selected by Attaches the file. EDITOR, LFN, CODE. procedure EDIT. variables Sets EDL global Should be followed by CCL XEDITR Return a retrieved text file after editing. XDDNPRE Preprocessing for ICEM DDN. data file. XSUSDDN Process a and TAPE3. XRESDDN Resume a DDN Session. XISHPRE Preprocess for entering the Create the input script file. XISMNEW Prepare for creating a new solid model. suspended Attach DDN session. the retrieved Renames ZZZSWAP Restores ZZZSWAP and TAPE3. ICBM Solid Prompt for Solid Modeler Library file. EDL global variables PFN, UN. Creates the XSCHPRE Prepare to run ICEM Schematics. Schematics file for the selected data. XOIRPRE Prepare file. XDDNLOG Convert the DDN EDLLOG file to standard EDL XISMLOG Convert the Solid Modeler Log file to format. XSCHLOG Convert Input Script for DDN Modeler. Attach the from OIR interface format. Standard EDL the ICEM Schematics EDLLOG file to standard c 15-3 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 15.0 EDL STANDARD OVERLAY CAPSULES 15.2 SPECIFIC APPLICATION INTERFACE EDL log file format. XFEMLOG Conv~rt Unistruc EDLLOG file file format. XIGBLK Prompt for External global variable BLKF. XPLOTN Prompt for Plot Destination and set global DEST. XPLOTNP Prompt LFN. XPLOTDD Check to be sure a TAPE9 file is local. XPLOTUS Prompt for LFN of unistruc plot file and set variable LFN. XPATPRE Prepare to Execute PATRAN. for LFN of IGES to standard EDL log blocking factor and set variable NPFILE and set global variable global 15.3 RETRIEVE XRETREV Retrieve Engineering data. This ovcap is a convenient and XDISPLA. XEXTRAC combinat'ion of XEXTRAC Extract information for a data retrieval list. If the following parameters are specified in TV records, the data that the user is allowed to retrieve is restricted to match the value of the parameter. If more than one TV record is specified for a parameter name, any data that matches any of those TV values will be eligible. The following TV parameters are used by XEXTRAC: o ADT EDT STATUS U~R Application Data Type (DIADT). 100 Max. Engineering Category (DIEDT). 100 Max. Status of the Data (DISTA). 20 Max. Owner of the Data (FIUSR). 10 Max. 15-4 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUsTOMIZATION GUIDE NOS 2 Level 642A .,,--.. I, ...... __...... 15.0 EDL STANDARD OVERLAY CAPSULES 15.3 RETRIEVE EXSCOPE XDIsPLA Scope of the data to appear on the selection list. (default) Eligible data from any ALL host in the network will appear on the list. LOCAL Only data residing on the local host appears on the list. UPDATE Only data which can be updated from the local host appears. That is, the data must be on the local host or on a non-EDL host managed by the local host. Display a data retrieval list. SELECT INTENT Used by XRETREV. Restricts the data which may be chosen from the retrieval list. ALL; (default) Any data from the list may be selected. LOCAL;Only data residing on the local host may be selected. Tells EDL the mode in which data will be attached. I Information mode--the data need not be attached at all. R Read mode--the .file will be read but not change~, as in a transfer. W Write mode--the user will be allowed to make changes to"the data. (' '-.... ../ After the user has selected engineering data to be retrieved, the following EDL global variables are set: EDN, PFN, UN, HOS, OS, NAME!, NAME 2 , SHEET, DD. XGETAPN Get the Application for Retrieved Data. retrieval task for the selected type of the execution stack. 15.4 TRANSFER ENGINEERING DATA XTRANsF Transfer Engineering Data. Pushes the data onto c' 15-5 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 15.0 EDL STANDARD OVERLAY CAPSULES 15.4 TRANSFER ENGINEERING DATA The data to be transferred must be selected by the XRETREV overlay capsule. XTRANSF creates the following EDL global variables: HOS2,. OS2, PFN2, UN2, NAME 12 , NAME22 , SHEET2, RENAME, EDN2. For transfers between hosts, it creates the following EDL global variables: BID, BPW, BID2,BPW2. RELEASE ACCEPT DISTA2 o FISTA2 If the transfer is performed to finalize a release, this TV record must be specified and its value must be the name of the rele~se procedure. If the transfer is performed to accept submitted data for release, this TV record must be specified and its value must be the name of the release procedure. Status of the new data. If this TV record is specified, the DISTA field of the destination data is given the parameter value. Otherwise, the DISTA field will be "WORKING". Status of the destination file. If this TV record is specified, the FISTA field of the destination data must be the parameter value. Otherwise, the FISTA field will be "WORKING". XDELDI2;Delete Destination Data Records if a Transfer Fails. ;Needs EDL SHEET2. global variables PFN2, UN2, NAME12, NAME22 , 15.5 RELEASE PROCEDURE 15.5.1 SUBMIT o XRELS Submit Data to a Release Procedure. The Data to be submitted must have been selected by the XRETREV ovcap. 15-6 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS'2 Level 642A 15.0 EDL STANDARD OVERLAY CAPSULES 15.5.1 SUBMIT Prompts for the name of the release procedure. Creates the Release Authorization record. The status of the data and the release authorization is set to the title of the message SUBMITTED ("SUBMITTED"). Grants permissions to releasers and reviewers. 15.5.2 ACCEPT XRELACC Prepare to Accept Submitted Data. Prompts for the release procedure name. Sets EDL global variable REL to the name of the release procedure. Creates a selection list of all data that hai been submitted to the release procedure. Should be followed by ovcap XDISPLA to display ·the list and allow selection. XRELTRA Accept Submitted Data. The data must have been selected by ovcap XDISPLA or XRETREV. The global variable REL must contain the name of the release procedure. The status of the release authorization is set to the title of the message PENDING (PENDING). The status of the designer's working data is set to the title of message RELTRAN4 (COpy PEND). May be followed by ovcap XTRANSF to copy the working data to a pending file. 15.5.3 REVIEW XRELREV Prepare for Review Pending Data. Extracts a retrieval list of all pending data the user is due to review. Sets the EDL global variable REL to the name of the release procedure. The Data list may be displayed and selected in the XDISPLA 15-7 o CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 15.0 EDL STANDARD OVERLAY CAPSULES 15.5.3 REVIEW ovcap. XRELR Prompt whether to display the data being reviewed. Push the retrieval task onto the execution task for immediate execution. XRELRS Prompt for review disposition and store the signature. XRELCHG Prepare to Change a Review Signature. release Prompts for release procedure and reviewer title. Set EDL global variables REL and TTL. Creates a retrieval list of all data the user has previously signed. o Should be followed by ovcap XDISPLA to list and allow selection. XRELCS display the Change Review Disposition on Review Signature. The data must have been selected in ovcap XDISPLA or XRETREV. The release procedure must be in variable REL. The reviewer's title must be in global variable TTL. Prompts for the new disposition and changes record. the RS 15.5.4 FINALIZE XRELFIN Prepare to Finalize Release. Creates a data retrieval list of all pending data which the releaser may release. Sets EDL global variable REL to the name of the release procedure. Follow by ovcap XDISPLA to display the list and allow selection. o XRELF Finalize or Reject Data. The Data must have been selected with the XRETREV or XDISPLA ovcap. The REL variable must contain the 15-8 CONTROL DATA CORPORATION 1985/12/31 ICEK ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A \-... .... 15.0 EDL STANDARD OVERLAY CAPSULES 15.5.4 FINALIZE name of the release procedure. If Finalized, the release authorization status is set to the value of the message RELEASED, and the status of the pending data and the designer's working data is set to the title of message RELTRF2 (COpy REL). If Rejected, the status of the release authorization and the pending data is set to the value of the message RELFRJO (REJECTED), and the the 'status of the designer's working data is set to the title of message RELFRJOA (COpy REJ). May be followed by ovcap XTRANF to move the data a release file. to o 15.5.5 RELEASE A PART STRUCTURE XRELPRT Release a Part Structure. 15.6 FILE MANAGEMENT XFILOWN List Files Owned by the User. XFILPER List Permitted Files. XFIDEFI Define a New File. XFIDEL Delete Files. XFIARCH Archive Files. Must be followed by CCL procedure RECL to submit the RECLAIM job. XFIRECL Reclaim Archived Files. Must be followed procedure RECL to submit the RECLAIM job. XFPMENU File Permissions. XFICORR Correct File Information. by CCL _. __ __-_._ _ - - - - - - - - .. .. c .. 15-9 CONTROL DATA CORPORATION 1985/12/31: ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 15.0 EDL STANDARD OVERLAY CAPSULES 15.6 FILE MANAGEMENT XIMPORT Prepare to Import a file. IMPORT1. XEXPORT Prepare to Export a file. EXPORT1. XCHKIMP Check that the Import worked. XCHKEXP Check that the Export worked. ·XATTLLO List Local Files. XSAVLOC Save local files. Must be followed by Task Must be followed by Task Must be followed by the CCL Procedure SAVLOC. XFIACQ Acquire a file. Makes a permanent file local. XATTRET Return Local files. XFIEDIT Edit a local file. procedure EDIT. XFIROUT Route a file to a Printer. procedure ROUTE. XFI~EQ Request a tape.· Must be followed by REQUEST. Must be by CCL Must be followed by CCL 15.7 UPDATE o followed XUPLOAD Mass Update for Data Files. XUPADD Add Information About Data. XUPCHG Change Information About Data. XUPDEL Delete Information About Data. CCL Procedure 15-10 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 15.0 EDL STANDARD OVERLAY CAPSULES 15.8 USER PROFILE 15.8 USER PROFILE XPERSON Update Personal Information. XDFMAIN Update Default Files XTRMCON Update Terminal Configuration 15.9 REPORTS XRDATAF Report program for full data report. XRPARTS Part List Report. XRPARTR Part Revision History Report. XRPARTW Where Used Part Report. XRPARTI Indented Part List Report. XPOSTRP Print Message After Reports Finish. 15.10 PART STRUCTURE MANAGEMENT XPSMGMT Part Structure Management. 15.11 MISCELLANEOUS USER TASKS XMESEND Send A Message. XMEREAD Read Messages. XTASKS List All Available Task Commands. c ------- 15-11 o CONTROL DATA CORPORATION 1985/12/31 ICEK ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 15.0 EDL STANDARD OVERLAY CAPSULES 15.12 ADMINISTRATOR TASKS 15.12 ADMINISTRATOR TASKS XUSMGMT User Management XGPMGMT Group Management. XGPLIST List Group Information. XGHHGMT Group Member Management. XGTMGMT Group Task Management. XRELADM Release Administration. XPIUPD Part Information Update. XPFUPD Part Family Relationship Update. XPVUPD Part Vendor Relationship Update. XVIUPD Vendor Information Update. XHUPD Update the Menu and Task Database using a transaction file. The transaction file data must have been retrieved by XRETREV. ( __ -'\1 ~ 15.13 RESERVED OVCAPS o XEDLINI Reserved by CDC. XEQUIT Reserved for CDC. XFIRST Initialize execution stack and push the user's first task onto the execution stack. XGEPGM Reserved by CDC. XREASUB XREAHAS XGENIMP XTRAREA XCHKDDB Reserved Reserved Reserved Reserved Reserved for for for for for Initialize EDL. Executed when EDL user Quits. CDC (networking). CDC (networking) • CDC. (networking) CDC. (networking) CDC. (networking) ._-_ .. _-_._.-. __ ._-_._--.- 15-12 CONTROL DATA CORPORATION 1985/12/31 lCEK ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A C~\ -------------------------------------------------------------------15.0 EDL STANDARD OVERLAY CAPSULES 15.13 RESERVED OVCAPS -------------------------------------------------------------------XCHKSDB XREAMES Reserved for CDC. Reserved for CDC. (networking) (networking) XUPDI XUPDD XUPPD XUPFD XUPDS XUPDR XUPALLD XUPDIS Reserved Reserved Reserved Reserved Reserved Reserved Reserved Reserved for for for for for for for for CDC. CDC. CDC. CDC. CDC. CDC. CDC. CDC. Sub Sub Sub Sub Sub Sub Sub Sub ovcap ovcap ovcap ovcap ovcap ovcap ovcap ovcap of of of of of of of of Update. Update. Update. Update. Update. Update. Update. Update. XUSLSTA XUSADD XUSDEL XUSCHG XUSACT Reserved Reserved Reserved Reserved Reserved for for for for for CDC. CDC. CDC. CDC. CDC. Sub Sub Sub Sub Sub ovcap ovcap ovcap ovcap ovcap of of of of of user user user user user XDISDET XDISEXF Reserved for CDC. Reserved for CDC. Sub ovcap of DISPLA. Sub ovcap of DISPLA. XTRATRA XTRADES XTRANEW XTRAREL XTTDUP XTTDUPH Reserved Reserved Reserved Reserved Reserved Reserved Sub Sub Sub Sub Sub Sub for for for for for for CDC. CDC. CDC. CDC. CDC. CDC. ovcap of ~vcap of ovcap of ovcap of ov~ap of ovcap of management. manag emen t • manag emen t • manag emen t • management. Transfer. Transfer. Transfer. Transfer. Transfer. Transfer. C~I 16-1 CONTROL DATA CORPORATION 1985/12/31 ICEK ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 16.0 CREATING A NETWORK IN EDL 16.0 CREATING A NETWORK IN EDL This section explains how to set up a network of EDL databases, one on each mainframe. Hosts in an EDL network are configured in a "star", with many subordinates clustered around a single master host. Administrative functions (user validation, part definition) are carried out on the master host. The DBA in the network, is responsible for running a job (started with the command INITNET) which polls other hosts in the network (a subordinate polls the master, while the master polls each subordinate), then rolls out for a site defined period before repeating the polling cycle. 16.1 DEFINE HOSTS The default EDL database host name is blank. In order to identify multiple hosts in a network, each host 'must be given a unique name within EDL. This name should be the three character LID (Logical IDentifier) by which the host is known to RHF. One host should be designated as the MASTER host for the network. This host must communicate directly, to all subordinate hosts which run EDL. All administrative functions, such as validating users, and defining parts, and vendors, will be done on this host, and the information will be passed to the subordinates. All transactions dealing with data are done on the subordinate hosts, and then passed up to the master. Therefore, the master host will contain information about the data on all subordinate hosts. o 16-2 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 16.0 CREATING A NETWORK IN EDL 16.2 DEFINE COMMUNICATION LINKS 16.2 DEFINE COMMUNICATION LINKS CL records must be created for each host in the database, telling EDL which other hosts a specific host can communicate with. Note that each link must be defined twice, saying that HOST A can communicate with HOST B, and that HOST B can communicate with HOST A. 16.3 QU DIRECTIVES TO DEFINE A NETWORK A sample network could consist of two Cyber mainframes, and a Cyber 120 which does not run EDL, but whose data is managed by MA4 (whose data is passed up to MB1). Following are the QU directives to update the MASTER host (in this case MB1) for this network configuration. INVOKE EDLDATAW OF EDLDATA KEY $EDLORDBA$ USING E123DDB STORE SETTING HIHOS,HIOFF,HIOS,HIEDL,HIHOSS $MB1$ 1 $NOS$ $T$ $MB1$ $MA4$ 100000 $NOS$ $T$ $MB1$ $SD2$ 200000 $AOS/VS$ $F$ $MA4$ *END STORE SETTING UVUSR UVHOS UVOUN $EDLID$ $MA4$ $EDLDBA $ $EDLID$ $MB1$ $EDLDBA $ $EDLID$ $SD2$ $DJH $ $EDLCOM$ $MA4$ $EDLDBA $ $EDLCOM$ $SD2$ $DJH $ $EDLCOM$ $MB1$ $EDLDBA $ *END STORE SETTING CLHOSS CLHOSR $MA4$ $MB1$ $MB1$ $MA4$ $MA4$ $SD2$ $MB1$ $SD2$ *END REMOVE USING UVHOS $ $ *END REMOVE USING HIHOS $ $ *END ~ I '1....--_/ ' ---------------- ------ ------------------------------------- 16-3 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 16.0 CREATING A NETWORK IN EDL 16.3 QU DIRECTIVES TO DEFINE A NETWORK MODIFY USING HIHOS SETTING HI OFF $MBl$ 0 *END END Once the network has been defined on what will be the master host, this configuration should be copied to subordinates. EDL should be installed, then this same QU file should be run EDL must run on the. same NOS on each subordinate host. account on each host. 16.4 E123PRC MODIFICATIONS C) 16.4.1 PROCEDURES GETMAS AND GETSUB Procedure GETMAS and GETSUB contain .DATA files with MFLINK directives. These directives are used to poll alternate hosts in the network for information which should be sent from the master to the subordinates, or vice versa. The first line in the .DATA files are USER,EDLDBA,EDLDBA. This user statement should be replaced with the batch user statement for the username wher'e EDL will be running in the network. Since the master host will be using these MFLINK directives to poll each subordinate, this means that the username and batch password where EDL runs on each subordinate must be the same. A recommended modification to the GETMAS and GETSUB procedures is to remove the .DATA files from E123RPC (which is available to all users running EDL) , put this information into a private file on the username on which EDL resides, and modify the procedures to read these files rather then the .DATA files. o 16.4.2 PROCEDURE EDL Procedure EDL on file E123PRC must be changed on each host, telling EDL the name of the host. The updated procedure header will look like: 16-4 CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 16.0 CREATING A NETWORK IN EDL 16.4.2 PROCEDURE EDL .PROC,EDL, I=INPUT, IT=O/IT,OT=O/OT,HOST=hos ,AUN=EDLDBA. where hos is replaced by the name of the host on which this file resides. This is the only change to E123PRC given host. which is specific to a 16.4.3 EDL LOG FILES Each subordinate should have, on the username on which EDL is installed, a file called EDLSLOG •. The master should have a file called EDLMLOG, and one file for each subordinate which rUns EDL. These files will be called EDLMhos, where hos is replaced with the host identifier for the subordinate. These files should be public, or permitted to all usernames which can run EDL, in WRITE mode. These files contain log entries of each transaction which needs to be shipped either from the subordinates to the master, or vice versa. These log files are polled periodically by their destination hosts. 16.5 NETWORK INITIALIZATION The DBA should log into each host on the account where EDL resides, and enter the command INITNET. This will start up a job which will: 1. 2. 3. 4. Poll the subordinates (or master) for transactions which should be sent to this host. Run EDL in batch mode to process these transactions. Rollout for the interval defined in the procedure NETROLL in E123PRC. Repeat. This job will have the UJN of NETJOB. It should continue to cycle until the system is deadstarted, at which time the INITNET task should be run again. If the job is dropped, the transaction data is not lost. Network transactions will 16-5 ,r-', ~) CONTROL DATA CORPORATION 1985/12/31 ICEM ENGINEERING DATA LIBRARY 1.2.3 CUSTOMIZATION GUIDE NOS 2 Level 642A 16.0 CREATING A NETWORK IN EDL 16.5 NETWORK INITIALIZATION accumulate in the log files, and will be sent to other whenever the INITNET job is run on the receiving host. o hosts " ( "-. ..... ' - - - - - - , - - - - - - - - - - - ._-. __ . _ - - - - - - - - - - 1986/04/09 CONTROL DATA CORPORATION ICEM ENGINEERING DATA LIBRARY VI.2.3 ,.OJ Operating System Level: NOS 2 Level 642A Date: 04/09/86 SOFTWARE RELEASE BULLETIN SMD131012 o --- ... - - - - -... .. _ _- - _....._---- 1 CI 1 CONTROL DATA CORPORATION o 1986/04/09 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 642A Table of Contents 1.0 INTRODUCTION o o .••• 1-1 2.0 NOTES AND CAUTIONS 2-1 3.0 PSR/RSE CORRECTIVE CODE 3-1 1-1 '. CONTROL DATA CORPORATION 1986/04/09 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 642A 1.0 INTRODUCTION 1.0 INTRODUCTION Version 1.2.3 of the Engineering Data Library incorporates the following new features and enhancements: 1. Networking between NOS and AOS/VS machines. 2. Part Structure definition and reports. 3. Graphics Programming Language interface. 4. Suspend and resume ICEM DDN sessions. 5. Improvements to UPDATE and SAVE. 6. General improvements in consistency and language. selection lists. More 7. Note facility to notify the user of the completion or failure of batch jobs and to allow EDL users to send and receive short notes. 8. Extract and load information automatically from existing Drawing, Global Drawing, and Solid Model Library files. 9. Improved Customization Documentation. 10. Performance improvements due to better IMF tuning decreased system control point communication. and o ------ ..... - .... _----- , c 2-1 \ CONTROL DATA CORPORATION 1986/04/09 C) ICEM ENGINEERING~DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 642A 2.0 NOTES AND CAUTIONS 2.0 NOTES AND CAUTIONS 1. On entering EDL, if the user's logged in NOS user name is different than the NOS username in the EDL database, a warning message is displayed. Files created under this condition will not be accessible when the user is logged into the correct username unless the files are specifically permitted to the user. o 2. Updating EDL for new files requires you to be running on the NOS username where the file resides. EDL assumes that all new files are private files. If the file is actually a NOS public file, use the EDL PERMIT task to change the file category to PUBLIC. 3. To install data files on a system username such as APPLLIB or LIBRARY, when a SUI statement is used to access the account, use UPDATE EDL FOR ENGINEERING DATA to add the information to EDL, then use CORRECT FILE INFORMATION to change the NOS username of the file to the right username. 4. An indirect access permanent file named USER must exist on the user's NOS username if the user wishes to use TRANSFER tasks on Solid Modeler data. The file USER contains the job card, user card, and accounting charge card image if needed. 5. If two users attempt to update the same EDL record at nearly the same time, a concurrency conflict may occur for the second user. An error message will be displayed and EDL will return to the previous task menu. The user should reobtain the data to determine what change was made by the other user and try the update again if appropriate. o 6. If the user uses a Control T to abort Query Update using IMF, occasionally the user job hangs and cannot be dropped. It may be necessary to do an override from the console to drop the job. 7. In a multi-host network, it is not possible to transfer data to a remote host when using the ACCEPT or RELEASE tasks. Data may be submitted to a release procedure ./ 2-2 CONTROL DATA CORPORATION C) 1986/04/09 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 642A 2.0 NOTES AND CAUTIONS from any host on the network, but to ACCEPT or RELEASE the data, the ,releaser must run on the host where the pending or released destination data is desired to reside. 8. Using the EDIT command on non-permanent files or creation files will prompt the user for the character code to be used to edit the file, UPPER CASE DISPLAY CODE or UPPER LOWER CASE ASCII. 9. The correct file type for PATRAN PATDAT, is RANDOM ACCESS DATA. DATA, local file 10. In using the transfer tasks involving an IGES DATA FILE, the user must use the correct data name of the origination file or the destination file. The IGES data name specified must match the origination data name. The transfer data name specified must match the data name in the IGES file, or if the name in the IGES file is blank, the ~efaultdata name IGES. 11. In a network configuration consisting of two or more hosts where a host is not available, the IMPORT and EXPORT commands will require a Control-T to exit the wait status. This will not exit the user from EDL: 12. The DRAWING to AP-INDEPENDENT DRAWING transfer currently suppo~ts only the ICEMDDN VI.57 drawings. The ICEMDDN Vl.60 translators will be made available after the release of ICEMDDN Vl.60 on the Application Processor. 13. The reference manual states that a part number cannot be deleted if any released data is associated with the part. In fact, the part cannot be deleted if any data is associated with the part, regardless of the status of the data. o 14. The default core memory field length to run EDL Vl.2.3 is 155,000 octal. If EDL aborts due to maximum field length (MFL) exceeded, then 'edit the procedure file E123PRC, procedure EDL, to change the command MFL,155000 to increase the amount of memory allowed for EDL and IMF. 15. The EDL relocatable libraries are compiled at NOS 2.4.2 level 642. If your site is using an earlier version of NOS and the product sets, there may be incompatibilities , C,I 2-3 CONTROL DATA CORPORATION o 1986/04/09 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 642A 2.0 NOTES AND CAUTIONS between the EDL libraries and the system libraries. This may cause problems if the EDL absolute is reloaded using the LOADEDL-p_~o~~~ure to include site-written Fortran cOde. If this situation occurs at your site, upgrade the product sets of your site to level 642. 16. The data type field is set incorrectly if a GPARTS file drawing is restored to a DRAWING file within ICEM DDN. The DDN log file specifies the data type of the restored data as GLOBAL DRAWING rather than DRAWING. To correct the data type, use the UPDATE-CORRECT INFORMATION task to correct the application data type or use QU to modify the DIADT field. The data type is set correctly if the GLOBAL DRAWING to DRAWING TRANSFER task within EDL is used. 17. Selecting a local file by name for routing to a printer does not work. Local files that need to be printed may be selected by entering 'LIST' and selecting from the" list. o c CI - _ _-_._.- - - - - - - - - - , .... . _ . _ - - - - - - _ . -. . . . 3-1 CONTROL DATA CORPORATION o 1986/04/09 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 642A 3.0 PSR/RSE CORRECTIVE CODE 3.0 PSR/RSE CORRECTIVE CODE The release of EDL V1.2.3 corrects the following PSR/RSE's. PSR/RSE DESCRIPTION ED1A011 Underlining is incorrect on certain TEK graphics terminals. Modeler analysis file transfers require suffix on file name. IGES data to DDN transfer fa·iled. Backup procedure in E120PRC prevents access to EDL 1.2. 1.13 to 1.2 conversion sets released drawing ADT to DRAWING RETDDN should retrieve drawings w/adt of GLOBAL DRAWING Submit should only retrieve data with a working or rejected status. Transaction parameter values not working correctly. TAPE3 read-only message flips by too fast to read. ED10145 answer is incomplete - command missing from LOADEDL,E120PRC 1.13 to 1.2 conversion leaves D1 status set to RELEASED 1.13 to 1.2 conversion leaves FI status set to spaces. ME transaction not working. Data goes into EDL even if it lS not actually created. Infinite loop after accidentally trying to edit E120MDB. Task RETSCH not updating EDL database after exit from application. IMF subsystem is a cpu hog. This PSR is to reopen PSR ED10141, which described the probiem. Limited lines of dialog. MCS does not recover after a system checkpoint correctly. Lack of security of the EDL data base. ED1A012 ED1A013 ED10137 o ED10147 ED10148 ED10149 ED10150 ED10151 ED10153 ED10154 ED10155 ED10157 ED10158 ED10161 ED10162 o ED10163 ED10164 ED10165 ED10166 ED10167 , 'I C, 3-2 CONTROL DATA CORPORATION o 1986/04/09 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 642A 3.0 PSR/RSE CORRECTIVE CODE ED10168 ED10170 ED10171 ED10172 ED10173 ED10176 ED10177 ED10178 ED10179 o ED10180 ED10182 ED10184 ED10186 ED10187 ED10188 EDI0201 EDL currently executes a password display with echo on. 1.13 to 1.2 conversion copies invalid tablet type from old database. EDL V1.2 standard capsule XRELS does not pop remaining tasks. EDL V1.2 looses track of ICEMDDN drawings with non alph-numeric names. EDL V1.2 one TV parameter card answers all of a capsules's prompts. EDL V1.2 REVPEND task is unusable, just to darn slow. File transfer for release does not check if destination is archived. RECLAIM fails due to lack of EDLRECL. Data ~ase gets updated when user creates drawing in a read-only file. EDL aborts with CMM error. Deleting of drawings in EDL V1.2 very complicated. Tape VSN's are not converted in EDL 1.13 to 1.2 conversion. EDL does not update GPARTS file content when changes are made. Cannot delete data sets from EDL menus. EDL believes whatever it is told without checking validity. Deleting more than 1 data set with source data deletes info source. o -.-- ... _.. _......._. __ _ - - - - ... C, CI -- - - - - - - - - - - - - - - - - - - c CONTROL DATA CORPORATION -------------------------------------------------------ICEM Facilities Ve~sion Ope~ating System Level: Date: 1.3 NOS 2.4.2 Level 642A 12/20/85 INSTALLATION INSTRUCTIONS -------------------------------------------------------DISCLAIMER o set a~e intended fo~ use only as be Control Data cannot this document. undesc~ibed ~esponsible fo~ the p~ope~ functioning of features or parameters. NOS and desc~ibed its in p~oduct Control Data Corporation reproduce this document. gives the user permission SMD131036 o to c ------- CI -------------- -- - - - ------------- ---------------- ---- - - - ---------'f-----~-· CONTROL DATA CORPORATION ICEM Facilities Ve~sion 1.3 Installation Inst~uctions NOS 2.4.2 Level 642A Decembe~ 20, 1985 Page 1 RELEASE DESCRIPTION ICEM Facilities Ve~sion 1.3 ~uns unde~ the CDC System (NOS) Ve~sion 2 and the CDC Inte~active Communications Subsystem. Netwo~k Ope~ating Facility (IAF) ICEM Facilities is designed to inc~ease the d~awing p~oductivity and enable the automatic gene~ation of ~epo~ts fo~ facilities building Manage~s and plan enginee~s. ICEM Facilities ~equi~es ICEM Vl.60. Design/D~afting The ope~ation of ICEM Facilities unde~ NOS 2 installation of the CDC Netwo~k Access Method (NAM), associated p~oducts. ~equi~es IAF and the the HARDWARE CONFIGURATION The minimum ha~dwa~e configu~ation ~equi~ed to suppo~t ICEM Facilities is 1. fo~ NOS 2 and IAF is ~equi~ed RELEASE MATERIALS The ICEM Facilities ~elease files ~eside on the tape with a VSN of REL37A. This tape has the following characte~istics: 9-t~ack with eithe~ 800 o~ 1600 CPI bina~y ~ecording mode, FACILITIES13 as the file ID in the HDR1 label, and 18 files. Fi le 1 INSTALL v Installation Fi le 2 FACTFIL Facilities tablet file. File 3 FACMSTR, Facilities MSTRING file. File 4 FACPATl Facilities global pattern file. File 5 FACPAT2 Facilities global Fi le 6 FACGPLS GPL Sou~ce. procedu~e file. patte~n file. -"_.- ----------- ... ----_.-- c' c ------------- ... __ ._------ .- --. -- - ------------.---.--- ----- .._. - ---- - --- ) G CONTROL DATA CORPORATION ICEM Facilities Version 1.3 Installation Instructions NOS 2.4.2 Level 642A December 20, 1985 Page 2 File 7 FACLIB Compiled GPL Library. File 8 FACGPRT GPARTS file' with tablet overlay drawings, pattern descriptions and example layouts. Script file for example layout. Procedure file for ICEM Facilities. CCL procedure reports. file to generate Haworth Bill of Materials database. Office furniture Bill database. of Materials Construction estimate database. Report generator source code. Report generator absolute binary. Installation verification procedure. Data for verification procedure. All limitations Facilities. applicable to NOS 2 and IAF also apply to ICEM The installer must be sure that permanent files do not exist with the same procedure. The permanent files list above will be generated. , JI o ,-) () ..? l! J.,I / ...... ( II :r L" ~/- ? c --------_._-----_._-------------------- -· C J CONTROL DATA CORPORATION ICEM Facilities Version 1.3 Installation Instructions NOS 2.4.2 Level 642A D~~ber 20, 1985 Page 3 INSTALLATION PROCEDURE The files which are part of the ICEM Facilities product are installed by executing the installation procedure which is file 1 V5N=REL37A. The installation of the ICEM Facilities tape, procedure must run interactively. Enter the following commands: LABEL,FACTAPE,R,L=FACILITIESI3,VSN=REL37A,F=I, = HD (9-track, 800 cpi) PE (9-track, 1600 cpi) D COPYBF,FACTAPE, INSTALL. BEGIN"INSTALL. Successful installation will be indicated at the terminal by message, IIINSTALLATION COMPLETE". the VERIFICATION PROCEDURE To verify the proper installation of ICEM Facilities complete following steps. The verification procedure must be interactively. the run NOTE This procedure was written assuming that ICEM Design/Drafting Version 1.60 is stored as a direct access file named ICEMDDN on user name APPLLIB. It is also assumed that a direct access file named GOLIB is stored on APPLLIB. If these assumptions are incorrect, the user must change lines 12 through 14 of file VERIFY to specify the filename and user'name in use. If the above changes are needed, lines 10 through -12 of procedure ICEMFAC and lines 7 through 9 of procedure EXTRACE both on file ICEMFAC must also be changed. G c c o CONTROL DATA CORPORATION ICEM Facilities Version 1.3 Installation Instructions NOS 2.4.2 Level 642A December 20, 1985 Page 4 Step 1. Log onto a graphics Design/Drafting. Step 2. Enter: terminal supported by ICEM BEGIN, ,VERIFY ICEM Facilities will retrieve certain files from your permanent catalog, and prompt the user with the prompt shown in Figure 1 to allow the user to enter ICEM Design/Drafting. Step 3. Answer prompts for baud rate and terminal configuration for your installation. Figure 1 shows the responses for a TEKTRONIX 4114 terminal. Key in PART NAME, SHEET NUMBER, UNITS and DRAFTING STD as shown in Figure 1. Step 4. After ICEM Design/Drafting places the user at the main menu, enter the following ICEM Design/Drafting command string. F.l.17.4.IT Step 5. Compare the display with Figure 2 to verify layout is the same. that the Step 6. Enter: 'Step 7. ICEM Facilities will complete ICEM Design/Drafting generate an office Bill of Materials. and Compare the .report report is the same. the NOTE: A carriage return. with Figure 3 to verify that Depending on the terminal used, the report may be written over the verification figure. Verification of ICEM Facilities will then be complete. o _ ...... - -. __ .__..•. _- .. _ - - - - - - - - _ . -- ..•.. - .......• _.-..- . _ - - - - C~ CONTROL DATA CORPORATION Decembe~ IeEM Facilities Ve~sion 1.3 Installation Inst~uctions NOS 2.4.2 Level 642A 20, 1985 Page 5 ----------------------------------------------------------------n;·£R 81.00 RA"E. Q ILEMD~~ VERSION Rl.SgZ CO~1~I~HT ~tNUFACTURING St:.P.IICES. IN:. 1Q78 AND CONSULTING COPYQIGHT CO~TROL DATA CORPORATION ~gle. lQ7Q, 1gea. 1get 19a2. tge3. 1ge~. Iges W(lCOHE TO ICEMOON TERMINAL TYPE TEKTRONIX ~al~ GRAP~ICS • 2. 3. ... 5. 6. 1. e. TEKrRO~Ix ~Ies ~la7 TEKTRONIX TEKTRONIX TEKTRONIX TEKTRONIX rEI(TRONl~ ~Ieg ~113 ~11" ~11S ~12S TEKTRONIX g. CDC ~lI ...., #1" ;t C-C/ ,; ..,"'/':. (~ '-... .. , - CONTROL DATA CORPORATION INTEROfFICE MEMORANDUM -~----------------------------------------------------------------------------- September 30, 1985 DATE! Distribution Mani L. Subramanian SUBJECT: ICEM EDL Enhancements for: 1. Multiple Document Retrieval 2. 3-D Piece Part Extraction Recently, some Enhancements were made in ICEM EDL to provide two special capabilities to CDC internal users. The first enhancement enables to generate multiple sheet plot files and transmit them to a remote platter of user's choice with minimum user input. The second enhancement enables to extract d Eta i I e r d T' a win S 5 of r 0 III 3 _. D lay 0 u t d raw i n :3 and rea sse mb I e IT! 0 d i fie d d eta i I e r drawings into layout drawins+ In either case, the user inputs only the part number for the drawins+ All necessary operations are carried out automatically by the system+ 80th these enhanCEments, thouSh developed to mEet our internal users' needs, can be effectively used by many of our customers. Attached to this memo are copies of User's Manuals and Installation Instructions Manuals for these two products. Please pass on copies of these manuals to any customer who may be interested in these or similar products+ elM division Special Support Group will be happy to modify these products to meet customers special needsr if any. For additional ihformation, please call me at (612)642-3849 (C/N ~380-3849) o (- -~~---------------~---~-- Mani Subramanian Cooperative Development eIM Division /ag o _. __ ._--_.... _._----_.-. __ ..... - . _ - - - - .... __._._--_._.... ,,_ ... __... - .---_._.... _- -_.__._--- c .-.- .-.. _--- ------- ---~----- ----~--- _. MULTIPLE PLOTS FOR MANUFACTURING DOCUMENT RETRIEVAL USERS MANUAL THIS DOCUMENT IS SUBJECT TO CHANGE. REFER TO THE LATEST REVISION FOR THE CURRENT INFORMATION o CONTROL DATA CORPORATION REVISION 0 Minneapolis, MN September, 1985 M. L. Subramanian ETC231 (612)642-3849 Multiple Plots for Manufacturing Document Retrieval Applications such as Process Planning.may require several sheets of drawings for each part. Ordinarily the process planner creates the plot files for each of these drawings, walks over to the plotter terminal and plots the drawings and then ships them to the manufacturing floor. Each of these activities requires considerable amount of planner's time. Furthermore, the planners office, plotting center and the manufacturing site are, in general, far apart. Consequently, there will be considerable time delay between design completion and the receipt of documents at the manufacturing floor. An enhancement added to the ICEM Engineering Data Library (EDL) provides an easy and quick means of transmitting multiple sheet plots to manufacturing site without much human interve~tion. To use this capability, the latest version of EDL is customized with the special software as explained later. One or more plotters are installed at as many remote manufacturing sites as necessary. These plotters are connected to the host computer using Control Data's application product Terminal Cluster Facility (TCF). When the installation is complete, the multiple sheet document can be transmitted to the manufacturing site by entering the part identification number. The system scans the data base to accumulate all the sheets with the given part number, generates a trace file to run ICEM DDN, executes the DDN to generate the multiple sheet plot file and then runs the appropriate postprocessor to convert the plot file into device dependent input file for the plotter of user's choice. The plotter input file is then transmitted to the remote plotter through TCF. If the designated plotter is not turned on, or if the plotter ~s busy with some other job, TeF holds the plot file in the queue until the plotter is ready to receive it. To use this simple document retrieval procedure, the EDL must be customized using the special software provided by Control Data. Your local CDC analyst will be able to help to customize EDL. Specific customization procedure is described in the document -Installation Procedure for Multiple Plots for Manufacturing Document Retrieval.' Figure 1 shows complete computer-user dialog under this option. As seen in this figure, the new customization adds two new choices to the ICEM applications task menu. The first addition is -Multi-Plot for Document Retrieval' and the next 'Reroute Last Multi-Plot File.! - 1 - c '.1. o ~~~b!!=EbQI_EQB_QQg~~g~I_BgIB!g~~b~ When the 1.lser selects the first choice by entering either the task number 9, or the task name MULPLT, the system responds with the message: ENTER THE PARTNO FOR THE DRAWING OR CR TO RETURN ?-------------------------------------------------------------The user enters the part number (1-70 characters long), the same name used ICEM DDN. The is informed of message on the while creating or modifying the part drawing in system begins to scan the data base. The user the current activity by displaying appropriate screen. Thus, the first message is **** GENERATING A LIST OF ALL SHEET NUMBERS **** followed by **** GENERATING TRACE FILE TO RUN ICEM DDN **** If the data base does not contain any part with the siven name (which could also happen if the name is misspelled), the system displays the message: NO DRAWING WITH GIVEN PARTNO IN THE DATA BASE L) r- and aborts back to the EDL menu. found the sV,.stem display,s: THE NAMED PART HAS n SHEETS. If the desired drawing is n PLOTS WILL BE GENERATED where n is the total number of sheets. This message will be followed by. **** ENTERING ICEM DON TO GENERATE TAPE9 **** and **** ENTERING UNIPLOT TO CONVERT TAPE9 TO NEUTRAL PICTURE FILE (NPFILE) **** After converting the plot file TAPE9 into neutral picture file, the system asks the user the destination point by displaying a menu: SELECT THE PLOTTER FOR DOCUMENT RETRIEVAL 1• 2. 3. Benson 90V Benson 9336V Calcomp Plotter B90 B9336 CalcolTlp SELECT OPTION o ?------------- ... ,- .. -~--------..-.., - - . - . - - - - -.. --_., - 2 - ~,~."., :r •. The above menu is only a typical menu. The actual menu for individual sites will be different depending upon the types of plotters used. Help messages similar to the one shown below can also be added in the menu data base: THIS MENU ALLOWS YOU TO SELECT THE PLOTTER TO WHICH THE PLOT FILE IS TO BE ROUTED BY TCF. BENSON B 90V PLOTTER CAN PLOT ONLY ·A· SIZE DRAWINGS AND IT IS LOCATED AT (SITE NAME). BENSON 9336 CAN PLOT ALL SIZE PLOTS AND IS LOCATED AT (SITE NAME). CALCOMP PLOTTER IS LOCATED AT (SITE NAME). The user selects the destination by entering the option number or the option name. The system continues with the messa~3e : **** ENTERING UNIPOST TO CONVERT NP FILE TO A SPECIFIC PLOTTER FORMAT. THE FILE WILL BE ROUTED THROUGH TCF **** When the routing is complete, the procedure is terminated with th~ message: **** ROUTING IS COMPLETE **** Control then returns to EDl menu. Sometimes it may be necessary to route the same file to more than one plotter. This second choice enables the user to accomplish this function without going through the long procedure followed during the execution of the first choice. Therefore, whenever a new plot file is routed to the plotter, a copy of the file is saved. When the second choice is selected, the user is asked to specify the destination plotter and the copy is routed to the specific plotter. The second selection of the plotter need not necessarily be the same type as the first selection. Hence, instead of saving the final plot file, the neutral picture file is saved and postprocessed according to the plotter selected. Terminal Cluster Facility only enables to route plot files to remote plotters. This capability eliminates the necessity to use the dedicated terminal at the plotter site. However, if there is no necessity for such a capability, one may use this EDL enhancement without the use of TCF. - 3 - r--- ( \ '-- . . ' If a plot file is routed to a wrong plotter and you like to drop the job, you may do so. First find the JSN for the Route process by looking into your dayfile. Then enter DROP, JSN nan.e If DROP command does not work, try GGET,JSN name,DC=PR If QGET also fails, platter has started platting the file. Only the computer operator can drop the job at this time. If a wrong drawing is selected, and if you like to drop out while the job is in execution, wait until it sets into DDN, then enter IControl TI twice. DON execution will be terminated and the control will return to EDL menu. Before you re-execute, return or rewind all local files. _. 4 - -.EDL 1&/.,". SELECT THE PLOTT£Jt FOIl DOCUfENT RETRIEVAL 1 • IENION-DIV eoe . •aa.IDIOM-GIIIV 80338 . I... ~'1t\..OT1'D CAL.~ 1 ___ __ IELECT CPrION ItEM EN8INEERIN8 DAT_ LIMM't YlRIIDN '.2 •• CCP'tJII8HT toHTROL DII TA CORP., I Q84 .... CURRENT TERMINAL COHF1BUMT 10M GRAPHICS TERltUML DI AL.06 AREA COtKJNICAT IONS RATE COtttUtlCATlONS TYPE TAIL£T OILFMJl.T OEFAIJLT BIT PLNEI 4 E~ ,. 2. 3. 4. S. 6. 7. 8. Q888 8N.A) ASYNCHRONOUS NO LOCAL. ASSIST LOCAL DISPLAY .... ~ .ROUT 1.. II tOfItL£TE. ,• EXIT DESIGNIDAAFTlN8INC SOL ID ttOOELlNB UNISTRUC 11 PATRAH-O ICE" SO£MTlCS ICE" TEKROUTE PLOTTING Q. fUL TJ -PLOT FOR DOCUIEHT RETRIEV*18. REROUTE LAST tU.TI-flLOT FILE ENTER TASk . OE'I~TlNI/NC I. SOL ID MODELIN8 4. UNISmtJC II 5. PATlWHI I. IC£" ICHEMTICS 7 • I~ TEJatOUTE I. PLOTTING Q. HULTI-9LOT FOR DOCUttENT RETRIEV*11. ItEROUTE LAST tlULTI-PLOT FILE EHTtR TAlk i,EXIT DON I ... US ~T.PI\ntM SCH TEK PLOT tU.PLT REROUT 1. NUttBERS.... 8ENEMTlN8 TRACE FILE TO RUN lcat ........ TtE NMED PMT w.s 4 SHEETS. 4 PLOTS WIll. BE OENERATED. STOP ENTERING lcat DOH TO GENERATE TAPED .... .... .... •••• 1. 2. S. ... 6. \ RtlJT INO IS COtA.£T£ lcat ~ICATJONS EMIT DESIGHIORAFTIN8INC SOLID HOOELING UNISTRUC 11 P4TAAN-G 8. 7. ICE" SCHEItATlCS IC£" TEkROUTE PLOTTING .ttUl.T1-PLOTFOR DOCUttENT RETRIEVAL. 'I. It£ROUTE L",r tU...TI-PLOT FILE ENT£ft TASK TEJ( . PLOT . tU.PLT REfQJT FIGURE 1. Computer-User Dialog During "Multi-Plots for Manufacturinr"-'ocument Retrieval" Session \ ". .. 8Q338 CALCOHP .... ..... E,EMIT DI* ISI't us PAT,PATRAH SCH TEl( PLOT HULPl..T . R£ROUT QUlL._:..;.. __ ? THIS MENU M..L.OWS TO SELECT THE PLOTTER TO WtiICH THE PLOT FIL£ "ILL IE ROUTED 8Y TCF. BENSON B-88V PLOTTER CAN PLOT ONl.. Y -A- SIZE DRAWINGS. B-Q0V IS LOCATED AT (SITE tWtE). BENSON ga3S CAN PLOT ALL SIZES DRAWINGS. BENSON galS IS LOCATED AT (SITE NAtE). CALCOHP PLOTTER IS LOCATED AT ;IIT£ ~). / .7 ·8. G. .. , ENTERING UNIPOIT TO CONVERT ..-FIL£ TO A IP£CIFIC PLOTTER FOAMT. .• THE FIL£ "Ill. IE ROUTED THROU8H TeF.· tJtlPOST n.2 REI E.... COPYJtIa.tT CONTROL. o.-TI\ 1 " SELECT THE PLOTTER FOR DOQI1EHT RETRIEVAL I • 8ENSON-GeV 8QII 2. 8ENSON-Q336V 8Q33S 3. CALCOtP PLOTTER CALCOHP OPT ION 1SELECT 1________ _ (-~ PLOTTER ., . . DON..... ENTERING UNIPLOT TO CONVERT TAPED TO NEUTRM. PICTURE FILE(NPFILE) DON lilt US PAT ,PAnw. 9tH SELECT THE PLOTTER FOR DOQ.ItENT RETRIEY. . 8£N8ON-08V EHTER THE PARTNO FOR THE OftA"JNO OR CR TO RETURN 2. 8ENSON-G3a8V ~Il~-~I_OE-RB8Wl~_EVB-~MI_~IBl~~eL ___ --------------iEtEeTaQpTi~~ •••• GEHERATlN8 A LIST OF AU. SHEET 1 _ __ .... £,EXIT ?~- ., tM.e\.I ___ _ ? ICE" NlflLICAllONl . EMIT 2~ lCEIt APPL 1CAT IONS .... .... Df1'£JtIN8 UNI~T TO COIWDT NPFILE. TO A SPECIFIC ftWlTTER FORMT. TtC FILE "Ill. 8E ROUTED TMROtat TeF. UN 1POST VI. Z R&L.£AeE 117 COPYRI8MT CONTROL. DATA t QI5 TEl( 4114 ON OMPHICS· 'TUItlNM,; / I (\ '. .. CONTROL DATA CORPORATION :! o MULTI-PLOTS FOR MANUFACTURING DOCUMENT RETRIEVAL RE'JISION 0 S EPTEME:ER, 1985 INSTALLATION INSTRUCTIONS DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Control Data Corporation gives the user permission to reproduce this document. o -_ ... _- .......... _._._-_._----------- - - - __ __._-_ _. --------------------_._ __ ._- - ._-. . .. .•. CONTROL DATA CORPORATION MULTI PLOTS FOR MANUFACTURING DOCUMENT RETRIEVAL INSTAllATION INSTRUCTIONS Page 2 SEPT., 1. 985 RELEASE DESCRIPTION -Multi Plots for Manufacturing Document Retrieval· is an enhancement to ICEM EDl Version 1.2 which runs under the CDC Network Operating System (NOS) Version 2. This enhancement enables you to generate multiple sheets of plots under the given part number and transmit the file to a remote plotter of your choice. You input only the part identification number and the destination plotter code. The system scans the database, creates a list of all sheets under the given part number, generates a trace file to run ICEM DON, executes DON to generate the multiple sheet plot file, converts the plot file to a neutral picture file using UNIPLOT, runs the appropriate postprocessor to convert the neutral picture file to device dependent input file for the plotter, and finally transmits the file to the plotter through Terminal Cluster Facility (TCF). Hence, to use this enhancement, you should be already using or willing to install NOS Operating System Version 2.0, ICEM EOL Version 1.2, ICEM DON Version 1.57, Terminal Cluster Facility Version 1.0. This enhancement will be operational in any later versions of these products, but not necessarily in earlier versions. HARDWARE CONFIGURATION The minimum hardware configuration required for NOS 2, EOl and DDN is also required for this product. RELEASE MATERIALS THE ·Multi Plots· release files reside on the magnetic tape with VSN of MPREL1. This tape has the following characteristics: 9-track with 1600 bpi binary recording mode, MPV10 as the file ID in the HDRl label, and 6 files. File 1: Installation Procedure File 2: FORTRAN routines that will be added to the EDl File 3: FORTRAN capsules that will be added to the EDl File 4: Procedure file to be included in the EDl c CONTROL DATA CORPORATION MULTI PLOTS FOR MANUFACTURING DOCUMENT RETRIEVAL INSTALLATION INSTRUCTIONS o Page 3 SEPT., 1985 File 5: Transaction file to be included in the EDL File 6: A procedure to compile the FORTRAN routines (File 2), FORTRAN capsules (File 3) and implement them in EDL NOTES AND CAUTIONS All limitations applicable to NOS 2, EDl, DDN and TCF also apply to this product. Also it is the customer's responsibility to provide the necessary postprocessor(s) for each plotter being used. Control Data has a large supply of postprocessors for various plotters. If not readily available, CDC can develop one. The postprocessor may need some modifications in order to use the plotter as a remote device using TeF. To convert the DON generated plot file TAPE9 into Neutral Picture File, you need UNIPLOT and DDNUTIL installed in your APPLlIB user name. If your EDl is already customized, running the procedure (File 6) may wipe out your original customization routines. Hence, modify File 6 as necessary if your EDl is already customized. This product is expected to provide the capabilities described in the User's Manual. However, it has to be fine tuned during installation to adjust for customer site requirements. INSTALLATION PROCEDURE The files which are part of t~is product are installed by executing the installation procedure which is File·1 of the MPRELl tape. To install the files, submit the tape to the computer operator and enter the following commands from your interactive terminal, under DBA account nuumber. LABEL,TAPE,VSN=MPREL1,NT,L=MPV10,R,F=I,PO=R,D=PE,l8=Klt COPYCF,TAPE,INSTAL. BEGIN"INSTAl. This procedure will install the following indirect access files: MPFTN,MPCPSl,MPPROC,MPTRAN and MPFTOE. o .. ---.- .. ------ ..... ~-- ... _--_ ........... - .~-- CONTROL DATA CORPORATION MULTI PLOTS FOR MANUFACTURING DOCUMENT RETRIEVAL INSTAllATION INSTRUCTIONS Page 4 SEPT., 1985 /'~--- ( '...-........ ' If you already have files with these name, transfer them to different names before running this procedure. Modify the transaction file MPTRAN using XEDIT or FSE. all BMLS2154 B to DBA account numberf Change Clear all local files and then execute the procedure MPFTOE by entering the commands: CLEAR+ GET,MF'FTOE. E:EGIN''1MPFTOE. This will update your EDl files by including the new capsules and FORTRAN routines. This will also create a new indirect access file MPLIB. Next? update the EDl Menu database in the following manner. Enter EDl using an ID with SYSADMIN privileges (like EDLID). A. Choose the UPDATE EDl for Engineering Data Task (Task Command UPDATE). 1• 2. 3. 8. Tell the EDl that the file is an UPPER CASE TEXT FILE. Give the data a meaningful name, like MOB TRANSACTIONS FOR MULTIPLE PLOTS. The Application Data Type is EDl MOB TF"'ANSACTIONS. Enter the task command MENUMGMT. 1. 2. Retrieve the data which you just entered into EDL. Select that data, and the changes will be automatically entered into EDL. To check whether there was any error while modifying the EDl menu databaser review the file M08lIST by entering EDIT task. If there is no error, enter into ICEM task. The IeEM APPLICATIONS task menu should show the additional two tasks MULTI PLOT FOR DOCUMENT RETRIEVAL and REROUTE LAST MULTI PLOT FILE. c' CONTROL DATA CORPORATION MULTI PLOTS FOR MANUFACTURING DOCUMENT RETRIEVAL INSTALLATION INSTRUCTIONS o Page 5 SEPT., 1985 VERIFICATION PROCEDURE To verify the proper functioning of this enhancement: 1. Generate a multi sheet drawing in DDN while running DDN fro ITI ED L • 2. Make sure TCF is properly installed and plotters are connected to the appropriate dedicated ports. 3. Both UNIPLOT and DONUTIL reside in your computer under user name APPLLIB. If they are in some other user name, edit the MPPROC file to replace the correct user name. 4. Make sure that the postprocessors for the plotters are updated to transmit data through TCF. 5. Edit the MPPROC to change all user names from MLS2154 to the corresponding names in your installation. Change the postprocessor file names as necessary. Edit the MPTRAN file to modify SELECT THE PLOTTER menu. Now, select the task MULPLT. If the installation is complete, the dialog will be as shown in Figure 1 of the User's Manual. Because of the largE amount of hardware-software compatibility matching requirements, considerable amount of fine tuning may be necessary before successful installation and execution of this enhancement procedure. o __ ,_____.". __.... ,. ___"."."". _"." '. ___,_'. __. ,____ , ____.._0._--' -----" -_ .... ---_.. __ ......_-------- -- - ------------------ - - - - - - - - - - 3-D Piece Part Extraction From Layout Drawing / USERS MANUAL This Document is Subject to Change Refer to the Latest Revision for the Current Information Control Data Corporation Minneapolis, MN o Revision 0 September", 1985 M. L. Subramanian ETC231 (612)642-3849 3-D Piece Part Extraction From Layout Drawings ., Conventionally 3-D layout drawings are generated first. Data for each piece part are extracted from the layout drawing to draw the detailer drawings. Detailers work on the piece part drawing to provide detailed information for the piece parts. Depending upon the complexity of the layout drawing, piece part data extraction may be very laborious and is prone to human error. To systematize this process, in computer aided design, each piece part geometry is designed at a different level. Then using the IDELETE BY THE LEVEL RANGEl Menu, piece part geometry data are extracted cyclically. Though a giant step forward in right direction, this technique still requires considerable amount of designer's time to senerate piece part drawings. An enhancement added to the ICEM Engineering Data Library (EDL) automize this entire process and eliminates possible human errors. The designer identifies the layout drawings by entering the part identification number. Name, level, find number, and quantity for each piece part are stored in a file called Part History File and is supplied by the user. Using these two sets of information the system scans the database to attach all necessary files, generates a trace file to run ICEM DON, executes DON and creates a GPARTS file which contains detailer drawings for each piece part listed in the part history file. Detailers can extract individual drawings from the GPARTS file, work on them and return them to the GPARTS file. By selecting another menu, the designer can reassemble all modified drawings and compare the reassembled drawing with the original drawing for possible design error. To help the designer to create and/or modify the part history file, a third menu choice provides ea~y access to the on-line full screen editor or the line editor. A fourth menu allows the detailers to enter the PARTNO of the layout drawing to attach the corresponding GPARTS file. The system also puts the detailer into DON automatically. The system keeps track of all existing files. If necessary, defines new files. If a file exists where one is to be created, the system requests permission to overwrite. If denied, steps back to the previous menu. Though not necessary fo~' user to remember, the system displays newly defined file names for information. If the named part does not exist in the database, issues error message and returns to the main menu. - 1 _. "..... To use this automatic piece part extraction process, the EDL must be customized using the special software provided by Control Data. Your local CDC analyst will be able to help to customize EDL. Specific customization procedure is described in the document IInstallation Procedura for 3-D Piece Part Extraction from Layout Drawins.' When this enhancement is implemented in EDL, a new task is added to the ICEM APPLICATIONS task menu as seen in Figure 1. The title for this new task is 'DETAILER DRAWINGS'. When this task is selected, another task menu as shown below is displayed. DETAILER DRAWINGS EXIT GENERATE DETAILER DRAWINGS F~OM LAYOUT ASSEMBLE DETAILER DRAWINGS INTO LAYOUT CREATE/EDIT PART HISTORY FILE ATTACH GPARTS FILE TO USE WITH DON 1• 2. 3. 4. 5. E,EXIT DETDRW ASEMBL PHEDIT GPATCH Per EDL convention, the first task EXIT allows you to return to the previous menu. When the task number 2 or task name DETDRW is entered, the system displays ENTER THE PARTNO FOR THE DRAWING OR CR TO RETURN (_~I ?----------------------------------------------------------------Enter the 1-70 characters long PARTNO used whi Ie cre~ting and/or modifying the layout drawing. The system begins to scan the database and informs the user by displaying *~** SCANNING EDL DATABASE TO OBTAIN PFN AND UN FOR ALL REQUIRED FILES ~~~~ Next, the system displays ~~** ATTACHING THE DRAWING FILE-TAPE3 ~*** If there is no drawing file in the database, control returns to the last menu after displaying the message NO DRAWING FILE IN THE DATABASE If the named part is not found in the database (which could also happen, if the name is misspelled), control will return to the last menu after displaying the message - 2 - o . . . . _.. __._-_.. " ...... --- - _..__ .......... _........_.._ - - - - -_._ ...... - - ... _--_..... . ***~ NO DRAWING WITH THE GIVEN PARTNO IN THE DATABASE **** .. , If the drawing is found, the system continues with the message: *~** **** ATTACHING THE PART HISTORY FILE - PHFILE If the part history file does not exist, the system displays the error message: NO PART HISTORY FILE IN THE DATABASE Or, if the part history file does not contain data for the given part number, the system displays the message: REQURED DATA IS NOT IN PHFILE. DRAWINGS. CANNOT GENERATE DETAILER In either case, the control returns to the previous menu. Then select the PHEDIT task to create the PHFILE or add data to it. If the required part history data are found, the system continues with the message: **** DEFINING A GLOBAL DRAWING FILE - GPARTS **** If a slobal parts file already exists with the given PARTNO, the systerll displays: GPARTS FILE WITH GIVEN PART NAME ALREADY EXISTS. OVER WRITE? If the answer is NO, control returns to the previous menu. YES, the system continues with the messages: *~*~ GENERATING A TRACE FILE TO RUN ICEM DDN If **** **** THE NAMED PART HAS n LEVELS n DRAWINGS WILL BE CREATED ON GPARTS FILE **** where n is a positive integer. **** ENTERING ICEM DDN TO GENERATE GPARTS **** SUCCESSFUL COMPLETION **** **** GPARTS FILE NAME IS GPFnn **** Where GPFnn is the name for the newly created GPARTS file. This is for your information only. You need not remember this name in order to retrieve drawings from the GPARTS file. - 3 - c' Please note that when the detailer drawings are generated, the entire piece part geometry for each component piece part is created at level zero. Now the detailers can add labels and other information at levels other than zero. c=) ~~§§g~~b~~~_QgI~~bgB_QB~H~~~§_~~IQ_b~rQ~I~ When this task is selected by entering the task number 3 or the task name ASEM8L, the system requests the part number of the original layout drawing by displaying! ENTER THE PARTNO FOR THE DRAWING OR CR TO RETURN ?---------------------------------------------------------------When you enter the part number, scanning the database, attaching the files, generating the trace file to run DDN and DDN execution proceeds almost in the same manner as in the previous task. The sequential output messages are shown in Figure 2. As seen in this figure, instead of defining a new GPARTS file and scanning data on it, GPARTS file with the PARTNO is attached and data is restored from it. Instead of displaying the newly defined GPARTS file name, the system puts you back in DDN and displays the newly reassembled layout drawing. You may review and make changes as necessary. ( '--") ~/ During reassembly all additional data put by detailers at levels other than zero are discarded. Piece part component geometry are moved to their original levels. The original layout drawing is not altered. The new assembly drawing is created with the same part number but the sheet number is incremented by 1000. That is, if the sheet number of the original layout drawing is 100, the sheet number of the reassembled drawing will be 1100. Since the sheet number cannot be greater than 9999, if the original sheet number is 9000 or more, the sheet number for the assembled drawing will be original number minus 9000. This task enables to create and/or edit the part history file. A part history file may contain part history for more than one part. Each part history begins with the PARTNO for the part. The second and the subsequent lines, except the last, contain the part history which include (a) find number, (b) level, (c) quantity and (d) piece part name. All these four items for each piece part are stored on a single line. The first five columns contain the find number. The next five columns contain the level. The next five - 4 - c=) ---------" ----, -''''''---''--'' --- columns contain the quantity. The last 70 columns contain the piece part name. The first three items can be anywhere in their specified area. While entering data using a text editor like XEDIT or FSE, left justified data entry is easier due to tab settings. The last line in part history must be SEND'. When this task is chosen, the system requests the PARTNO by displaying ENTER THE PARTNO FOR THE DRAWING OR CR TO RETURN ?----------------------------------------------------------------Enter the 1-70 characters long PARTNO. The system looks for a part history file. If one does not exist, it will define a new file. If a part history file already exists, then it scans the data to see if the history for the named part exists. If it does, it positions the cursor on the first line of that history if you are using the full screen editor. If you are using XEDIT, it will print the first five lines of that part history. In either case, the tab character is set as '\' (inverse slash) and tab columns are set at 6, 11, and 16. Hence, you can insert a new line of data by entering a line like: 25\3\60\HAlF INCH NUT The data will be entered into the file as 25bbb3bbbb60bbbHAlF INCH NUT where b is a blank space. If the part history for the given PART NO is not found, FSE will set the cursor at bottom of the file and XEDIT will put you at the top of the file. Find number and quantity are not used in this application. But they are included here so that the same part history file can be used in other applications such as Bill of Materials. When you leave the edit session, control will return to the last EDl menu. c To begin his task, the detailer must attach the GPARTS file and run DON to extract the piece part drawing. One cannot expect every detailer to remember the file name. Hence, by selecting this task, a detailer can attach the right GPARTS file by entering the PARTNO for the layout drawins. Thus, this task also begins - 5 - C, .' with a request for the PARTNO for the layout drawing. enter the PARTNO, the system will display: When you DURING THIS SESSION, WILL YOU SAVE PARTS ON THIS GPARTS FILE? o Answer yes or no depending upon whether you are to save parts or restore parts from the GPARTS file. As seen in Figure 4, you will automatically enter into DON after havins an opportunity to attach additional files, if necessary. Of the four tasks, the last one will be chosen by any detailer. Other three tasks should be performed only by a selected few. Hence, a security code is assigned to the first three tasks dedscribed above. Unless one is a member of a group and the group has permission, one cannot access the first three tasks. If you select a wrong task, the easiest way to quit non-existing PARTNO. While the job is in progress, sets into DDN and then enter 'Control T' twice. If 'Control T' at any other time you may be forced out C) - 6 - o -_._---_ .. ..... _-_ ...... _.. _---. __ _ ._--_ .. - ... - - - - - .. - - - _ . is inputting a wait until it you enter of EOL. ./R/a. leIM INIINEEJU. . ~TA LI ....." VPlION '.2.' ~I8HT CONntOL ~TA CO• • , , .... •. ".D. CUMINT TEM'''' COIFIIUMT'ON ~ICS TEMtUML DIM.08 NEA TEIC 4114 ON . . . .Ic. TlMI . . . TML£T NO D€JrMJI. T ~ICATIOM1 IMTI COf9UtICATIOMI TYPI LOCM.. . .lIT LOCM. Dl.-w..AY a.t elT PLANES 4. 4 UNI111IJC II s. PATMI-e lcat IQCMTICS ICEM TEICMJUTE •• 7. a. T~ IIffElt DUU-T NO leat ..... ICATtCIIII EXIT DQIINIDMFTINIINC SOLID PlJD€L.I. . ,. 2. I. 8. _ WIU) MYNCHIDOII PUJTTI. . DETAIL£1t DMWU•• ~IT I .. us ~T.MTIMN tcH TE1C .....OT DETAIL "KIeU._ ,. 2. I. 4. DETAILEIt DMWI. . . EXIT OENEMT£ D€TAILER . ., . . . ,... LAYOUT MSaa.£ DETAILEIt ~I'" INTO LAYOUT CREATElEDIT fWtT HISTOItY FILE ATTACH.-Mrs FILE TO U. WITH DON T.-. ., DlIIft_ DI1'!It , s. .... ........ .... .... ENTER TME twn'NO F'CIt THE DMWI. III _ CIt _TO .TUM ________ • __ 1:I~1~..MIU&I- SCMeCa.. EDL DATA . . TO oaTAIN PFN * I ) 1M F'CIt M.L _QUIltED FILES "TTM:HI" THE . .1. . FILE - TMID .uTACIII . . THE PMT HISTCItY FILE - PHFILE D€F'INIMD A 8UI8M. _ _ ... FILE - .wtTS OENER"TI" A T1MCE FILE TO RUN leat DON •••• THE NMED PMT HAS 4 LEVELl • 4 ORMf I MaS "ILL IE CllEATED OM .-MTS FILE. •••• •••• ENTERINO ICa. DON TO OENEMT£ c.MTS .... ~~ MEJa.. PHEDIT &PATCH SUCCES9F'LA. CONtLETION • CPMTS FILE NME IS 8PF'1t ........ .... .... .... ........ .... •••• Figure 1. n \ / Computer-User Dialog During the "Gener(+) Detailer Drawings from Layout" '-"ask \ -:. ~ ~ o (\ \,~) tCEM ~ICATIONI EXIT DESI9H/DlMFTIN8/NC 1WLIO ttOOELlNa ONISTRUC II 5. PAT"AN-G 8. ICa. SCHEMTICI 7. ICE" TEtCROUTE .. 8. PLOTTINB D. OETAILER DftMlrNGI TASk _ ?ENTER V_______ 1. 2. 3. 4. DETAILg DRMfINBS EXIT 2. OENE_TE DETAltER MAWr . . . FROtt LAYOUT 3. ASSEH9L£ OETAILER !)RAVINeS INTO LltYOUT 4. CREATEIEOJT PART HISTMY FILE 5. ATTACH &PARTS FILE TO USE WITH DON EHTER TASt( 1. .... us PAT,H.TRNt ICH TEt< PLOT· DETAIL ~!.I)(IT DETORV AIEt1BL PHEOJT &PATCH I ~ E i I B _ I ~ e _ ~ , ENTER THE PMTNO______________________________________________ FOR THE: DttMIINa OR CR TO RETURN _ E l e _ -. Q : ? U~J(IT IU. eK!M. ___ _ 1 ? o ..... SCANNING EDt. OATA IAIE TO .,.TAIN PFN ANI) UN FOR ALL REOUIR£O FIL£S ATTACHING THE DRMIING FILE - TAPES •••• •••• ..... ATTACHING THE GLOBAL ORMIIN8 FILE - OPMTsa. . . ..... ATT~IN8 •••• GENERATING A TRACE FILE TO RUN ICE" DON ..... ENTERING ICE" DON TO AStEtB..E DETAILER DRAWINGS INTO LAYOUT DRAWING .... .... SUCCESSFUL COtFLETION. • ... •••• WAIT A "INUTE TO SEE THE REAS9EtILED THE PART HISTORY FILE - PHFILE LAYOUT DRAWING ..... .... ..... Figure 2. Computer-User Dialog During the "Assemble Detailer Drawings into Layout" Task < 4 lENDS ICEK ~IC_TIONS 1. EXIT 2. OESIGNIDfMFTINGINC 3. SOLID 1100E1.1N9 .... UN1STRUC II 6. PATfMN-G 8. ICEM ICHEMTICt 7. ICEM TEKROUTE .. 8. PLOTTING V. OETAILER DAM1 ... , ENTER TMnC 1 ~!elL ___ _ ~XIT I'" us PAT,NTRAN' ICH TEl( PLOT. DETAIL 4 • TEXTS 1-0 P.JECE . . .T MSIJ1ILy 27 • 27 • .,. •• OQQ 128 1 • . POINTI 0 ,. 45 LINES CIRCLES' TEXT. --EOIt---£OF--£Olrrr:.:: 11 Q .. PHf:lLE . 1. A LOCN.. ' l L E , *** EDt. '·11 NOW M>OIM8 DETAILER ~1N8S EXIT GENERATE DETAJLER DR~IN9S f:RCM LAYOUT 3. AssatBLE OETAILER ORtWIN6S INTO LAYOUT 4. CREATE/EDIT PART HISTORY FILE . S. ATTACH SPMTS FILE TO USE WITH DON TASk _ 1ENTER ________ ,. 2. E,DIT OETORV AsatBL PHEDIT &PATCH .. ' . VOULD YOU LIkE TO lPOATE EDt. IIFORtMTiON ,- ENTEIt YES OR NO (YIN) t. . ..FORMTleM FOR 1-0' PIECE PART . . . . I IfQR THE OATA I)£TAILER DlMWINas EXIT ~ ENTER THE PARTNO _____________________________________________ FOR THE DRAWU. OR at TO RETURN __ 1 i:Q_~1~C~_e~!_911~~I **.* •••• ATTACHING THE PHF'ILE FOR EDITING 3-0 PIECE PART ASSEH9LY 27 27 36 POINTS 96 36 g LINES 81 000 18 CIRCLES 128 1 ~5 TEXTS 11 TsP. ILLEGAL PARMETER 11 T 11 P. R... I8S4G88 1 9 t PRINT£D "IR INO BOARD (PWO) OUTLUE 2 2 ,. FORMAT, ENG INEERJNG NOTES, TILTLE 8I..OaC ETC. 5 18 1 PVO COttPONENT LOCAT I ON DR 10 6 50 SS INTEGRATED CIRCUIT BODIES 7 51 45 IC FINO NUH8ER CIRCLES 8 52 55 It VENDER IDENTIFICATION g 68 63 SINOlE-IN-LIHE (SIP) 900IES 18 80 27 DISCRETE BODY OEOfETRY 12 lee go DRILL PATTERN DATA 1 t3 t01 123 DRILL PATTERN DATA 2 t... '02 54 DRILL PATTERN DATA 3 15 t93 27 DRILL PATTERN DATA ... 16 194 12 DRILL PATTERN OATA S DRILL PATTERN DATA & . 17 '85 3 18 196 S DRILL PATTERN OATA 7 23 291 45 IC FINO NUttBER INF'ORf'ATION 24 292 36 IC LOCATION NUt1BER INFDRl'9ATJON 2S 26 27 28 391 392 491 492 , 30 2 '9 SIP FINO N~ INF'ORMTION SIP LOCATION NUftBER INFORMATION DISCRETE FINO HtJtt8ER INFORP1ATJI* POINTS LINES 'END. 3-0 SECOND 2 I 2 I 5 g 3 3 S DISCRETE LOCATION ~R INFORKATION CIRCLES Or n Figure 3. computer-user Dialog During the "C~1.te/I.:dit Part History Filel! rrask \. ) / \ .... ... o ''---- " I~ ~ICATIONS 1. 2. ~~)(n EXIT DES ICJNI1)ftM:TlNOINC 3. SOLID "ODELING 4. UNISTR\JC II s. PATRAN-9 s. ICE" SCt-tE""TJ~ 7. ICE" TEKROUTE 8. P\.OTTINO .. G. OETAILER DRMIINOS ENTER TASk _ ? i ________ 4. S. ENTER TASt( ., ., tF-~!CIj 1Sf1 US ICH PAT ,PATf'''' TEl( PLOT OETAIL OETAILER DRMIINOS EXIT 1. 2. 3. ? o ('\ GENERATE DETAILER DAMnNS! FROft LAYOUT ASSEf't9l.E DETAILER DRAWIN9S INTO LAYOUT CREATE/EDIT PART HISTORY FILE ATTACIi GPARTS FILE TO USE WITH DOff ~~ ASOa. PHEOIT GPATCH ___ _ ENTER THE PMTMO ____________________________________________ FOR THE ~1N8 OR CR TO RETURN ___ 1:Q_el~,~_e~!_~~~~! DURING nus SESSION, WILL YOU SltYE PMTS ON THIS m-MTS FILE? ENTER YES OR NO (YIN) ~-- ATTACHING THE GLOBAL DfMVING FILE - OPMTha•• •••• PLEASE SPEC I FY THE MMfING FILE SPECIFY FILE 1. EXIT 2. SPECIFY BY FILE tW1E 3. LIST AVAILABLE FILES 4. CREATE A NEW FILE SELECT OPT ION £,EleIT N,tWE L,LIST CR,CREltTE ., ~------ ? e~!~ __ ENTER THE PERtW£NT FILE NN£ OR CR TO EXIT ENTER THE NOS USER NNE FOR ? nus FILE OR CR FOR YOUR OWN ••• THE FILE HAS BEEN ATTACHED ••• FILES ENTER APPLICATION ALTER~TE 1. Z. 3. 4. S. s. RETURN TO TASK IENU ~ILES RETURN LOCAL FILES ATTACH ~ILES BY FILE TYPE ATTAC~ FILES BY FILE NAME LIST LOCAL SELECT OPT ION APPl..,GO E,EXIT L,LISTLF R,RETlJRtII T,TYPE N,NAME ? ---------••• NOV ENTERING ICE" DON ••• Figure 4. Computer-User Dialog During the GP1~R'I'S File to Use t'Ji th DDN" Task . "Attach 4: . '" /' • C) CONTROL DATA CORPORATION 3-D PIECE PART EXTRACTION FROM LAYOUT DRAWING SEPTEME:EF~, 1985 INSTALLATION INSTRUCTIONS C) DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functionins of undescribed features or parameters. Control Data Corporation gives the user permission to reproduce this documEnt. o • CONTROL DATA CORPORATION 3-D PIECE PART EXTRACTION INSTALLATION INSTRUCTIONS Pase 2 SEPTEMBER, 1985 RELEASE DESCRIPTION !3-0 Piece Part Extraction from Layout Drawing! is an enhancement to ICEM EOl Version 1.2 which runs under the CDC Network Operating System (NOS) Version 2. This enhancement enables you to extract piece-part geometry for detailer drawings from 3-D layout drawings. It also allows you to reassemble detailer drawings into layout drawing. A comparison between the original drawing and the reassembled drawing may reveal design error. Your only input is the part identification number, which is the same as the 1-70 characters long PARTNO you used while creating and/or modifying the layout drawing in ICEM DON. The system scans the database, attaches all necessary files, generates trace files to run DON, runs DON to save parts on GPARTS file or restore parts from GPARTS file. To inform the system what components a layout drawing contains and their levels of definition, the user also supplies a file called ·Part History File.· Part history file data structure is explained in the User's Manual. To assist the designer to create and/or edit the part history file, this enhancement provides special capabilities as described in the User's Manual. Also, this system enables detailers to set access to the GPARTS file by entering the PARTNO for the layout drawing. To use this enhancement, you should already be using or willing to install NOS Operating System Version 2.0, EDl Version 1.2 and DON Version 1.57. This enhancement will be operational in any later versions of these products, but not necessarily in earlier versions. c HARDWARE CONFIGURATION The minimum hardware configuration required for NOS2, EDl and DON is also required for this product. RELEASE MATERIALS The 83-D Piece Part Extraction! release magnetic tape with VSN of TOREl1. This characteristics! 9-track with 1600 bpi TOV10 as the file 10 in the HORl label, File 1 : files reside on the tape has the following binary recording mode, and 6 files. Installation Procedure File ry + FORTRAN routines that will be added to the EDl File 3: FORTRAN capsules that will be added to the EDl ~. File 4: Procedure file to be included in the EOl C • GONTROL DATA CORPORATION Page 3 3,--D PIECE PAf:!T EXTRACTION iNSTALLATION INSTRUCTIONS o SEPTEMBER, 1985 File 5: Transaction file to be included in the EDL File 6: A procedure to compile the FORTRAN routines (File Z), FORTRAN capsules (File 3) and implement them in EDl ~ NOTES AND CAUTIONS All limitations applicable to NOSZ, EDl, and DDN also apply to this product. If your EDL is already customized, running the procedure (File 6) may wipe out your original customization routines. Hence, modify File 6 as necessary if the EDl is already customized. This product is expected to provide the capabilities described in the User's Manual. If you have some special needs, you ffiay modify the enhancement programs to meet your needs. Control Data will assist you to meet your special requirements. INSTALLATION PROCEDURE The files which are part of this product are installed by executing the installation procedure which is File 1 of the TDREll tape. To install the files, submit the tape to the computer operator and enter the following commands from your interactive terminal under DBA account number. C) LABEL,TAPE,VSN=TDREll,NT,l=TDV10,R,F=I,PO=R,D=PE,LB=KL. COPYCF,TAPE,INSTAl. BEGIN"INSTAl. This procedure will install the following indirect access files! TDFTN,TDCPSl,TDPROC,TDTRAN,and TDFTOE. If you already have files with these names, transfer them to different names before running this procedure. Modify the transaction file TDTRAN using XEDIT or FSE. all aMLSZ154 8 to DBA account number. Chanse Clear all local files and then execute the procedure TDFTOE by entering the commands: CLEAR. GET,TDFTOE. BEGIN"TDFTOE. o This will update your EDl files by including the new capsules and FORTRAN routine. This will also create a new indirect access file TDLIB. - .. __ _ ._,,-_._.. ....... __.• -._..- ...... __... _._--- • CONTROL DATA CORPORATION 3-D PIECE PART EXTRACTION INSTALLATION INSTRUCTIONS • I, SEPTEMBER, 1985 (,,'- .. " Next, update the EDl menu database in the following ffianner: Enter EDL using an 10 with SYSADMIN privileges (like EDLID): A. Choose the UPDATE EOl FOR ENGINEERING DATA task (task command UPDATE). i. Tell the EDl that· the file is an UPPER CASE TEXT FILE. 2. Give the data a meaningful name like MOB TRANSACTIONS FOR 3-D PIECE-PART. 3. The APPLICATION DATA TYPE is EDL MDB TRANS?\CTIONS t B. Enter the task command MENUMGMT. 1. Retrieve the data which you just entered into EDL. 2. Select that data, and the changes will be automatically entered into EDL. To check whether there was any error while modifying the EDL menu database, review the file MDBLIST by entering EDIT task. If there is no error, enter into ICEM task. The ICEM APPLICATIONS task menu should show the additional task DETAILER DRAWINGS. Next, update the EDL Engineering Database in the followins ITI.anner: A. Choose the INTERACTIVE QUERY UPDATE task (task ITI ITI and Q 1I ) • c0 1. When Query Update responds with the prompt --; enter INVOKE EDLDATAW OF EDLDATA KEY SEDLORDBA$ USING E120DDE: all in one line. 2. When Query Update returns with the prompt --; enter STORE SETTING FTFTC,FTNAM,FTLFN.FTLFNR,FTAPN, FTMUL,FTCHR,FTPRT all in one line. · ) Page 5 CONTROL DATA CORPORATION PIECE PART EXTRACTION iNSTAllATION INSTRUCTIONS ~-D 3. SEPTEMBER, 1985 When Query Update returns with the prompt enter- », $PARTbHISTORYbFIlEbbb$bSPARTbHISTORYbFILEbbbSb $P~d:;':THIS$b+ $T$b$ICEMbDDN$b$TSbSD$b$T$ where b is a blank space. shown. Enter the data just as », 4. When Query Update returns with the prompt enter )KEND 5. When Query Update returns with the prompt --, enter STORE SETTING ATADT,ATNAM,ATFTC,ATSIDR,ATTNA all in one line. 6. When Query Update returns with the prompt enter », SPARTbHISTORYbbbbbbbb$b$PARTbHISTORYbbbbbbbb $b$PARTbHISTORYbFILEbbbSb+ $F$b$bb$ o _ where b is a blank space. shown. 7. When Query Update enter Enter the data Just as r~turns with the prompt », )l(END 8. When Query Update returns with the prompt --, enter END You will be back at your last EDL menu. Next, enter into GROUP ADMINISTRATION task (task command is GROUPADMIN) i. Create a new group with a meaningful name. 2. Add the names of all staff who are likely to use o (a) GENERATE DETAILER DRAWINGS FROM LAYOUT ---"'--'--"-'---" _..- ....._------------- .. _.. __ ... _._-_. __ ._--_._----- Page 6 CONTROL DATA CORPORATION 3-D PIECE PART EXTRACTION INSTALLATION INSTRUCTIONS SEPTEMBER, 1985 (b)~SSEMBLE DETAILER DRAWINGS INTO LAYOUT and (c) CREATE/EDIT PART HISTORY FILE tasks, as members of the newly created group. 3. Give task access to the group. DTLDRW. Task name is That will complete the installation procedure. VERIFICATION PROCEDURE To verify the proper functioning of this enhancement, 1. Have a 3-D layout drawing where component piece parts are defined at pre-set levels, available in the drawing file. 2. Create a part history fil~ for this part, using the task CREATE/EDIT PART HISTORY FILE. (Data structure is explained in the User's ManuaJ.). 3 Select the GENERATE DETAILER DRAWINGS FROM LAYOUT task. Upon completiony examine the newly created GPARTS file by selecting the F.6.1.Z+3 menu in DON. t 4. Select the ASSEMBLE DETAILER DRAWINGS INTO LAYOUT task. Review the reasssembled drawing for the completeness of the task. 5. Select the ATTACH GPARTS FILE TO USE WITH DON task to verify that proper files are attached when the PARTNO for the layout drawing is supplied by the user. To add any special locaJ. CDC analyst. re~uirements for you~ site, contact your c --- --- CDC 790-20 WORKSTATION TEKEM MICROCODE Version 3.0 RELEASE 003 Product 790-202 tor tne Control Data 790-20 Workstation c ************************* • ** RRRR EEEE M M E'EEE ! ! • 000 A ..' * Mf1 MM E 0 A A 0 * RRRR R EEEE AAAAA !! M M M EEE 0 0 ** ** R R E M E M A 0 0 A . M M EEEE ! ! • * R R EEEE A A ODD * Cr Itlcal I n for ma t I on i s contained in this * * * document. At tile very least you * * * * MUST READ THE NEXT PAGE COMPLETELY!! * * * * ************************* o .. _-_ .. - - -----'-"------ ._-- .-.----- TEKEM .V3.0 Microcode SR8 p ;;tge2 IF YOU WANT TEKEM V3.0 TO WORK RIGHT (AND WE ALL KNOW THAT YOU DO) THEN IF YOU DO NOTHING ELSE READ THIS 1. You must fol low the instructions in section 5 to change the alpha baud rate and tablet switches or TEKEM V3.0 ~ll!_nQ.l_~Q.r.li. c' I "' o Page 3 TEKEM V3.0 Microcode SRB If any difficulties arise in the installation or operation of th I s product, p I ease ca I lApp' i cat ion Centra I Suppor t at one of the following phone numbers: External Domestic Users Internal CDC Users International Users 800/638-8502 (to II free) CDC Controlnet 232-3900 USA 301-340-3900 These support hotlines operate Monday through Friday, except holidays, 8:00 a.m. to 5:00 p.m., Eastern time. o _._--_ .. _._-... -._-_.... __. _. .---- ._-_.. __ .- .--_' _.. .,..I TEKEM V3.0 Microcode SRB Page 4 TABLE OF CONTENTS fQg~ 1.0 INTRODUCTION • • • • • • • • • • • • • 5 2.0 REFERENCES • • • • • • • • • • • • • • 6 3.0 HARDWARE/SOFTWARE ENVIRONMENT. • • • • 7 4.0 GENERAL SOFTWARE DESCRIPTION • • • • • 8 New Features • • • • • • • • • • • • Fixed Features • • • • • • • • • • • 10 INSTALLATION OF THE PRODUCT. • • • • • 12 Terminal Configuration Changes • • • Tablet Switch Changes. • • • • • • • 12 14 6.0 DOCUMENTATION ADDITIONS AND CHANGES. • 15 7.0 KNOWN PROBLEMS AND WORK-AROUNIJS. • • • 22 4.1 4.2 5.0 5.1 5.2 8 ('\ I .~ o TEKEM V3.0 Microcode SRB 1.0 Page 5 INTRODUCTION The CDC 790-20 is an ergonomic workstation used with ICEM appl ications on both the CVBER 120 Application Processor and CVBER 800 mainframe computers. The CDC 790-20 has two display screens, one high resolution color graphics and the sec 0 n d s c r 0 I lin 9 a I p h a nu mer i c. I t a Iso has a key boa r dan d tablet. The TEKEM microcode provides the program for the CDC 790-20 to operate in one of two modes: 1. Transparent Mode - the alphanumeric terminal is directly connected for standard host operating system communication. 2. Tektronix[ll 4115 Emulation Mode the terminal operates like the Tektron i x 4115 graphics terminal substituting the separate alpha display for the Tektronix dialog area. This SRB describes TEKEM V3.0 which is a corrective code release of the CDC 790-20 microcode. This microcode is delivered on one 3 1/2 inch diskette for loading on the CDC 790-20. This .version differs from previous versions. It was oroduced by Control Data elM Development. With certain restrictions, third party applications may also be used with the CDC 790-20 in Tektronix 4115 emulation mode or transparent mode. r his S RB C0 cum e p t s the f 0 I low i n g imp 0 r tan t i t em,s : chan ge s to o Installation Changes required terminal operate properly with this new microcode. o New Features operation. o Fixed Features lists the features that operated improperly in past releases that have been fixed. o Outstanding Problems which corrective action completed. descriptions of new features and their hight ights known problems for is in process, but not yet o [1] Tektronix is a registered Inc., Beaverton, Oregon. trademark of Tektronix, "I' TEKEM V3.0 Microcode SRB 2.0 Page 6 REFERENCES o CDC 790 ICEM Ergonomic Workstation - Tektronix Emulation Manual - 62950166 o CDC 790 62950150 o CDC 790 ICEM workstation Communications Interfaces Installation and Maintenance Manual - 62950153 o Series ONE The Thin Dimension - Graphics Tablet User's Manual - Kurta Corporation o Tektronix 4110 070-3892-00 o Tektronix 4110 070-4664-00 o Tektronix 4115B Co~puter Manual - 070-4665-00 IeEM Ergonomic Workstation - Owner's Manual - Series Command Series Host Reference Programmers Display Terminal Manual Manual Operators I ... o Page 7 TEKEM V3.0 Microcode SRB 3.0 HARDWARE/SOFTWARE ENVIRONMENT 3.1 Hardware Requirements This microcode product executes in the CDC 790-20 graphics workstation configuration to control its operation. The CDC 790-20 consists of microprocessor display list and graphics processors, a high-resolution color graphics display monitor, an alphanumeric monitor and keyboard (which is the CDC 721 display terminal), and graphics tablet. CDC basic Options ava; lable to the configuration and supported by TEKEM following: C) o 79n-20 hardware V3.0 include the o Display I ist memory expansion from 1MB to 2MB. o Seiko color hardcoPY with Centronix parallel o Kurta 3-button cursor. interface. \ ............/ TEKEM V3.0 Microcode SRB 4.0 Page 8 GENERAL SOFTwARE DESCRIPTION Refer to the referenced CDC 790-20 manuals for detai led information about this product. In particular, refer to the "CDC TQO ICEM Ergonomic Workstation Tektronix Emulation" manual. The inforrr.ation that follows in this and subsequent sections refers to changes to that manual. 4.1 4.1.1 New Features Seiko Parallel Hardcopy In previous versions of TEKEM the Seiko graphics printer was supported using the RGB video interface. This version provides for support of a paral lei interface that makes exact screen copies of the graphics displayed. Microcode options are provided to support dithering for higher color resolution and selectable dark background or inverse hardcopy background. 4.1.2 Segmented Display List Speed-up Processing of segmented display list drawings from the host (also known as a "host repaint" when using ICEM DON) has been improved so that host paint times are reduced by up to a factor of eight.4.1.3 Run-Length Coded (RLC) Display Speed-up Processing of RLC drawings (typical of the ICEM Solid Modeler shaded picture drawings) has been improved so that paint time is reduced by up to a factor of four. 4.1.4 19.2 and 38.4 ~bps Communications Communications from the CDC 790-20 are now supported at asynchronous speed of up to 38.4 Kbps. On CVBER 120 Appl ication Processor systems 19.2 Kbps is supported from all ports. AP ports can be specially configured to operate at 38.4 Kbos as can the master console port. CVBER 800 systems require the CLA performance upgrade to operate at rates above Q600 and, if provided, will operate at up to 38.4 Kbps. 4.1.5 Local TEKE~/Transparent Mode Toggle In previous versions only receipt of the proper host command could cause the terminal to go from TEKEM to transparent mode. Similarly, to go from transparent mode to TEKEM required a host command or terminal reset. o TEKE~ V3.0 Microcode SRB Page 9 A local function that allows the user to toggle between the two modes at wi II is now provided. The mechanism is to hit the BREAK key twice, rapidly. A ti~e delay is used to detect the difference between a single BREAK that should be forwarded on to the host and a BREAK/BREAK that causes the mode toggle function. Note: The BREAK/BREAK sequence does send two to the host in addition to toggling the mode. 4.1.6 BREAK signals 2MB Display list TEKEM V3.0 allows installation and utilization of the 2~B display li.~t option. The microcode will automatically detect the presence and enable use of the extra memory without any user or engineer intervention. Previously a manual confiquration process was required to enable access to this memory. 4.1.7 Three-Button Cursor A 3-button cursor, also called a "puck", may be installed on the Kurta tablet. Although not strictly being provided as a new feature it 1s highlighted as a new option that may be obtained and installed to replace the pen stylus. TEKEM V3.0 provices no support for the multi-button functional ity of the puck at this time. 4.1.8 AI~ha Terminal Speed-up The communication rate to the alphanumeric terminal is doubled from 9600 bps to 19200 bps. This allows much better oerformance ma~ching for text operations between the host and the alpha monitor wheri host connections exceed 9600 bps. Performance is not significantly improved when scrolling is enabled due to increased processing overhead in the alpha monitor. Improved Memory AI location Display I ist memory use per segment has been reduced 25%. Th i s ~ i I I a I t ow more segment s to be stor ed in the same amoun t of display I ist memory. 0 , \ TEKEM V3.0 Microcode SRB 4.2 Page 10 Fixed Features A major emohasis of this release is to provide corrective code rather than new features to the field users of the CDC 790-20. The items below list some of the major functions and features that were either missing or significantly deficient in previous releases of TEKEM. Not all fixed features are listed. Refer to the later section describing outstanding bugs for a I ist of a" reported problems that are stili not fixed in this release. 4.2.1 Panel Fi II Panel fill operations is now more robust in function and with improved performance. Panel fill with or without boundaries wor~s. The various ways polygon boundaries may intersect, forfT' islands, etc., are handled properly for panel fi II. 4.2.2 Diskette Boot Time i~...... ........,-, At first use of TEKE~ V3.0 the user wil I notice a significant speed-up in diskette toot time. The time is reduced from about 65 seconds to 33 seconds. (- 4.2.3 Dragging In previous versions entity dragging (attaching segments as the cursor) did not work at all. This feature is improved so entity dragging can now be performed. CAUTION: Refer to the I ist of outstanding problems for the description of the limitations of this feature. 4.2.4 Highlighting· Entity highl ighting (bl inking) now functions properly and uses a clock rate for consistent bl ink frequency. Because of processing overhead selection of a large number of entities for simultaneous highlighting may cause the blinking time to become large. 4.2.5 Communication Flagging Input and output flow control operations are working properly. This f lxes many reported problems that were caused by loss of process synchronization and loss of data due to inadequate flow control by TEKEM. 4.2.6 Display of Facetted Pictures C_.' o TEKEM V3.0 Microcode SRB Page 11 The DON facettea method to display surface shaded pictures now works properly. 'This was fixed by properly handl ing communications flagging. 4.2.7 Tablet O~erations Two tablet problems have been fixed: (1) Frequent manual resets and (2) Inability to detect back-to-back picks at the same position. 4.2.8 Tablet Typeahead During some operations tablet picks would be lost. A tablet typeahead buffer of 50 tablet picks has been added to queue the user's tablet entrfes. 4•2•q .S rea k Fun c t ion The "BREAK" key did not operate properly in previous TEKEM versions. This presented a problem with CYBER 120 AP installations where the BREAK function is an important exception signal ing mechanism. This function now operates properly. 4.2.10 Set-Up MOde Back Space The back space key now works when entering and correcting Set-Up mode parameters. 4.2.11 Transmit Limit A transrT·it I imit is now imposed on character transmissions. This implies that although the output rate on a bit-wise basis wil I conform to the selected baud rate, the net output rate on a character-wise basis wil I be constrained to a potentially slower rate. The default is 9600 bps. 4.2.12 Terminal hang with Large Drawings The terminal no longer hangs when display list memory is exhausted. It operates as expected: drawing continues but' a repaint will be of only that part of the display list received before memory was exhausted. G I TEKEM V3.0 Microcode SRB 5.0 Page 12 INSTALLATION ON THE CDC 790-20 Normal installation of TEKEM microcode requires no more than insertion of the diskette and a boot operation. Because of changes made to improve performance and correct problems two changes to the basic configuration parameters in the CDC 790-20 must be made at the time of installation of this diskette. These changes are a one-time change. Once the changes are performed on the CDC 790-20 no fu~ther action is required to operate with TEKEM V3.0 on a continuin~ basis. 5.1 Term"i"Ral Configuration Changes " The alohanumeric terminal in the CDC 790-20 is a CDC 721. The default baud rate of the terminal must be changed from 9600 bps to 19200 bps. Perform the change according to the steps below. Reter to page A-3 of manual 62950166, "CDC 790 ICeM Ergonomic Workstation - Tektronix Emulation," and perform the following steps to change the default baud rate. The steps below assume that other steps have already been performed and that the CDC 790-20 works with prior TEKEM versions. Refer to the documentation change description in the sections that follow for complete details of the manual change: Step 1. Reset the alpha RESET button. terminal using the rectangular Step 2. Depress SETUP (second key from the left in the top row); then depress FlO twice; then depress CONTROL/SETUP. Step 3. No action required. Step 4. Depress FlO. Step 5. When the mode prompt "ENTER MODE n de pre s s "l·~. (1-6)" appears Change the default baud rate from 9600 (code OOAA) to 19200 (code OOSB) in configuration parameter F9 by entering first "F9"; second enter "OOBB". DFTR OOBS 1 1 •1 _ _ _ _ _ _ _ _ 1 (The display for F9 should be changed to look like this.) TEKEM V3.0 Microcode SRB Step 7. Page 13 Save the changed state by depressing the COpy key and then depress F1 twice to return to the original set-up state. Reset the terminal again and boot the terminal. NOTE FOR CVBER 120 AP USERS: You must perform the above steps exactly the same but sub st it ut i n9 an entr y of "5" f or the "ENTER MODE n (1-6)" response to set the SMALL CVBER default baud rate. Some AOS/VS utilities require the alphanumeric terminal be cont igured to operate' in Mode 5 and the default baud rate for this mode must also be 19200 bps. o o TEKEM V3.0 Microcode SRB 5.2 Page 14 Tablet Switch Changes ~his change sets the tablet to work in streaming mode rather than delta mode. This allows multiple picks to work properly when the stylus/puck remains in the same position. The Mode/Baud switches should be changed to the following positions. The switches are located on the rear of the tablet, possibly under a rrotective adhesive label: NJ !::!..- 5-1 - OFF 5-2 - OFF 5-3 - OFF 5-4 - ON ~L r:. d N 6 /.J b~r o~ The Program Switch should be as follows - 51 - OFF 52 - OFF 53 - OFF 54 - OFF 55 - OFF 56 - OFF 57 - OFF S8 - ON C C: o Page 15 TEKEM V3.0 Microcode SRB 6.0 DOCUMENTATION ADDITIONS AND CHANGES The following notes are corrections and additions to the "CDC 790 ICEM Ergonomic Workstation - Tektronix Emulation" manuat, publ ication number 62950166. It is recommended that the pages that follow be copied and inserted into your manual so that future references to the manual contain up to date information. b.1 Setup Parameters (p2-3) Replace the "TERMINAL STATUS" table and the "Changing Setup Parameters" sections with the following page. The "Saving Setup Parameters" section remains the same. o ----- ----- ---- TEKEM V3.0 Microcode SRB Page 16 (Replacement page for Manual 62950166 page 2-3. TEKEM V3.0) TERMINAL STATUS GENERAL ECHO LOCKKYBD DAENABLE IGNOREOEL LFCR CRLF SAVECONFIG SCROLLING SNOOPY • TABLETECHO • HCDITHER • HCINVERSE ERRORLEVEL YES NO YES NO NO NO NO NO NO NO YES NO ~. 2 I ~, COMMUNICATIONS BAUD RATE STOPBITS PARITY PROMPTSTRING PROHPTMODE QUEUESIZE FLAGGING BYPASSCANCEL LOCAL/REMOTE * 19200 1 NONE .? • NO . 8100 IN/OUT (NL) REMOTE New parameters this release. Changing Setup Parameters (Note: r~place The first paragraph remains the same. Delete the second paragraph with the next section.) ana c . TEKEM V3.0 Microcode SRB 6.2 Page 17 Transmit Rate Limit Feature (p2-3+) Add the page whi ch fol19wS to the manual after page 2-3 as new information. Transmit Rate Limit The SET-TRANSMIT-LIMIT command imposes an upper bound on how fast the terminal may send characters to the host computer. This ~ust be entered by means of the encoded escape sequence described below and in the Tektronix reference manuals. C) o This may be useful in circumstances where the host cannot process characters as fast as the terminal can send them over the communications line. The default transmit limit is 9600 bps. SYNTAX RANGE IS LIMITED TO -65535, 65535 WINDOW DOES NOT CHANGE WHEN VIEWS ARE CLUSTERED VIEW BOX IS LEFT ON THE SCREEN AFTER POLYGON ERASE. BORDER NOT DISPLAYED ON CHANGING VIEWPORT WITH NEXT VIEW KEY. SETTING OVERVIEW WINDOW. IN PROMPT MODE, PROMPT STRING IS DISPLAYED t NO INPUT IS RETURNED ( ) \ I I -- -- --- -- ------ --' .--.---.- o Page 19 TEKEM V3.0 Microcode SRB 6.4 New Setup Commands Cp4-1) (Add the 4-1.) fol lowing descriptions of new Setup commands at page Table 4-1 (Additions). HCDITHE~ HCINVERSE TABLETECHO Setup Mode Commands Set hardcopy dither mode (YES,NO) Set hardcopy background inverse (YES,NO) Set tablet audible echo mode (YES,NO) o o .... _ ... ,---- --_. '" ._---,,_... -.... __ ... _-------'"' ... ,----_. __._---_ ... TEKEM V3.0 Microcode SRB Page 20 Misc. Changes 6.5 (Please ~ake the tol lowing 'changes by marking up your manual original. The changes described are not significant enough to require complete page replacement.) 6.5.1 CDC Application Hot-Line Phone Number (pA-l) Change the number in section CDC APPLICATION HOTLINE to 1-800-638-8502. 6.5.2 Alpha Terminal Set Up (pA-I) At the bottom of page A-I in section SETTING UP THE ALPHA TERMINAL there is a statement that reads as fol lows: You may notice that there is also a BAUD parameter shown. This should be set to 9600, regardless of the workstation host connection. ~ Change the rate mentioned as the default term ina I to read 1<1200' instead of 9600. 6.5.3 rate for the alpha Configuration Parameter F9 in Step 6 (pA-3) In step 6 of the alpha set up sequence shown on page A-3 the box for F9 shows "COAA". Change it to show "OOBB". F 9 DFTR OOBS I1 _ _ _ _ _ _ _ _ I, (The display for F9 should be 'changed to look like this.) ( ''-.... . CDC 790-20 WQRKSTATION TEKE~~ MICRCCUOE Version 3.1 RELEASE 004 Product 790-202 for the Control rata 790-20 Workstation *....,.. * ...... ...,.. C~ * *.... *... ." 'r ... ... ... ~. "t" "t" R RR F~ R RPRPRR RR RRR RR RR RPR~R R~ R RRRP ...... RP RR ...* R~ ... ... ... ...... RR RR 'r ~R .,. .'. ~. ." .... .,..... .,.... ...... ~ EEEEEEEE EEEEEEEE EE EE EEEEEFEF EEEEEEEE EE EE EEEEEEEE EE EEEE EE ***** At. AAAA AA AA AA AA At..AAAAAA AAAAAAAA AA AA AA AA AA AA AA AA .,..... * ...... ",... .,'... ...... ....'- .,..... ODDDODO DO Dr DD DO DD CD DC' DO DO DO DD DO DD DO OD Dr. DDDDDro * ... "t" * ..... .,.... ' :;c MM MM EEEEEEEE ~iM~ Mr-'M EEEEEEEE ~M MM ~M EE MM Mf'4 ~M EE MM MT-'. M~l EEEEEEEE MM EFEEEEEE MM ~~ M EE MM ,..M EE (-'1M MM ~M EEEEEEEE MM MM EEEEEEEE J • t .....' ... ...... ...... ..... "t" , ... .... .. ..'...... ... ", , , ~. ~. Critical i n for rna t i on i s contained in this document. At the very least you ',' * * *.,.... ...... ...,,... ...... ...... ~. *..... , r,UST REAC THE NEXT PAGE COMPLETELY!! *... ~, ...... ...... ,','.. ... ...... .,'.. ..... ~. , ' ',' ..,.... ... ',' :~ * ...'" ...... .,'... .,.... -._ ......... __ .. _. . . . .- _.. _. . _ - - * * * ...... ....... * ... ." * ....... * * ...... * ....... Page 2 · TEKFM V3.1 ricrocode SRB IF YOU WANT TEKEM V3.1 TO WORK RIGHT (AND WE ALL KNOW THAT YOU DO) THEN IF YOU DO NOTHING ELSE READ THE FOLLOWING SECTIONS 1. Tablet Overlay installation. Refer to section 4.1.7. 2. Setup of Alpha Terminal. 3. AUTONEWLINE Setup section 4.1.<1. Refer to section 6.4. parameter for IeEM users. ~efer to c TE~E~ V3.1 Microcode SRB Page 3 G If any difficulties arise in the installation or operation of this product, please call Application Central Support at one o f t h e f 0 I low i n 9 p h 0 n e n u IT! be r s : P'.t. I __ )-P / 2External Dcmestic Users Internal CDC Users International Users -&0 0/63-8-8 50~to I I free) CDC Controlnet 239-2739 USA 612-482-2739 These support hotlines operate Monday through Friday, holidays, 8:00 a.m. to 5:00 p.m., Central time. c o except Page 4 TEKFM V3.1 Microcode SR8 TABLE OF CONTENTS 1.0 I~TROCUCTIO~ 2.0 REFERENCES 3.1 HARDWARE/SOFT~ARE 4.0 GENERAL SOFTWARE DESCRIPTION 4.1 4.2 5.0 6.0 T~E PRODUCT Installation of Tablet overlay Label ing of Puck Buttons How to order three button puck DOCUMENTATICN 6.1 6.2 6.3 6.4 7.0 New Features Fixed Features INSTALLATION OF 5.1 5.2 5.3 E~VIRONMENT ADDITIO~S AND CHANGES Determining Setup Parameters. Setup Parameters New Setup Commands Misc. Changes KNOWN PROBLEMS AND WORK-AROUNLS TEkEM V3.1 Microcode SRB 1.0 Page 5 INTRODUCTION The CDC 790-20 is an ergonomic workstation used with ICEM appl icaticns on both the CYBER 120 Application Processor and CYBER BOO mainframe co~puters. The 790-20 has two display screers, one high resolution color graphics and the second scrol I ing alphanumeric. It alsc has a keyboard and tablet. The TfKEM microcode provides the firmware for the 790-20 to operate in one of two modes: 1. Transparent r-'ode - the alphanun·eric terminal is directly connected for standard host operating system communication. 2. Tektronix[!l 4115 Emulation Mode the operates I ike the Tektronix 4115 graphics substituting the separate alpha dis~lay Tektronix dialog area. terminel terminal for the This SRB describes TEKEM V3.1 which is a corrective code and feature enhanced release of the 790-20 microcode. This microcode is deliverec on one 3 1/2 inch diskette for loading on the 790-20. With certain restrictions, third party a~pl ications ~ay also be used with the 790-20 in Tektronix 4115 emulation moae or transparent mode. This SR8 documents the following important items: o New Features operation. o Fixed Features I ists the features that operated improperly in ~ast releases that have been fixed. o Outstanding Problems which corrective action completed. Ll) o ..... descriptions of new features and their highl ights known problems for is in process, but not yet Tekt~onix is a registerea Inc., Beaverton, Cregon. __..._.."._- - - - - - - - - ' - - - - - - - - - - - - _ . _ ... __.......... trademark .. of Tektronix, Page 6 TEKEM V3.1 Microcode SRB REFERFNCES 2.0 o o "'- •.. cnc 790 ICEM Ergonomic Workstation - Tektronix r.anual - 62950166 CDC 790 ICEM / E~ulation Ergonomic Workstation - Owner's Manual - 62950150 o CDC 790 ICEM ~orkstation Communications Interfaces Installation and Maintenance Manual - 62950153 o Series ~anual ONE The Thin ri~ension - Graphics Tablet User's - Kurta Corporation o Tektronix 4110 070-3892-00 Series Comn.and o Tektronix 4110 070-4664-00 o Tektronix 41158 Computer Manual - 070-4665-00 Series Host Reference Programmers Display Terminal Manual Manual Operators c~ C", ·TEKE~ Page 7 V3.1 Microcode SR8 3.1 HARDWARE/SOFTWARE ENVIRONMENT 3•1 Ha r d war eRe qui r e e n t s "I Tris microcode product executes in the CDC 790-20 graphics workstation configuration to control its operation. The 790-20 consists of ~icroprocessor display I ist and graphics' processors, a high-resolution color graphics display monitor, an alphanumeric monitor and keyboard (which is the CDC 721 display terminal), and graphics tablet. Options avai labl e to the bas ic 790-20 hardware cont iguration and supported by TEKE,., V3.1 include the following: o Display I ist memory expansion from 1MB to 2MB. o Seiko color hardcopy with Centronix parallel o Tektronix 4692 interface. o o v'K u r t a color interface. hardcopy with Centronix parallel 3 -b u t ton cur s 0 r • The following item is no longer a supported option: o DCSL coaxial interface to CYEER 600 processors. o --_.. _---_.• _.. _----_ .. _.__ ... ,._--_.... ..... _-_ ............----., , ... ,."._-_.- .TEKEM V3.1 Microcode SR8 4.0 Page 8 GENERAL SOFTWARE DESCRIPTION Refer to the referenced CDC 790-20 manuals for detai led information about this product. In particular, refer to the "CDC 790 ICEM Ergonomic Workstation Tektronix Emulation" manual. The infcrrration that follows in this and subsequent sections refers to changes to that manual. 4.1 4.1.1 New Features Numeric Keypad The numeric keypad keys operate as cursor controls whenever the thumbwheels crosshairs, zoombox, or panbox is "up". The Remainder of the time, the keypad prOduces numeric data. 4.1.2 Tek 4692 Hardcopy TEKEM V3.1 now supports both the Seiko and Tek 4692 hardcopiers. The device in use is selected in Setup mode ~y setting the parameter HCTYPE (SEIKO/TEK 4692). (Note: Interface cables are different between the two units.) 4.1.3 Scrolling Additional scroll ing features have been implemented in TEKEM V3.1 which provide the user with greater flexibi I ity and a lar~er scrol ling buffer. If desired the user can disable s ere r lin 9 bye n t e r i n 9 SET UP m0 ae 2 n d ch a n gin 9 the val u e 0 f the S CR0 LLIN G par am e t e r fro m II YES I' t o " NO" • As be for e , scre II ing works when in TEKEM mode and not ~hen in Passthru _ mode. The SCROLLING parameter is saved on the TEKEM disk, to be restored at boot time. Thus, the user can disable SCROLLING at boot time by doinq the following. 1. Enter SETUP mode 2. At the SETUP prompt type: * SCROLLING NO * SAVECONFIG * 3. It is not nessesary to ~e-boot TEKE~. SCROLLING is automatically disabled with the SCROLLI~G NO command. The next time you re-boot TEKE~, the Saved SCROLLING para~eter wi I I be restored from the configuration file as NO, and SCRCLLIJ\G wi II be di sabl ed. C' r c Page 9 TEKEM V3.l r.icrocode SRB o ToR e - e nab I eSC R0 LLIN Gat boo t t i ni e, 1. Enter Setup mode. 2. At the SETUP prompt type: SCROLLlt\G YES SAVECONFIG 3. 4.1.3.1 * * * Again, 00 the f 0 I low i n 9 • Re-boot is not nessesary. Control I in9 th~ The followi ng commands the dialog area: Dialog area: are new SETUP commands which affect DABUFF command specifies the minimum number of I ines the dialog area buffer can hold (of DACHARS length). rore I ines may be within the scrolling buffer depe:nding on the actual I ine lengths. The Q~.t.gy!.t. __ ~~!y.E_l~_l~Q I ines; however, the user can change it to any value from 24 to 16384. command specifies the size of the dialog area, i.e., the number of lines visible at once on the screen. There are only two possible values for this parameter: 30 and 24. The Q~igy!.t._~elYf_li_~Q lines. DALI~ES OACHARS command specifies the number of characters per I ine in the dialog area. The value of this parameter can be set at either 80 or 132. The Q~.t.aY!l __ l~ __ ~Q characters per line. 4.1.3.2 Scroll ing the dialog area: Function keys F11 and F12 have been designated for the use of scrol I ing the dialog area. When depressed alone, or with the Shift key and/or the Control key, the function ke},s (F11 f. F12) invoke the following functions: Shi ft Shi ft Control Control Control Shift Control Shift 4.1.3.3 0 F11 F12 F11 FI2 Fll F12 FI1 F12 o splay D splay o splay D splay D splay o splay D s~12Y D s~lay Qr~~lQu~_Qag~ of text. n~~l_Q~g~ of text. Qt~~lgy~_!in~ of text. n~~!_lin~ of text. Qr~!lQy.~_b~!l_Q~g~ of text. of text. IQQ_Qgg~ of text. BQ1!Qm_~gg~ of text. o~~!_bgll_Qgg~ Scroll ing performance: scro II ing The performance of i n TEKEM V3.1 i s much better compared to previcus releases. Speed i s notably the most improvement. significant The variable sized dialog are versions of TEKEM buffer i s a flexibility that the earlier did not have. Page 10 TEKEM V3.1 Microcode SRB 4.1.4 Tablet Zoon.ing/Unzoorring.') These two functons offer the user an alternative method of performing local zoom/pan functions. The original zooming and panning functions have not changed. (However, only one method or the other m2Y be used at one time.) To initiate tablet zooming, press the "tablet zoom" tablet k~y (refer to section 4.1.7, leftmost "key", button 0). Special colored crosshairs ~i I I appear on the screen. Using the tablet. select the position of one corner of the region you wish to zoom in on. This first corner is called the anchor point. Now a zoom box wi I I aDJ."lea r on the scr een. The zoom box wi I I "rubber band" on the screen as you move th~ pen/puck around on the tab let. T his a I low s you to se e wh at W ou I d bee en ta i ned within the zoomed view. Note that the aspect ratio of the zoo ", box i s a I way 5 ma i n t a i ned a s 5 : 4 in W0 r I cI spa c e coordinates. One corner of the zoom box is always the anchor poi n t c h 0 sen • T 0 zoo n: i n ma k e a t a b let pic kwh e nth e des ire d re9ion is enclosed by the zoo~ box. The zoomed view wi I I appear. If at any time prior tc completing the zoo~ you wish to exit without zcorr.irg select any tablet key. Tablet zooming \r;i II b e can eel led. The fun c t ion ass 0 cia ted wit h the tab let key pressed wi II not be executed. C _/,1 To zoom out, or "unzoorn", simply press the "tablet unzoom" tablet key in the tablet's menu area (second from the left, button 0). The field .... ill be zoomed out in all four directions by the unzooming scale factor (default is 1007.). If the scale amount is 501. the x and y dimensions wi II be increased by one half. For example. if the view coordinates were (1000,1000) to (2000,1800) and the unzoorn scale factor 50%, the resulting view coordinates after unzoorning would be (750,800) to (2250,2000). The overview window, as before, is the limit for unzoorning. Both the unzoorning scale factor and the tablet zooming crosshairs color are changeable through the new host command described in sectior. 4.1.4.1, Set Tablet Zoom Parameters. The defaults ~re: UnZoom Scale Crosshair Color Index lOOi. 7 c TE~EM o Page 11 V3.1 Kicrocode SRB 4.1.4.1 Set Tablet Zooming Parameters Command Description: This command sets the tablet zocminp crosshairs color and the tablet unzooming scale factors. Host Syntax: (esc)IZ int:scale-factor int:color-index Setup Syntax: None Parameters: scale factor Range: 0 The scale factor in the x- and unzoow.ed. For factor 100 would to 2**31 - 1 represents the perceptage increase y-dimensions when a view is example, a 10x8 view with scale be unzoomed by 1001. or 20x1b. color index ~ange: 0 to 32767 The color index parameter determines the color of the tat let zooming crosshairs which are used when selecting the first corner, or anchor point, of the zoom box. The color is selectable so that the tablet zooming crosshairs can be easily distinguished fro~ the gin crosshairs. C' Defaults: Scale factor On power up if omi tted 100 100 Color Index On power up if ommitted 7 7 Errors: IZ11 (level 2) 1Z21 (level 2) invalid scale factor inval id color index - - - _...." . _ - - - - - ••.........._.. _ - - TEKfM V3.1 Microcode SRE 4.1.5 Page 12 Previous Zoom Special Function The Previous Zoom Special fupction, labeled PREV ZOO~ on the tablet overlay, changes the vie~ing window to the previous zoomed windo~, if any. It is similar to the Restore key, except that no zoom or pan box is displayed. 4•1•6 T h r e e E. u t ton Tab let P u'c k TEKEM V3.1 now fully su~ports the three button tablet puc~~ The user may define key macros for any or al I of the buttons; the buttons may be defined in a variety of ways: 1. Define a button to operate just I ike a pen stylus pick. This is defined using a special function NOP (special ~ey COde -38). In this case, if tablet GIN is enabled and the button is pressed, a single GIN report is sent to the host with the button number as the gin report key character. (The buttons are numbered 0,1,2 from left to right.> If tablet GIN is not enabled, nothing will occur. 2. Define a key macro for a button. In this case, pressing the puck button results in one or more tablet GIN reports sent to the host if tablet GI~ is enablea (one GIN report for each character in the ex~anded key macro, with each character of the macro included i~ successive GIN reports as the key character). If tablet GIN is not enabled, the key macro characters are treated as if they had been input from the key~oard. (So these characters can cause thu~bwheel GIN events.> 3. Define a key macro for a button and treat the button as if it were a keyboard key. To do th is, the first value in the key macro definition must te GINSUP (i.e., -1) which serves as a flag to indicate tablet GIN suppression whenever the button is pressed. No tablet GIN events are caused by press ing the button. However, thi s button wi I I cause thumbwheels GIN events if thumbwheels GI~ is enabled. 4. Define a tutton to be a special function key. In this case, no GIN reporting occures. The special key function is performed. 5. Defaults: Button 0 has a default definition of NOP. Button l's default definition is special function "O~eration Complete" (til"). Button 2's default definition is special function "Operation Reject" ( " [ U ) . Ci .TEKE~ V3.1 ~icrocode Page 13 SRB The tablet GIN areas way be considered to be a very s~ecialized tablet key, PleCise read about tablet keys. 4.1.7 large, Tablet Keys Tablet keys are now defined on the tablet. (Please Refer to Figure 4) There are 23 "Keys" located in a 1" x 12" horizontal strip across the top portion of the active area of the tablet. Each key is 1/2" wide. These keys are considered to be an extension of the keyboard of TEKEM. Fourteen of the keys are predefinedj the remaining nine are undef ined (i .e., they are def ined to be NOP). All 23 keys are redefinable, however, just as the keyboard keys are. The predefined functions: keys TABLET ZOOM UNZOOM OVERVIEW PREY ZOOr. PAGE PASSTHRU BOTTCM TOP COWN LINE UP LINE H PG DOWN H PG UP PAGE DO~H·: PAGE UP CLEAR perform local viewing and Perform tablet-controlled zooming Perform fixed factor zooming out Same as OVERVIEW key Change to previous zoomed window. Same as PAGE key Enter/exit Passthru mode Display Bottom Page of scrolling text Display lop Page of scrolling text Display f'..ext line of scroll ing text Display Previous I ine of scroll ing text (lisplay next half page of scrolling text Display previous half page of scro II i nQ text o i sp I ay next page of scro II i ng text Dlsolay previous page of scroll ing text Clear dialog area buffer, and screen (Refer to Appendix D for the default definitions macro numbers for al I the tablet keys.) A new scrol ling and key tablet overlay has been designed which labels the non-DON users, refer to Figure 1 and 2 for the new overlay. The dotted I ines indicate with the lower 1/2 inch of the overlay overlaprig the top 1/2 inch of the active area of the tablet. ta~let keys. For the ~Iacement of t~e positioning, Fer DON users, refer to figure 2. The new overlay fits directly above the existing den tablet overlay, with the ne~ overlay's bottom edge directly against the existing overlay's top edge, and the left. edges I ined up. o To use a tablet key, ~osition the pen or puck within the box BELOW the label ins and make a tablet pick. The appropriate T~K.6M V3,1 p.c.oO~ PAlZE 13A SRB r ~ d w ~~ ~i ~o Q.O (!) Q.~ J: ~~ 0 :to w ~:: .J ~~ 0- O.J B .... ~ LL ~~Ia. ~ « Q. IrJl: ~!!! 0> >~ UJO !t~ ~ 38N 9~ II i. PAf.£ '138 TE.K.EH V3.1 f4.WDE. SR.B r FIGURE 1 FUNCTION BUTTON AREA (NOT ACTIVE) ~----~-~-~~--~------------~ ACTIVE TABLET AREA .-._.. _........... _... _- T~J!.E.M VZ.I PCODE S.~B PAGrE' 13~ r FIGURE 2 No Space Be tween _=- ...... , Overlays uter-AI ded ~ Manufacturin leEM TABLET OVERLAYS ~r ~,-., JW .J 10 <: J- W > tU <: C: G o Page 14 TEKEM V3.1 Microcode SRB function ~i I I be executed. Tablet keys cannot be used with the shift, Control, or Shift/Control keys from the keyboard. However, the same effect may be achieved through the use of a multi-button tablet puck, or by using "color" functions which emulate a multi-Dutton puck. If a multi-button tablet puck is used in conjunction with a tab let key, e a c h but ton / tab let key c 0 fil bin a t ion may bed e fin e d to be a separate key. So, with a theoretical four button puck (not yet avai lable), 92 (4x23) separate keys can be defined. With the three button puck now avai lable, you can effectively use 69 different keys. Color functions may be used to emulate the multi-button puck. (See "New Feature: Color Functions".) The default definition for all the "higher" tablet keys is NOP. 4.1.8 Operation Complete Functions and Operation Reject Special The new special functions Operation Complete ("]") and Operation Reject ("[") have been introduced into TEKEM V3.1 for the convenience of users who use the lEW in conjuction with Control Data's ICEM program. Any keyboard or tablet key may be defined as an Op Complete or an Op Reject. The default key for Op Co~plete is button 1 (middle button) of the wulti-button tablet puck, when the tablet puck is in the GIN area of the tablet (i.e., not in the tablet key area). The default key for Op ~eject is button 2 (right button) of the multi-button tat let puck, when the tablet puck is in the GIN area of the tablet. Pressing the key ass~ciated with an Op Complete or Op Reject results in the appropriate d~ta being sent to the host. Some host computers e~rect an Cp Complete or Op Reject to be terminated by a Newl ine. A new Setup comrr,and, AUTONEWLINE (YES/~O) has been introduced. AUTONEWLINE YES causes a Newl ine to terminate all OP Complete's and Op Reject's, while AUTONEWLINE NO suppresses Newline after Op Complete's and Op Reject's. (See New Feature: AUTONEWLI~E setup command.) \ ......... _. ' T~KEM o V3.1 4.1.9 Page 15 SRE ~icrocode AUTONEWlINE Setup command AUTONEWlINE is a ne~ setup command which affects special functions Operation Complete and Operation Reject, which are also new. (Please read about these new special functions.) Setting AUTONE~lINE to YES results in al I Op Complete's and Op Reject's being terreinated with a Newline; AUTONEWlINE NO causes sUDPression of the Newline terminator. If you wish to use the Op Complete and Op Reject special functions, you mush first set the setup parameter AUTONEWlINE. If your host co~puter is a CY~ER 120 or 793/794 workstation AUTONEWlINE should be NQ. If your host computer is a CYEER 170/1EO AUTONEWlINE should be YES. To set AUTONEWLIf\E, perforIT' the following steps prior to using TEKEM V3.1 the first time: 1. 2. 3. 4. 5. o Boot TEKE~ V3.1 Enter Setup Mode. Enter "AUTONFWlINE NO" or "AUTONEWLINE YES" as the case may be. EntE'r "SAVECONFIG". Exit SETUP mode. Now, whenever you boot TEKE~ V3.1 correctly for your system. 4.1.10 Key ~acro AUTONEWlINE wi I I be set Modifications. This section describes tMe modifications to the Tektronix DEFINE-MACRO and EXPAND-MACRO commands and their counterparts on the CDC lEW. In general, macros work the same way on the lEW as on a Tektronix terminal. ~hat is different is the commands that create and execute them. In the CDC version beth DEFI~E-MACRO and EXPAND-MACRC have been enhanced. 4.1.10.1 Additional Macro Expansion Values The range of permissible values for macro expansion has teen extended. The Tektronix commands restrict the values of bytes in an expanded macro to the ASCII set, decimal 0 through 127. CDC's TEKEM allows the full ASCII set, plus values in the range -64 to -1. (he wi II call macros in this range "Special key codes") These 64 additional values execute the local functions normally performed by the speciil (non-ASCII) keys on the keyboard, such as PAN, 100M, PAGEUP and SETUP. See Appendix C for a I ist of the special key codes E their corres~onding special functions. Though these codes were developed for internal use, you may use them through the DEFI~E-MACRO command, to assign the function of the special keys to any ASCII key of desired. Appendix A describes each of the special functions. o ---._-,--,_... __ ..._ - - - _.._........,-- -....:.......--- ,TEKfM V?l ~icrocode Page 16 SR8 4.1.10.2 Mappin~ of Keyboaro C,:, ../ As a result of this additional macro expansion feature, the user Olay "re-Iayout" the entire keyboard, if desired, using DEFINE ~ACRO commands. For example, to redefine the Normal key as the Previous View key, one would define macro number -60 to be -19, since -60 is the macro nurrber for the ~ormal key, and -19 is the special ~ey cede associated with the Previous View special function (see Appendices B and C). 4.1.10.3 Expanded Macro Hanoling In general, macros work the same wayan the lEW as on a Tektronix terminal. There are, however differences in the macro definitions and a general expansion of the cap a b i I tie s for ha" d lin g rna c r 0 s • The m0 s t not ice a b I e difference is ,that the macros in the range -176 to -18 are completely different between the two terminals. AI I other macro ranges are identical. A comparison of the macro codes for a II keys between the lEW and the Tektronix terminal is shown in A~pendix B. 8ecause of limitations imposed by the keyboard, and because of the layout used in previous versions of TEKE~, certain control character keys may not be used to transmit their corresponding keycodes to the host. Any key fro~ the keyboard which executes a local function ~hose code does not start with RS can not be simultaneously be used to send its code to the host. Specifically, the keycodes AH, AK, AW, AX, AY, AZ, and A (where 'A' means 'CONTROL') now execute local functions when TEKE~ V3.1 reads them from the keybo~rd. Control keys K and _ always execute their corresponding local function. If it is necessary to send a AK or A to the host, a macro rray be defineo which generates the appropriate value. Control keys Hand h-Z (cursor speed and movement) only execute exclusively local functions when the thumbwheel crosshairs, or a zoom or pan box is being displayed. At al I oter times, these keys' codes are sent to the host whenever ther corresponding local function is executed. As a side effect of this, if some other key is defined to produce a crosshair movement or speed local keycode it to wi II send the appropriate control key to the host when crosshairs are not displayed. c TEKFM V3.1 Microcode SRB o 4.1.11 Pa ge 17 Color Functions Coler functions are special functions which enable you to emulate a four-button tablet puck using a three-button puck or a pen. Invoking a color function forces the next tablet pick's button press to be a particular button number: Red: forces Green:forces Blue: forces Gold: forces next next next next tablet pick's button press to tablet pick's button press to tablet ~ick's button press to tablet pick's button press to be be be be button buttcn button button O. 1. 2. 3. None of the keytoard or tablet keys are defined in the default definitions to execute color functions. In order to use a color function, a DEFINE MACRO containing the cofor function's special key code must be issued. Then, whenever the m2cro is expanded, the color function wi I I be executed. 4.1.12 Dithering An additional type of hardcopy dithering for the Tek 46q2 hardcopier is now avai lable. It may be selected by setting the HCDITHER Setup mode parameter to MANY. ~ith the Seiko h2rdcopier, there is no difference between HCDITHER set to YES or MANY. 4.1.13 Terminal Mode at Poot A new Setup parameter, BOOTMODE, specifies the terminal's mode after booting the system. The mode may be either TEKEM or PASSTHf::U. o - - - - - - - - - _....... -.... __... _ - - - - - - ·TEKEM v3.1 ~icrocode 4.1.14 Page 18 SR8 Summary of New Setup ~ode Parameters Several new Setup mode para~eters have been introduced in TEKEM V3.1. They are as follows: HCTYPE SEIKO/TEK.4692 type of hardcory device being used HCDITt-'ER YES/NO/MANY dithering method PASSThRU S~'ALL CY6ER/ LARGE CYBER terminal conf ig. to use when passthru mode. TEKEM/PASSTHRU mode BGOTMODE syste~ in to enter after is booted AUTONEWLINE YES/NO include/excluoe a carriage return when sending an Operation Complete or an Operation Reject to host DALINES 24/30 maximum number lines visible dialog area OA BU FF DACHAPS 4.1.15 24 to 16384 80/132 minimum line sin buffer of in of number a log area d i maximum number of characters per lin e of dialog New Setup Mode 'Commands Two new Setup mode commands have been added, STATUS GENERAL and STATUS CO~MUNICATIONS. These new commands permit viewing of subsets of Setup mode par2m~ters. The STATUS commard sti II works as before, displaying both general and communicatipns parameters. To view only the General terminal parameters, enter "STATUS GENERAL" in Setup ~ode. To view only the Communications parameters, enter "STATUS COMMU~ICATIONS" in Setup mode. These can be abbreviated to "STAT GEN" and "STAT COM It • c; TEKEM V3.1 ~icrocode 4.2 SRE Page 19 Fixed Features An additional ~mphasis of this release is to provide corrective code to users of the CDC 790-20. The items below I ist some of the major functions and features that ~ere either missing or deficient in previous releases of TEKEM. Not a I I fixed features are listed. Refer to the later section descri~ing outstanding bugs for a I ist of al I reported problerr,s that are still "ot fixed in this release. 4.2.1 Passthru Mode Passthru in small Cyber mode now works. AI I CYBER 120 apotications are now supported, including SED, CEO, and In order to use SLATE. the lEW as a 120 terminal, do the following: 1. 2. 3. Set the Setup parameter PASSTHRU MODE to Sr.ALL CVBER. (Only done first tim€.) Issue the following terminal characterist ics command from AOS/VS: char/605x/off/nas Enter Passthru mode. To return to using the lEW as step s: 1• 2• a workstation, Exit Passthru mode. Issue the following command from AOS/VS: char/crt4/on/nas terminal reverse your characteristics 4.2.2 Entity Dragging Entity dragging now works without restriction. However, it i s i n a d vis a b let 0 d rag v e·r y I a r g e n u rr, be r s 0 fen tit i e s, sin c e drag processing time goes up ~ith the number of entities. 4.2.3 Change of Origin in DON CMange of origin of text or dimensions in DON now works correctly. using an lEW 4.2.4 Set GIN Area Command (esc IV) The Set GIN Area command is now fully functional, including multiple and overla~ping tablet GIN areas, and GIN area mapping to thp GIN window, current window, or other specified window. o Page 20 TEKEM V3.1 Microcode SRB 4.2.5 Set Report EO~ Frequency Command (esc 1M) The Set Report EOM Frequency command now works properly the EOM. frequency is set to "less frequent". wh~n 4.2.6 4q53 Tablet Report 4953 Tablet Reports now contain the proper header character. 4.2.7 GIN Stroke keporting The key char-reports in GIN stroke reports are now correct. 4.2.8 xy Reports in Coordinate Mode 1 In Coordinate Mode 1, the x and y values for xy reports were previously reduced to modulo 4096. This has been corrected. 4.2.q Di sabl ing of Tab let Previously, if the tablet was not enabled for GIN, tablet picks were still entered into the tablet data buffer. This has been correcteo. 4.2.10 Segment GIN cursor Deletion of a segment which is the GIN cursor now works in a noncurrent properly. Tracking of segment GIN cursor view now works properly. 4.2.11 GI~ CI window limits The GIN window was previously I imited to (-65535,-65535) to (65535,65535). This I imit has been removed. 4.2.12 View Clust~ring The windows of all views within a vie~ cluster are properly updated whenever one view in the cluster has any of the fol lowing operations performed: SET WINDOW command issued, VIEW, RESTORE, or OVE~VIE~ key pressed. All views within a view cluster are renewed whenever one view in the cluster has any of the fol lowing operations performed: RENEW VIEW command issued, PAGE command issued, or PAGF, VIEW, RESTORE, or OVERVIEW key pressed. 4.2.13 Set Border Visibility Corr.mand (esc RE) Issuing the Set Border Visibi lity command with a parameter of 2, which toggles the visibility, previously gave an error message and did not toggle the border visibi I ity; this has been corrected. C,I TEKEM V3.1 Microcode SRB Pa ge 21 4.2.14 Border Display with Next View key u Borders are now the Next View key. 4.2.15 GI~ ~Iinked correctly when changing views with Bypass r.ode GIN Bypass mode now works. 4.2.16 Bypass Cancel ~ode Bypass cancel mode now works. C) o - .-. __ ._.. _--_ - - - _ ... ...... _--_._--_._ .. -- . -.. - ....._- TEKEM V3.1 r.icrocode SRB 5.0 Pa ge 22 INSTALLATION ON THE. CDC 790-20" Normal installation of TEKE~ microcode requires no more than insertion of the diskette and a boot oper2tion. Because of changes made to improve performance and correct problems two changes to the basic configurat)on arameters in the f9G-=20 must be made at the time of installation of this diske e. These changes are a one-time change. Once the changes are performed on the 790-20 no further action is required to operate with TEKEM V3.1 on a continuing basis. 5.1 Installation of Tablet overlay (Tablet functions) For non-DON users, refer to Figure 1 and 2 for the placement of the overlay. The dotted lines indicate the positioninQ, with the lower 1/2 inch of the ove r I ay over lapp i ng the top 1/2 inch of the active area of the tablet. For DON users, refer to figure 2. 1 The new overlay fits directly above the existing DDN tablet overlay, with the new overlay's bottom edge directly against the existing overlay's top edge, and tre left edges I inec up. 502 Labeling of Puck Buttons It fTlay be useful for users of TEKEM to label the buttons of the three button puck. This may be done by I iftin9 the clear button covers up, and inserting a piece of paper which signifies the button purpose. See figure 3. 5.3 How to order a three button puck. If the user does not own a three button puck, it may be obta ir.ed at the followi n9 distr ibuters 1. 2. 3. Radio Shack (Tandy Express service) Entre Micro Age Stores Please ask for the "Kurta 3 button puck". /",,--..., .-~ f"" ) u 0 I "'------/ irl l' m ~ , rF - ~ur e 31 j To Remove Key Cap Ins e r t s ma I I Pr y Ca p and f f ~ - ~ [j 0 p J71 Sc r e wd r i v e r 0 < 11\ a i\J /t 113 /// // 1/ / ,/ .I ,I / / // Lable B I u e'p Op La bel Gr e e n Op JJ This Button a s we I I a s Re j e c t D Th i s Bu t t 0 tI a s we I I a s Co mp let e a ~ ~ fTJ ~ La bel Th i s Red pas wei I The norma I buttona L Bu t ton a s· Pi ck N » TEKEM V3.1 u ~icrocode 6.0 Page 23 SRB DOCUr.ENTATIO~ ADDITIO~S AND CHANGES The following notes are corrections and additions to the "cce 790 ICEM Ergonomic Workstation - Tektronix Emulation" manual, publ ication number (.2950166. Also, these notes are to be us~d 1~ CtHlD9~~. __ AQQIIIQ~ __ ~Q_IEKE~_Y~~Q_QQ'Ym~Qla!lQD_Agg111Qn~_~ng It is recommended that the pages that follow be copied and inserted into your manual so that future references to the manual contain ~p to date information. 6.1 Determining Setup Parameters. (p2-2) Change Paragraph From: When the terminal is in Setup mode, terminal and communications status can be determined by typing STA folow~d by a carriage return. This will display the TEKEM parameters on the alpha terminal as follows: TO: When the terminal is in Setup mode, General and Communications status can be determined by typing "STA" followed by carr iage return. To determine the General Status only, type "STA Gil follcwed by carriage return. To determine the Communications Status only type uSTA (" fol lowed by carriage return. By typing "STA" followed by cariage return, TEKEM parameters wi I I be displayed on the alpha ter~inal as follows: 6.2 Setur Parameters (p2-3) Replace the "TERMINAL STATUS" table and the "Changing Setup Paramters" sections with the following Jjage. The "Saving Setup Parameters" section remains the same. o TEKEM V3.1 Microcode SR8 Page 24 (Replacement page for Manual ~2950166 page 2-3. TEKE~ V3.1) TERMINAL STATUS GENERAL * * * * ECHO LOCKKYBD DABUFF DACHARS DALINES DAE~ABLE I GNORED'E L LFCR CRLF SAVECONFIG SCROLLING SNOOPY TABLETECHO HCDITHER HCINVERSE HCTYPE ERRORLEVEL YES NO 240 80 30 YES NO NO NO NO YES NO NO YES NO SEIKO 2 COMMUNICATIONS * * * * BAUD RATE AUTONEWLINE STOPBITS PARITY PROMPTSTRING PROMPTMODE CUEUESIZE FLAGGING BYPASSCANCEL LOCAL/REMOTE PASSTHRU MODE BOOT MODE C" 19200 NO 1 NONE '? ' NO 8100 IN/OUT (NL) REMOTE SMALL CyaER TEKEM MODE New parameters this release. Changing Setup Parameters (Note: The first paragraph remains the sa~e. Delete replace the second paragraph with the next section.) and ( " ..,,/1 TEKFM V3.1 Microcode SRB c=) 6.3 Page 25 New Setup Commands (p4-1) (Add the 4-1.) fol lowing descriptions of new Setup commands at page Table 4-1 (Changes). Change: HCDITHER TO: HCDITHEP. Set hardcory dither mode DACHARS DALINES HCTYPE AUTONEWLINE PASSTHRU "',ODE ~-- ....... (~ BOOT MODE (YES,~O) Setup Mode Commands Minimum ~urTiber of Lines stored in Dialog buffer. (24->16000) hid tI'"l of Dialog Area (80,132) Visitde Dialog Area Size {Screen Size} (24,30) Hardcopy Type (Seiko, Tek 4692) (Yes,No) MOde to enter when in Passthru mode. (SMALL CYBER, LARGE CYBER) Terminal r.Ode to boot. (TEKEM MODE, PASSTHRU MODE). c=) - .... -... _•.._._--_._----_. __ ._._--- ... _----.-_._ .... Co~mands Set hardco~y dither ~ode (YES,NQ,MANY), MANY ;s only applicable to Tek 4692 Hardcopy operation. Table 4-1 (Additions). DA BU FF Setup Mode TEKEM V3.1 Microcode SRB Page 26 Misc. Changes 6.4 (Please make the fol lowing changes by marking up your manual original. The changes described are not significant enough to require complete page replacement.) Configuration Parameter F6 in Step 6 (pA-3) 6.4.1 In ster 6 of the alpha set up sequence sho~n on oage A-3 box for F6 ~ sho~ u4625". Change it to show 1t4C25". the F 6 : OPR OF : 4C25 : ,--------, , (The display for F6 should be changed to leok like this.) I c' Page 27 TEKEM V3.1 Microcode SR8 o 7.0 KNOWN PROBLEMS AND WORK-AROUNDS This section describes problems and work-arouncs that are known to be in TEKEM V3.1 product that is being reteased at this time. The purpose of this section is to inform the user about potential problems and what, if any, workarounds are avai table to allow productive USE' of appl ication software with the 790-20 workstation. A second reason for this list is to inform the user what problems are known and need not be reported. These problems will receivE' corrective attention in future releases of TEKEM. Memory Allocation Rplating to Scrol I fng. 7.1 Currently, the memory allocation/deallocation operations have a bug when large blocks of memory are obtained. (i.e. larger than 32K bytes) Norma Ily thi s I arge of a block is .D~:!~r. QQ!aln~Q. This is only a problem when a large scrol I ing buffer is desired, analor ~hen the OUEUE SIZE (setup parameter) is changed to a value larger than 32K bytes. If the user desires a scrolling buffer with the following attributes DABUF 300 DACHARS 132 This will result in a scrolling butfer of approximately 300*132 bytes, or 39,600 bytes. Which is larger than 32k bytes. Thus it appears that the scrol I ing buffer may be set larger than 32k bytes at system boot time, but do so at your own risk. As for the OU~UE SIZE, the user must always to keep this parameter tellow 32K. 7.3 setup Outstanding Bug List The following is a tabular I ist of outstanding bugs, their severity rating, and a one-line description of the problem. ***** ***** the OUTSTA~DING lug report text is to be merged at this point o -- - -... __ ._ ......_ .. _.-_ _..... - .... .. " - - - - "'---" --------------_. ........ ----_. - - - - - ***** ***** Outstanding bug list TEKEM V3.1 CUTSTA~DING o Page 1 PRGELEMS SORTED BY PROLUCT,TYPE,CLASS,SECTION TYPE/CLASS SECTION PROBLEM PSR I PROMPT MODE IN PRCMPT MODE, PRO~PT STRI~G IS DISPLAYED E NC INPUT IS RETURNED. INITIAL CUKSOR OPERATION DOES NOT FUNCTION CORRECTLY. POSITION OF CURSO~ ~HEN ENABLED IS DIFFERE~T BEThEEN 4115 AND TEKEr. LINE A TO B DOES ~OT HAVE SAME PIXELS AS LIr~E B TO A. READBACK FORM~T IS DIFFERENT FROM DOCLIMENTATICN. ESC NP DOESN'T SET PARITY CORRECTLY TB ODES NOT ALLOW BLI~K BACKGROUNC COLOR. VIEh BOX IS LEFT ON THE SCREE~ AFTER PCLYGON ERASE. SET OVERVIEW hINDOW DOES NOT SET HOME PSR I PSR I Ie PS~ I LINE P S R ~'. P SR ~~ t. P PSR ,.,. 18 PSR ~1 VIEW 80X PSR r~ ~~INDCW PT~ r POLY-80RDE~ PSP. ~'I P SR ~~ POSITIO~. eRA G ~. ~B, NC PSR r PARITY PSR ~ FOLYGON PS R PTR fo4 ~S8 P T I< ~~ (E C ) SM STrIP P SR S P S~ S P SF' S PSR S C~LF PTR SOP SYS PT~ ~ 07/10/&6 SCPOLLIt\:G PTK S MALLDC POLYGON BORDER LEFT WHEN DRAGGING POL'tGON. COORDINATE MOOE CAN NOT CHANGE DURING PANEL DEFINITION. LARGE SEGME~T IS NOT DRAWN PROPERLY WHEN DRAG-ED, ••• ESC N~, ESC NC ARE IGNORED. PARITY SETTINGS ARE NOT SAVED PROPERLY POLYGCN PICKING DOES ~OT WORK WHEN DISPLAY PRICRITY IS IN USE. MSB (rOST SIG BIT) OF INPUT BYTE(FROM HOST) IS ST~I~PED. ESC SM (XCR,A~D,OR) MODES DON'T SEEM TO WORK ~ITH TEST CASE RE-DRAWING OF POLYGON CURSOR DOES NOT KEEP VP WITH TYPE-AHEAD BUFFER. EDL INDEX CARDS DISAPPEAR WITh 50 CHAR DISPLAY £ REVERSED SCROLLING ZOOMI~G WITH VERY srALL wINDO~S YIELDS STRAY VECTORS. SEE TEKTEST FILE. THE CRLF AND LFCR COMr.ANDS DO NOT wCRK WHEN DIALOG AREA IS ENAB/DIAB'ED CONTROL P IS ~OT SENT TO HOST E ALSO PUTS TEKEM IN PSUDO LOCAL. SCROLLING DOESN'T WORK WELL, hHEN VIKING IN 24 LPP, E 600TED IN 30. MALLOC FAILS hHEN OBTAINING BLOCK> 32K. ALSO OTHER INSTANCES. o ._".",' .., - " " . _ - - - - - - TEKEM V3.1 Microcode SRB Appendix Page 1 APPENDIX A - Special Function Descriptions o CURUP ~ove the thurrbwheels GIN cursor up (towards the top of the screen) one movement uni t. AI so, if the ZOOM box is up, this will increase the size of the ZOOM box. The movement unit may be made larger or sma I I e r us i n g the s p e cia I fun c t ion sSP E ED, S LOW, MEDIUM, or FAST. CURLF T Move the thumbwheels GIN cursor left (away from the alpha monitor) one movement unit. Also, if the ZOOM box is up, this wi I I decrease the size of the ZOOM box. The movement unit may be made larger or smaller using the special functions SPEED, SLOk, ~EDIUM, or FAST. CURRT Move the thumbwheels GIN ~ursor right (towards the alpha monitor) one movement unit. Also, it the ZOOM box is up, this wi II increase the size of the ZOOM box. Tre movement unit may be made larger or smaller using the special functions SPEED, SLOW, MECIUM, or FAST. CURDWN the thumbwheels GIN cursor down (towards the bottom on the screen) one movement unit. Also, if the ZOOM box is up, this wi I I decrease the size of the 'ZOOM box. The movement uni t may be made larger or smaller using the special functions SPEED, SLOW, MEDIUM, or FAST. CANCEL Reset to detault values various terminal parameters and modes: o Put terminal in ALPHA mode. o Disable al I GIN device-functions. o Unlock the keyboard. o Cancel BYPASS mode. o Remove the terminal from PROMPT mode. SPEED Toggle the current movement unit of the thumbwheels GIN cursor. Three different movement units are supported; slow, medium, ana fast. This operation changes the speed from slow to medium to fast and then back to slow again. FAST Set the t hum b whe e I s GIN m0 v e nl e n tun i t t 0 FA ST. MEDIU!'1 Set the thumbwheels GIN moveffient unit to MEDIUM. SLOW Set the thumbwheels GIN moveffient unit to ~ove o - - - - - - - - - _.. _.._..__.. - - - - - - - - - - SLO~. TEKtM V3.1 Microcode SRB Appendix Page 2 LOCAL This o~eration causes the terminal to transition to or from local mode. If in local mode already, this wi I I put the terrr;inal into remote mode. If in remote mode, the terminal wi II go to local mode. SETUP This operation causes the terminal to transition to or from setup mode. If in setup mode already, this wi I I exit setup mooe. If not in setup mode, this wi I I put the terminal into setup mode. HCOPY This operation initiates a hard copy on an attached hard copy device. Black and white areas of the screen are printed as is. HI"-V This operation initiates a hard copy on an attached hard copy device. Black areas on the screen are printed as white, and white areas on the screen are rrinted as black. This feature is not currently supported, but reserved for future implementation. HALPHA This operation produces a hardcopy of information on the alpha monitor. This feature is not currently supported, but reserved for future im~lementation. PAGE This operation initiates a RENEW-VIEW, repainting the screen. P ORDE R This oreration toggles the border visi~i I ity in the current view. If borders were not visible, they will be made visible. If they were visible, they beco~e invisible. NXTVIEl-J This operation selects the next higher view defined. It only one view is defined it is a null operation. PREVIEW This operation selects the next lower view defined. It only one view is defined it is a null operation. CLEAR This operation erases the dialog area, and clears any data in the dialog area scrolling buffer. DIALOG This operation toggles the dialog area location. If the dialog area was on the alpha monitor, it will move to the graphics display. If it was on the graphics display, it wi II move to the alpha monitor. TEKEM V3.1 Microcode SRB Appendix PAf\J This operation toggles the local pan function. The pan viewing function displays a box on the graphics device, with a crosshair in the center. The box may be moved around with the CURUP, CURLFT, CU~D~N, and CURRT operations. The selected view can be displayed ~ith the VIEW operation. OVRVW This operation erases the current view, then re-displays the vi~w using the partial overview window (as set by the SET-OV~RVIEW-WINDOW command). Any views clustered with the current view are also redisplayed using the current view's partial overview window. VIEW This operation erases the current view, then re-displays the view using the most recent window and viewport data. Any views clustered to the current view are also affected. RESTORE This operation erases the current view, then re-displays the view using the previous transformations stored in the circular restore-queue. Viewing transformations ana local viewing operations (PAN and ZOOM) are entered into a circular Queue each time that the VIEW operation is selected. Up to four sets of "old values" for the viewing transforwations can be stored. Any views clustered to the current view are also affected. ZOOM This operation toggles the local zoorr· function. The zoom viewing function displays a box on the graphics device, with smaller corner markers inside the larger full box. The box may be made smaller with the CURDWN or CURLFT operations. The CURUP or CURRT operations make the box larger. The selected view may be displayed with the VIE~ operation. NORMAL This operation restores the size and shape of the pan or zoom viewing display boxes. CREAK This operation causes a BREAK signal to be sent to the host on the host RS-232 communications line. PASTHRU This operation toggles the current state of the 'transparent'mode. If the terminal is in TEKEM mode, it wi II go to transparEnt mode; if in t ran spa r e n t n' 0 de, i t wi I I got 0 TEKE fI, mod e • Not currently implemented. PAGEUP This operation scrol Is the dialog area back one ful I page (either 24 or 30 lines) of text on the alpha display. o o ... --,------_.. "., Page 3 . ... _-----_ ... "". "'."._--,_.-..,... ' - - - TEKEM V3.1 ~icrocode SRF Appendix Page 4 PAGEOWN This operation scrol Is the dialog area forward one full page (either 24 or 30 I ines) of text on the alpha display. HPAGUP This operation scrolls the dialog area back one half page (eit~er 12 or 15 I ines) of text on the alpha display. HPAGDWN This operation scrolls the dialog area forward one half page (either 12 or 15 lines) of text on the alpha display. LINE l' P This operation scrolls the dialog area back one single I ine of text on the alpha display. LINEDWN This operation scrolls the oialog area forward one single I ine of text on the alpha display. TOP This operation scrolls the dialog area all the way back to the teQinning of the dialog buffer, and displays the first 24 or 30 lines of the buffer on the alpha display. BOTTOM This operation scrolls the dialog area all the way forward to the end of the dialog buffer, and displays the last 24 or 30 lines of the buffer on the alpha display. NOP This operation does nothing. When used with key ffiacros -100 to -103 (associated ~ith the tablet GI~ area buttons), a tablet "GIN report wi II be sent. Any other key macro defined to this function effectively disables the key. TZOOM This operat ion initiates the tablet controlled ZOOrTl feature. t crosshair appears on the screen, which is used to locate one corner of the zoom box. After that, a zoom box appears whose size is controlled by the tablet pen. It is only possible to zoom in on a view with this method. TUNZOOM Zoom out of the view by a fixed factor. The factor may be changed from the default value of 100i. with the Set Tablet Zooming Parameters (esc IZ) command. PREVZOO~ The previous Zoom Special function, labeled PREY ZOOM on the tablet overlay, changes the viewing window othe previous zoomed ~indow, if any. It is similar to the Restore key, except that no zoom or pan ox is displayed. GI~RED This operation forces the next tablet pick to assume button #0 was pressed. c TEKEM V3.1 Microcode SR8 Appendix C\ GINGRE~ This operation forces the next tablet pick to assume button #1 was pressed. GINBLUE This operation forces the next tablet pick to assume button #2 was pressed. Glf'.lGC'LD This operation forces the next tablet pick to assume button ~3 was pressed. oP CO~; Operation Complete. Sends a ")" or a tt) ". Inclusion or exclusion of the carriage return is con t r 0 I led by the Set u p par an. e t erA UTON EWLIN E • I c· o Page 5 C: ---~----.--~.- .- .. -_. ~-.- --._- .. - ..-. . .. ..." .. --------.. -." ,".. ", " , -- ---._------_ ..__.•.-. , .. ".. .. . ______.___ ... ____ ",. _________ ,.___ - _0-- . __________ .. Page TEKEM V3.1 t",icrocode SRB Appendix APPEN[iIX B C ) Macro Number 0 1 2 3 4 5 6 7 8 (-', .--~j TEK keyt·oard key ------ ---------------- 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 CNTL 2 CNTL A CNTL B CNTL C CNTL 0 CNTL E CNTL F CNTL G CNTL H CNTL I CNTL J CNTL K CNTL L CNTL ~ CNTL N CNTL 0 CNTL P CNTL Q CNTL R CNTL S CNTL T CNTL U CNTL V CNTL W CNTL X CNTL y CNTL Z CNTL [ CNTL CNTL ] CNTL A CNTL blank It - Macro Number Table lEW keyboaro key ---------------@ CNTL Cf'\TL A CNTL B C~TL or BACK SPACE or TAB or LINE FEED or RTN CNTL CNTL CNTL CNTL CNTL CNTL CNTL CNTL CNTL CNTL CNTL CNTL It # # 36 $ $ 37 38 39 40 41 42 43 44 I. I. E. E. ( ) *+ , ~. "'" + , 45 46 47 0 • / E F G or BACK SPACE I or TAB J or LINE FEED H K L M N 0 P CNTL Q CNTL R Cf\JTL S Cf'\TL T CNTL U CNTL V CNTL l-i CNTL X CNTL y CNTL Z CNTL [ or ESC CNTL CNTL ] Ct\TL A CNTL blank C~;TL or ESC C D / lEW keyboard character sequence (hex) -------------00 01 02 03 04 05 06 07 08 09 DA oe DC 00 OE OF 10 11 12 13 14 15 16 17 18 19 lA IB 1C 10 IE: IF 20 21 22 23 24 25 26 27 2ti 29 2A 26 2C 20 2E 2F 6 -------_._.- TEKE~ 0 CI V3.1 f'i:icrocode SRB Appendix 102 103 104 1C5 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 -1 -2 -3 -4 -5 -~ -7 -8 -9 -10 -11 -12 C) --- f f g 66 67 68 69 6A h i j k I m n k I m n 0 0 j 66 } } N N RUB OUT Fl F2 F3 F4 F5 F6 F7 Fe SHFT F1 SHFT F2 SHFT F3 SHFT F4 SHFT F5 SHFT Fb SHFT F7 SHFT FB DEL Fl F2 F3 F4 F5 F6 F7 F8 SHFT SHFT SHFT SHFT SHFT SHFT SHFT SHFT F1 F2 F3 F4 F5 F6 F7 F8 6C 60 bE 6F 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F lE,71 1E,72 IE, 7 3 lE,74 lE,75 lE,76 1E,77 lE,78 1E,6l lE,62 1E,63 lE,64 lE,65 lE,66 IE ,67 IE ,68 CNTL CNTL CNTL CNTL CNTL CNTL CNTL CNTL SHFT SHFT SHFT CNTL CNTL CNTL CNTl cr-.. TL CNTL Cf'.1TL CNTL SHFT SHFT ShFT F1 F2 F3 F4 F5 F6 F7 F8 CNTL Fl CNTL F2 CNTL F3 lE,3l 1E,32 IE, 3 3 lE,34 IE ,:; 5 1E,36 IE, 37 IE ,38 lE,21 lE,22 lE,23 p p Q q r r s t u v s t u w w x x y v z z { { Fl F2 F3 F4 F5 F6 F7 F8 CNTL Fl CNTL F2 CNTL F3 ,-_._- - . - Page 8 9 h y -_.-._-_._-_..... _._------ TEKEM V3.1 Micrccode SRp. Appendix -13 -14 -15 -16 -17 -18 -19 -20 -21 -22 -23 -24 -25 -26 -27 -28 -29 -30 -31 -32 -33 -34 -35 -36 -37 -38 -39 -40 -41 -42 -43 -44 -45 -46 -47 -48 -49 -50 -51 -52 -53 -54 -55 -56 -57 -58 -59 -to -61 -62 -63 -64 -65 -66 SHFT CNTL F4 SHFT CNTL F5 SHFT CNTL Fe S~FT CNTL F7 SHFT CNTL FB Z(lOM PAN NEXT VIEW VI E~: SHFT ZOOM SHFT PAN SHFT NEXT VIEW SHFT VI E~J CNTL ZOOM CNTL PAN CNTL NEXT VI E~;' CNTL VIEW SHFT CNTL zeor SHFT CNTL PAN SHFT CNTL NEXT VIEw SHFT (NTL VIEW SHFT RUB OUT CNTL RUE OUT SHFT CNTL RUB OUT SHFT ESC CNTL ESC SHFT CNTL ESC SHFT BACK SPACE CNTl BACK SP ACE SHFT LINE FEED LINE FEED SHFT CNTL LINE FEED SHFT TAe CNTL TAB C~~TL SHFT RTN CNTL RTN SHFT (NTL RTN SHFT SPACE CNTL SPACE SHFT CNTL SPACE Num Num 1 Num 2 Num 3 Num 4 Num 5 Num 6 Num 7 Num 8 Num 9 NUll! • Num , ° Page 9 SHFT CNTL F4 SHFT CNTl F5 SHFT CNTL Fb SHFT CNTL F7 SHFT CNTL F8 CANCEL SHFT CANCEL CNTL CANCEL S~FT CNTL CANC EL DIALOG S~FT DIALOG Cf\TL DIALOG SHFT CNTL DIALOG 'U P , SHFT 'UP' CNTL 'UP' SHFT CNTl 'UP' ESC SHFT ESC CNTL ESC SHFT (NTL ESC PAGE SHFT PAGE 'SUPER' SHFT 'SUPER' CNTL 'SUPER' SHFT CNTl 'SUPER' 'SUB' SHFT 'SUB' C~TL 'SUB' SHFT CNTL 'SUB' SCROLL UP SHFT SCROLL UP C~TL SCROLL UP S~FT CNTL SCROLL UP SCROLL DOWN SHFT SCROLL DOWr\ CNTL SCROLL DOWN SHFT CNTL SCROLL DOV:N CLEAR SI1FT CLEAR SETUP SHFT SETUP LOCAL SHFT LOCAL HARDCOPY BREAK NORt"AL SHFT NORMAL OVERVIEW SHFT OVERVIEW SHFT CNTL OVERVIEW RESTORE SHFi RESTORE lE,24 lE,25 lE,26 IE, 2 7 lE,28 lE,12,2C lE,12,20 lE,lZ,2E lE,1Z,2F IE ,12,28 lE,12,2<1 lE,lZ,2A 1E,12,2B 1E,12,24 IE , 12 ,25 1E:,12,26 lE,12,27 lE,12,20 lE,12,21 lE,12,22 lE,12,23 IE ,OZ lE,Ol IE,79 IE,69 lE,39 lE,29 lE,7A lE,6A IE,3A IE,2A IE: ,7B IE ,6B lE,3B IE,26 lE,7C lE,6C lE,3C lE,2C lE,4F IE,52 IE ,4E lE,5l OB OC lB BREAK lE,5C lE,58 IF lE,5D lE,59 1E,5E lE,5A (-'" \.., C (~"I '-...-,' - -- -----_.- _. __ ... - .. _.-_._._.--._--_ .... -67 -68 -69 0 -70 -71 -72 -73 -74 -75 -76 -77 -78 -79 -80 -81 -82 -83 -84 -85 -e.6 -87 -E8 0 0 -89 -90 -91 -92 -93 -94 -95 -96 -97 -98 -99 -100 -101 -102 -103 -104 -105 -106 -107 -108 -109 -110 -111 -112 -113 -114 -115 -116 -117 -118 -119 -120 Num Num ENT SHFT N urn SHFT Nurr. 1 SHFT Nurr 2 SHFT Num 3 SHFT Nurr. 4 SHFT Num 5 SHFT Num 6 SHFT Nurr. 7 SHFT Nurr: 8 SHFT Nurr 9 SHFT Num • SHFT ~!um , SHFT Num SHFT Nurn ENT CNTL Num CNTL Num 1 CNTL Num 2 CNTL Num 3 CNTL Nurn 4 CNTL Num 5 CNTL Num 6 C~~TL Nurr 7 CNTL Nurn 8 CNTL Num 9 CNTL Nun; • CNTL Num Ct\TL Num CNTL t\um ENT SHFT CNTL Num SHFT CNTL Num SHFT CNTL Num SHFT CNTL Num SHFT CNTL Num Sf-IFT CNTL Num SHFT CNTL Num SHFT CNTL Num SHFT CNTL Num SHFT CNTL Num SHFT CNTL ~um SHFT CNTL Num S~FT CNTL Num SHFT CNTL Num DIALOG SETUP LOCAL COpy PAGE BREAK" SHFT DIALOG SHFT SETUP SHF T LOCAL SHFT COpy BORDER SHFT BOJ\DER [ ° SHFT [ ZOOM SHFT ZOOM CNTL ZOOM SHFT CNTL ZeOM PI. N SHFT FAt\ CNTL PAN SHFT CNTL PAN VIEW SHFT VIEW CNTL VIEW SHFT CNTL VIEW NEXTVIEh SHF T ~~ EXT V1 t W C"TL t\EXTVIEW ° ] , 0 1 2 3 4 5 6 7 8 9 ,• ENT .- ..__ ._._-_. ~---.--- Page 10 TEKEM V3.1 Microcode SR8 Appendix . - SHFT ] CNTL TAB BACkTAB Ct\TL BACK TAD CURSOR UP CURSOR DOWN CURSOR LEFT CURSOR f'IGHT CURSOR SPEED RESERVED RESERVED RESERVED RESERVED TABL ET GIN AREA BUTTO~ TA 8L ET GIN AREA BUTTON TA8LET GIN AREA BUTTO,", TABLET GIN AREA BUTTON TABLET KEY C BUTTON #0 TABLET KEY 0 BUTTON #1 TABLET KEY 0 oUTTON #2 TABLET KEY C BUTTON #3 TABLET KEY 1 BUTTON #0 TABLET KEY 1 BUTTeN #1 TABLET KEY 1 BUTTON #2 TABLET KEY 1 BUTTON #3 TABLET KEY 2 BUTTON #0 TABLET KEY 2 BUTTON #1 TAELET KEY 2 BUTTON #2 TABLET KEY 2 BUTTON #3 TABLET KEY 3 BUTTON #0 TA8LET KEY 3 BuTTON #1 TABLET I - -Fr. =N.- - - ALLOWS FOR USER TO SET THE NUMBER OF FEET DESIRED TO BE THE BOUND AFTER WHICH INCH DIMENSIONS ARE DISPLAYED AS FEET. EXAMPLE: IF SET TO 2, 15" WILL BE DISPLAYED AS 15", BUT 25" WILL BE DISPLAYED AS 2"1". 108 F.16.1.14 ISOMETRIC DRAFTING REPLACES SECTION LINING CONTROL SECTION LINING MODALS ARE NOW SET WHEN YOU ENTER F.16.3. ISOMETRIC DRAFTING 1. DN - DISPLAY IN VIEW OF DEF ONLY - THIS ACTIVATES ISOrvtETRIC DRAFTING AND PLACES THE DIMENSIONS IN THE VIEW OF CREATION ONLY BY AUTOMATI CALLY SELECI1VELY VIEw BLANKING THESE ENTITIES IN ALL OTHER VIEWS 2. ON - DISPLAY IN ALL VIEWS - TIllS ACI1VATES ISOMETRIC DRAFfING AND WILL DISPLAY THE DRAFfING ENTITIES IN ALL VIEWS 3. OFF 109 (DEFAULT) ISOMETRIC DRAFTING • WHEN CREATING DRAFfING ENTITIES . WITH THIS TURNED ON, THE DRAFfING ENTITIES ARE CREATED IN THE SA~ MANNER AS ANY OTHER ENTITY IN 3-D SPACE AND THE FOLLOWING TIPS MAY HELP. ALWAYS BE AWARE OF THE CURRENT WORKING DEPTH AND WORK SPACE, AS THEY WILL DETERMINE THE ACTUAL PLANE OF CREATION. WHEN DETERMINING THE TYPE OF DIMENSIONING TO USE (I.E. HORIZONTAL VS. VERTICAL), IMAGINE LOOKING AT THE PART AS IF YOU WERE IN THE VIEW THE WORK SPACE IS SET TO. WITH THAT PERSPECTIVE, IS THE DESIRED DI~NSION VERTICALOR HORIZONTAL? ISOMETRICALLY CREATED DIMENSIONS CAN BE SELECfIVELY VIEW BLANKED IN THE SAME WAY AS ANY OTHER 3-D ENTITY. 110 16.2 DIMENSION - VERSION 1.6 INTRODUCES 3 NEW DIMENSIONING METHODS: CHAMFER, ARC LENGTH, AND RECfANGULAR COORDINATES. 9. CHAMFER - ALLOWS YOU TO INDICATE A LINE AND DIMENSION IT AS SHOWN IN THE FOLLOWING FIGURE: 'sae2 ANSI OWFER D I WENS I ~ 4S·X 1.0000 1.0000 X 45· CHAM 1973 ANSI ow.FER DIIENSI~ . NOTE: A LINE DOES NOT HAVE TO BE CREATED AS A CHAMFER TO DIMENSION IT AS A CHAMFER. THE CHAMFER WILL ALWAYS BE DIMENSIONED AS IF IT WERE 4S DEGREES (ANSI STANDARD). IT WILL TAKE THE LENGTH OF THE LINE BEING DIMENSIONED AND CALCULATE THE LEG LENGTH OF A 4S DEGREE CHAMFER. THAT LEG LENGTH IS THE CHAMFER DIMENSION GIVEN. C) 111 16.2 DI~NSJQN (CONT.) 10. ARC LENGTH - ALLOWS YOU TO INDICATE AN ARC AND DIMENSION IT AS SHOWN BELOW WITH THE LENGTH OF THE CIRCUMFERENCE OF THE ARC 11. RECfANGULAR COORDINATE - CAN CREATE VERTICAL AND HORIZONTAL DIMENSION WITH RESPECf TO A PRE-DEFINED ORIGIN. 1. DEFINE ORIGIN - MUST INDICATE A POINT FROM WHICH DIMENSIONS ARE MADE 2. HORIZONTAL 3. VERTICAL NOTE: ONCE THE ORIGIN IS DEFINED WITH F.2.11.1, IT NEED NOT BE DEFINED AGAIN IN THE CURRENT PART UNLESS YOU WANT TO CHANGE TIlE DIMENSION REFERENCE POINT. c' 112 r- -. tf) z -o + Ul ~ Z 1J.J - ::E o -$-- ~ - w ...... e{ z -a: o . o o u '-., cr < C/ 5 t!) z ....< ~ ~ - I 18 - . -$-- ~ , ... - u w a:: I U) t- ::l o ...:z:- N .-. CD 0 tD " J t 4IIIt - I ~~- ~ 0 r- r- - " - In --0 to -• -. () 113 ------- -------- · -· t!) + z z o (f) z w . - to N -$- to CD ... ~ - .o ....lJJ ,t!) z.:( -$- tU W to + ~ a: · 0 !' lO U1 o .. ........c (\ -...., ,,-,,/ 114 ! c.) F.16.3 SECTION LINING IS NOW BROKEN DOWN INTO 2 SUBMENUS 1. 2. MODALS DEFINITION SECfION LINING MODALS 1. MATERIAL TYPE 2. VISffiILITY 1. VIEW OF DEFINITION 2. ALL VIEWS 3. ALIGN:MENT 1. ON - CAN SELECT OTHER SECTION LINES TO MATCH THEIR SPACING ALIGNMENT'= N.,-MUST SET THE ALIGNMENT FACTOR FROM 0 TO 1.0. A 0 OR 1 SETI1NG GIVES FULL ALIGNMENT. A .S SETTING GIVES HALF ALIGNMENT. 2. OFF 115 , ,,, .. ,,. ''''''''''''''', .. , ' ' ' _ . ,,',. ,'-,,, ..' , - - - - - - - - - - - F.16.3 SECTION LINING (CONT.) DEFINITION SECTION LINING HAS BE ENHANCED TO MAKE THE PROCESS MUCH MORE USER FRIENDLY. • CAN USE NEW ENTITY SELECTION METHODS • CAN DISALLOW PRESELECfED CURVES • NOW HAS OPEN BOUNDARY CHECK • CAN NOW HA VB A SMALL OPENING IN THE BOUNDARY AND STILL GET SECTION LINING TO WORK 116 F.16.7 GEOMETRIC TOLERANCE HAS BEEN ENHANCED TO INCLUDE COMPOSITE GEOMETRIC TOLERANCES. TInS ENHANCEMENT DIVIDED THIS :MENU INTO 2 SUBMENUS. 1. 2. GEOMETRIC TOLERANCE - SIMILAR TO EARLIER VERSION COMPOSITE GEOMETRIC TOLERANCE EXAMPLE OF COMPOSITE GEOMETRIC TOLERANCE 117 ,r-' \ " F.16.13 MODIFY DRAFTING ENTITY HAS THE FOLLOWING ENHANCEMENTS: 6. MODIFY TEXT HAS 2 ADDmONAL CHOICES 4. ADD PREFIX (SUFFIX) TEXT 5. REMOVE PREFIX (SUFFIX) TEXT BOTH 4 AND 5 ARE SIMILAR TO THE AUTOMATIC CREATION OF PREFIX TEXT DESCRffiED IN SECTION 16.1.4, AND THE CHOICE OF EITHER WILL BRING UP THE FOLLOWING MENU: 1. 2. 3. 4. 5. 6. DIMffiTER SYMBOL RADIUS SYMBOL SPHERICAL DIAMETER SYMBOL SPHERICAL'RADIUS SYMBOL SQUARE SYMBOL . REPETITIVE FEATURES TEXT THE CHOICE OF ANY OF THESE WILL ADDIREMOVE THESE ENTITIES AS DESCRIBED IN SECTION 16.1.4 ADDED MENU CHOICE: 18. DIMENSION NOT TO SCALE - THIS MENU CHOICE ALLOWS YOU TO SELECT AN ENTITY AND PLACES A LINE UNDER THA'T ENTITY NOTE: LABELS ARE NOT SELECTABLE. 118 \ "- , " FEET AND INCHES 119 FEET AND INCHES GENERAL DESCRIPTION • FEETIINCHES UNIT OF MEASURE AT ENTRY • DATA ENTRY IN FTIIN. • DATADISPLAYINFTIIN. • DIMENSIONS WITH FfIIN. • FRACTION ROUNDING OF FTIIN. IN SYSTEM AND DRAFTING • CONTROL OF FOOT UNIT ON DISPLAY RESTRICTIONS • NOT IN GRAPL • UNIT CONVERSION NOT AVAll...ABLE • ONLY IN ANSI 73· AND 82 120 FEET AND INCHES INPUT OUTPUT 5' 2" 5'2" 5 FEET 2 INCHES 5 FEET 2 INCHES 5'0" 2" 5'2" 2" OR 2 2 INCHES . 2" 121 FEET AND INCHES FRACTIONS (}6.}.4.2) 2" 1/2 1'3/8 3'6"7/8 2.5 INCHES 1 FOOT .375 IN. 3 FEET 6.875 IN. 2"1/2 1'0"3/8 3'6"7/8 3 FEET 6.785 IN. 3'6.785" . DECIMAL 3'6.875" FOOT SYMBOL ON V ALlJE (16.1.4.7) . VAL >.. Ff 0 VAL >.. Ff 2 15" IS 1'-3" 15' IS 15" 122 c' FEET AND INCHES WHEN USING FRACTIONS WHEN IN FEET! INCHES, MENU F.16.1.4.2 WILL OFFER THE FOLLOWING CHOICES FOR ROUND-OFF IN DIMENSION TEXT: ROUNDING INCH INCH INCH INCH INCH 112 INCH 1 INCH 1 FOOT 1/64 1/32 1/16 1/8 1/4 o 123 - --_._---_. __._-_._---_._-",_ ..... _._._ ... - ---_. .... _--,.,-_ .. -......... --_.__ ... _--------_. __. _ . _ - - - ' MENU 17: NUMERICAL CoNTRoL THE AREAS OF THE NUMERICAL CONTROL SECTION FOR VERSION 1.60 ARE AS FOLLOWS: • DISPLAY AND EDIT • DRILLING • EASY GENERATION • -GENERATION PARAMETER GROUPING • • • • LATHE TURNING • • SURFACE PROFILING LATHE DRILLING MACROS SURFACE MILLING TOOL DEFINITION THE EXISTING FEATURES OF DRILLING, PROFILING, LATHE TURNING, AND LATHE DRILLING ARE EXTENSIVELY AFFECTED BY THE INTRODUCTION OF THE GENERATION PARAMETER GROUPING AND THE EASY GENERATION FEATURES. SINCE THE GPG AND EASY GEN ARE NEW, THE USAGE OF FEATURES THAT NOW INCORPORATE THEM REQUIRES TRAINING IN THE NEW FEATURES. 124 j " "'-.l THE MACRO FEATURE HAS BEEN TOTALLY REWRITTEN FOR THIS RELEASE. IT HAS EXPANDED CAPABILITY AND ENHANCED USER FUNCTIONALITY. IT DOES REMAIN A SUBSET OF GPL AND THE APT LANGUAGE. IN ORDER TO PROPERLY USE THIS PEATURE, IT IS NECESSARY TO VIEW THIS AS A NEW FEATURE. THE DISPLAY AND EDIT FEATURE HAS ALSO BEEN COMPLETELY REWRIITEN. THE TOOLPATH EXISTS NOW AS A TEXT FILE. IT CAN BE EDITED BY USING EITHER A MENU DRIVEN LThffiEDITORORBYACOMMANDDruVEN SCREEN EDITOR. THIS FEATURE ALSO ALLOWS TOOL SIMULATION AND MACRO EXPANSION. THE AREAS OF SURFACE MILLING AND PROFILING ARE AGAIN AREAS THAT HAVE BEEN COMPLETELY REWRIITEN. THE FEATURES HA VE ENTIRELY NEW INTERFACES. THE OTHER ITEMS PREVIOUSLY NOTED ARE NEW FEATURES AND THE TRAINING NECESSARY IS OFFERED IN THE NEW FEATURES CLASS. IT SHOULD BE UNDERSCORED THAT FOR PROPER USAGE OF THE N/C SECTION THE TRAINING COURSE SHOULD BE TAKEN. 125 ._ .. _--- _ .... - ---------- ----- ",' Control Data Corporation ICEM IGES TRANSLATOR Version 2.23 June 1988 User Release Bulletin Please make this document available to all ICEM IGES users. Control Data Corporation gives the user permission to reproduce this document. Disclaimer ICEM IGES is intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Note Please contad the appropriate hottlne If you have questions concerning this release. 800 . '345-9903 USA and Caa:ia 612 851-4131 International SMD131974 - ..- ... _ .......... _- _ _- .........._....... .... _.. , - ---- Control Data Corporation ICEM IGES Translator Version 2.23 User Release Bulletin 1.0 June 1988 Introduction ICEM IGES Version 2.23 supports the tolerance stacking notation that has been introduced with ICEM DON 1.65. 2.0 NOTES AND CAUTIONS 1. IGES V2.23 should be used in conjunction with ICEM DON V1.SS. It may be used in conjunction with ICEM DON V1.60, V1.62, V1.63 or V1.64. 2. Not all drafting symbols supported by ICEM DON are supported by the IGES V2.0 standard. Control Data's IGES V2.23 substitutes a blank in place of the symbols not translated. Drafting symbols unique to other vendors may not be translated to ICEM DON. 3. IGES Drawings are translated into ICEM View Layouts. It may be necessary to adjust the' view borders and view scales using DON when restoring the resulting IPARTD files. 4. The IGES Preprocessor may fail if the IPARTO file does not have DON type 16 entitles as its first two entitles. When encountering such a file, the IGES Preprocessor issues warning message 202: EXPECTING ENTITY TYPE 16, TRANSLATION MAY FAIL If such an IPARTO file causes the IGES Preprocessor to fail, restore the IPARTD file into DON and write It back out again. Use the new IPARTD file. 5. The Tape-ta-Disk (TADI) and Disk-to-Tape (DITA) utilities use the NOS FCOPY command. FCOPY is limited to reading and writing tapes with blocking factors less then 49. (The Recommended Practices Manual for IGES, written by the IGES Standard Committee, suggests a blocking factor of 10 .) 6. When restoring IPARTO flies generated by the IGES Postprocessor into DON, It is Important that the DON part be in the same units as the IPARTD file. =- ,~.... CONTROL DATA CORPORATION ICBM DDN Version 1.65.0.00 SOFTWARE RELEASE BULLETIN NOS 2.5.3 Operating System Level: Level 688 June, 1988 Date: DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Control" Data Corporation gives the user permission to reproduce this document. *** NOTE *** Please call the following HOTLINE numbers if you have any problems or questions: 1-800-345-9903 -~-612-851-4131 U.S. and Canada International- Additional information pertinent to this release may be found in SOLVER Installation Bulletins for ICBM products. *** URGENT *** Please make this document available to all ICEM DDN users. SMD131838 1 June, 1988 Table of Contents 1.0 INTRODUCTION 1-1 2.0 VERSION 1.65 FEATURE REVIEW 2.1 SELECTION TOLERANCE IN CHAIN SELECT . • . • 2.2 TOLERANCE SPECIAL CHARACTER SYMBOLS FOR ANSI . . • . •. 2.2.1 CREATING TOLERANCES VIA MENU 16.13.4.1 • • 2.2.2 UPDATING DIMENSION TEXT CONTAINING TOLERANCES 2.2.3 MODIFYING TEXT WITH TOLERANCE SPECIAL CHARACTER SYMBOLS • • . • • • . . • . • • 2.2.4 NOTES AND CAUTIONS. . . • 2.3 POINT TO POINT GPG ENHANCEMENT. . 2.4 TAPE3 RECOVERY UTILITY. . . • • • 2-1 2-1 2-2 2-3 2-4 3.0 PSR CORRECTIONS INCLUDED IN THIS SSU . 3-1 4.0 4.1 4.2 4.3 4-1 4-1 4-1 4-2 COMPATIBILITIES . . . . . VERSION NUMBERS OF RELATED ICEM APPLICATIONS. ICEM DDN VERSION 2.0 . . ••• ICBM DDN UNDER IWOS 5.0 NOTES AND CAUTIONS •. ••••..•. . • • • • 5.1 VERSION 1.65 VIEW CLIPPING • • • • • • . 5.2 PART INTEGRITY REPORT .••• 5.3 PART INTEGRITY PSR FIXES • . • • • 5.4 POST PROCESSOR WORD LIBRARY UPDATE •. 5.4.1 HOW PART UPDATE HANDLES TOOLPATH PPLIB WORDS BEFORE 1 .65 . . . . . . . . . . . . . . . . . . . . . . . 5.4.2 HOW PART UPDATE HANDLES TOOLPATH PPLIB WORDS IN 1.65 5.5 SURFACE MILLING CHANGES 5.6 3 AXIS FLANGE FEATURE REMOVED . • • . . • • . 5.7 USING MSTRINGS AFTER SUSPEND 5.8 DECREASE OF TAPE3 . • • • • • . • • • . 6.0 POST-1.62 ICBM MANUAL CHANGES 6.1 CONTINUED TOOLPATH STATEMENTS IN CL FILE GENERATION 6.2 GPL MSTRNG MANUAL CHANGE • • • . • ••• 6.3 GPL SPLLNE =HANliAL CHANGE • • • • • • . • . ". • • • 6.4 GPL PREFIX MANUAL CHANGE • • . • • • • • • • . • • 6.S CURVE MESH SURFACE MANUAL CHANGE • . • . • • • . • . 6.6 NEW ICBM DDN CONTROL CARD PARAMETERS 'RO' AND 'LF' • 6.7 CLFILE TRANSLATION • • • • . • . • • . • • • • 6.7.1 ALTERNATE INPUT FILE FORMAT • . • • • • • • • 6.7.2 NEUTRAL FORMAT DEFINITION •••• 6.7.2.1 Definitions • • • . . . • 6.7.2.2 File header. • . . . ..• 6.7.2.3 CL data record •• 6.7.2.4 End of file record • . • • . • • • 6. 7 • 2.5 Examp 1e • • • • . . . • . . . • • • 6.7.3 CL FILE STRUCTURE • . . . 2-5 2-6 2-6 2-8 5-1 5-1 5-2 5-2 5-2 5-3 5-3 5-4 5-5 5-5 5-5 6-1 6-1 6-2 6-2 6-2 6-3 6-3 6-5 6-8 6-9 6-10 6-11 6-11 6-11 6-12 6-12 2 June, 1988 6.8 IPARTD SAVE . . . . . . . . 6.9 IPARTD MODALS . . . . . . . 6.10 TAPE9 PLOT FILE OPTIMIZER 6.10.1 OPTIM RESTRICTIONS 6.10.2 OPTIM ERROR MESSAGES . . . . 6.11 INCREMENTAL POINTS ON ELLIPSES AND HYPERBOLAS 6.12 MSTRNG STATEMENT IN GPL . . . . . . . . . . . 6.13 CHAIN SELECT TOLERANCE • . . . . . . . . 6.14 TOLERANCE SPECIAL CHARACTER SYMBOLS FOR ANSI 6-15 6-15 6-16 6-18 6-18 6-21 6-21 6-21 6-23 7.0 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7-1 7-1 7-1 7-1 7-2 7-2 7-2 7-3 NOS TAPE3 RESTORE UTILITY INTRODUCTION . . . . . . APPLICABLE DOCUMENTS . . PROGRAM DESCRIPTION INSTALLATION OF CONVT3 . CONVT3 PROGRAM EXECUTION. NOTES AND CAUTIONS . . CONVT3 PROGRAM OUTPUT r 1-1 ICEM DON Vl.65 Software Release Bulletin June, 1988 1.0 INTRODUCTION 1.0 INTRODUCTION This SOFTWARE RELEASE BULLETIN (SRB) is designed to inform site analysts and ICEM DON users of PSR/RSE corrections and enhancements which are contained in the ICEM DON Vl.65 Software System Update (SSU). In addition, this document contains relevant comments and descriptions of changes which should be' made to the ICEM DON Vl.62 Reference Manuals. Any information not included in this SRB but pertaining to the SSU is documented on a SOLVER Installation Bulletin. This SSU includes all corrections from the Vl.64 Batched Critical Updates (BCUs) and supersedes all previous NOS ICEM Vl.6 releases. 2-1 ICEM DDN Vl.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.0 VERSION 1.65 FEATURE REVIEW 2.1 SELECTION TOLERANCE IN CHAIN SELECT A new modal in menus F.l.ll.2.4, E.7.10, and F.!.!!.! enables the user to modify the tolerance used by chain select to identify contiguous entities. These tolerances are used for all entity selections made via chain select. Chain Selection Modals in Entity Selection Control have been increased to four items (F.l.l1.2.4). --- CHAIN SELECT MODALS 1.CHAIN SELECT MODE 2.CHAIN SELECTN METHOD 3.DISALLOW PRESELECTED CURVES 4.CHAIN SELECT TOLERANCE Modals in ,Entity (E.7.10). E/D SCREEN OFF 0.001 Selection have been increased to ten items --- MODALS 1.REPEAT INCLUDE/EXCLUDE 2.CONSTRAINT SET DURATION 3.SELECTION MODIFICATION 4.SINGLE SELECT FROM GROUP 5. CHAI1t SELECT MODE 6.CHAIN SELECT METHOD 7.DISALLOW PRESELECTED CURVES 8.ATTENTION INDICATORS 9.CONSTRAINT SET LEVEL 10.CHAIN SELECT TOLERANCE ON ONCE OFF OFF E/D .. SCREEN OFF ON CUR 0.001 Display Modal Status in Entity Selection increased to eleven items (F.l.ll.l). Control has been 2-2 ICEM DDN V1.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.1 SELECTION TOLERANCE IN CHAIN SELECT SELECTION SYSTEM MODALS 1.CHAIN SELECT MODE 2.CHAIN SELECT METHOD 3.DISALLOW PRESELECTED CURVES 4.SINGLE SELECT FROM GROUP 5.ATTENTION POINT OF LINES 6.REPEAT INCLUDE/EXCLUDE 7.CONSTRAINT SET DURATION 8.SELECTION MODIFICATION 9.SELECTION METHOD 10.HIGHLIGHTING METHOD 11.CHAIN SELECT TOLERANCE E/D SCRN OFF OFF MID ON ONCE OFF SCRN ATT IN 0.001 When the modal is selected, its current value is displayed. The default value is 0.001 inch (0.0254 millimeter). Valid input is between 0.001 inch (0.0254 mm) and 0.000000001 inch (0.000000025 mm). If invalid input is entered, an error message is output and the system reprompts you for a valid chain select tolerance. 2.2 TOLERANCE SPECIAL CHARACTER SYMBOLS FOR ANSI Two Special Character Symbols have been added to allow greater flexibility when creating tolerances in ANSI dimensions. The additional Special Characters are used to control when tolerances should be displayed as stacked. See Table A, Special Character Symbols, for the list of all predefined characters and associated symbols. 2-3 ICEM DDN V1.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.2 TOLERANCE SPECIAL CHARACTER SYMBOLS FOR ANSI TABLE A SPECIAL CHARACTER SYMBOLS Character Entry \D \L \0 \R \S \B \C .\ Symbol Name Depth Left Bracket Diameter Right Bracket Square Counterbore Countersink Degree Plus/minus Plus for tolerancing Minus for tolerancing Prefix character All other characters \@ \+ \\\ \c When using ICEM DDN to place dimensions in a working drawing it is common to have tolerances and other combinations of plus or minus signs in drafting text display as stacked. At times stacking should not be done, however. The following shows an example of each. Linear dimension with tolerance and Radius dimension with thread callout <---- +.010 5.000 -.000 ----> <---- .500-20UNC-3B 2.2.1 CREATING TOLERANCES VIA MENU 16.13.4.1 the When creating tolerances that are not equal using tolerance menu, the Special Character Symbol for the tolerancing plus or tolerancing minus sign will be added into the dimension text. (Equal and opposite tolerances will continue to use the plus/minus sign \@ representation). The 2-4 ICEM DDN Vl.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.2.1 CREATING TOLERANCES VIA MENU 16.13.4.1 presence of the tolerancing Special Character Symbols signify that the text would be displayed as stacked, like the linear dimension shown on the previous page. ICEM DDN will always create tolerances from the tolerance menu so that the text will display as stacked. Text to be displayed nonstacked on a single line may be added with the modify text menu (16.13.6). 2.2.2 UPDATING DIMENSION TEXT CONTAINING TOLERANCES All dimension drafting entities containing tolerances will be updated to use the Tolerance Special Character Symbols. ICEM DDN will examine the text associated with the dimension to determine if tolerances are present. If tolerances are encountered, the plus or minus signs located within the text will be replaced with the Special Character 'Symbols for'a plus or minus tolerance. On NOS, the character count for the string will be incremented by two for each pair of tolerances, because the Special Character Symbols require a two character representation. When searching for tolerances, ICEM DDN will only allow character string representations signifying tolerances that could have been created automatically. Whether they were actually created by the tolerance menu or by the modify text menu is irrelevant since they are processed identically. The following criteria are used when searching for tolerance strings: 1. Notes and Labels are excluded. 2. Only numerics are allowed (i.e. 0123456789)-alphabetic or other characters are not allowed, with a few exceptions outlined below. 3. Spaces within tolerances are not allowed. The only exceptions are metric zero tolerances which display as "0" and fractional formats which use spaces in the numerator or denominator portion of the text. A space is used as a delimiter between the second tolerance and any suffix or trailing text. 4. Special character symbols are not allowed. 2-5 ICEM DDN V1.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.2.2 UPDATING DIMENSION TEXT CONTAINING TOLERANCES 5. Degree symbols, foot marks, and inch marks are allowed. 6. Each line of text will be processed to locate tolerances. In the past, tolerancing was restricted to only the first line of text. 7. Only one pair of tolerances is allowed per line within the dimension. Only the first pair of tolerances encountered on a line will be updated to use the Tolerance Special Character Symbols. The criteria mentioned above are only applicable within the substrings of dimension text that could be interpreted as tolerances. It is possible that portions of dimension text may get incorrectly updated, either because ICEM DDN thought a tolerance was found or the text substrings could not be validated as tolerances. These occurrences will be rare and are easily reversed using the modify text menu. 2.2.3 MODIFYING TEXT WITH TOLERANCE SPECIAL CHARACTER SYMBOLS The Tolerance Special Character Symbols may be used within any drafting entity just like any of the previous Special Character Symbols. When placed within dimensions only, the Tolerance Special Character Symbol signals that a tolerance follows and that the text shou-ld-Te displayed as stacked.· When u~ed wi thin other drafting entities, the current Prefix Character will display with the Tolerance Special Character Symbol to allow these symbols to be recognized and removed easily. Stacked tolerances must be paired within a line. If only one Tolerance Special Character Symbol is present within a line, no text will display stacked. In addition, the current Prefix Character will display with the Tolerance Special Character Symbol. This will enable any mismatched Tolerance Special Character Symbols entered by hand to be recognized and corrected easily. 2-6 ICEM DDN V1.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.2.3 MODIFYING TEXT WITH TOLERANCE SPECIAL CHARACTER SYMBOLS Text may be displayed as stacked within any line of text. dimension Only one pair of tolerances is allowed on a single line of dimension text. Extra occurrences of Tolerance Special Character Symbols will display with the current Prefix Character so that the text may be corrected. When tolerances are ,used along with suffix or other trailing text, a space must be used as a delimeter between the second tolerance and the suffix or trailing text. When the unprefixed plus or minus sign is used, the text will be displayed as it was entered, with no stacking or adding of the current Prefix Character. 2.2.4 NOTES AND CAUTIONS It is recommended that the Prefix Character be changed from the default reverse slash (\) under the following circumstances: 1. If dimensioning is being done with fractions, the reverse slash is used in the fraction text representation, causing problems interpreting the dimension text. 2. GPL uses the reverse slash to signal the beginning of a new line. Because of this conflict, the Special Character Symbols will be processed incorrectly during GPL programs. The Prefix -Character may be changed in menu SET PREFIX. 16.1.1.5 SPECIAL 2.3 POINT TO POINT GPG ENHANCEMENT A new statement has been created for the point to point generation parameter group. The new statement "SAPPRT" replaces the statement "SRTRCT". Previously the "SRTRCT" statement offered no control over the first and last retract plane moves. The "SAPPRT" statement has the same funtionality ,. 2-7 ICEM DDN V1.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.3 POINT TO POINT GPG ENHANCEMENT of the "SRTRCT" statement plus control over the first and last retract plane moves. To more completely describe the tool motion offered by the "SAPPRT" statement the menu that is used to set "SAPPRT" options has been renamed. The menu entitled RETRACTION BETWEEN POINTS that appears in the point to point modify GPG menu has been renamed APPROACH/RETRACT. Selection options of the APPROACH/RETRACT menu remain the same as the RETRACTION BETWEEN POINTS menu: 1. 2. 3. 4. NONE CLEARANCE RETRACT PLANE PROMPT The following question will appear when NONE or CLEARANCE is selected from the APPROACH/RETRACT menu to indicate if the first and last retract moves are to be included in the toolpath: MOVE TO THE RETRACT PLANE BEFORE THE FIRST POINT AND AFTER THE LAST POINT ? The format of the "SAPPRT" statement is very similar to the old "SRTRCT" statement. The only difference is a YES or NO appearing after the minor word NONE or CLEARANCE. The possible settings of the "SAPPRT" statement are as follows: SAPPRT/NONE,YES SAPPRT/CLEAR,YES SAPPRT/RETRCT SAPPRT/NONE,NO SAPPRT/CLEAR,NO SAPPRT/PROMPT The YES and~O values appearing after NONE and CLEAR control the first and last retract moves. YES indicates the first and last move are wanted in the toolpath, and NO indicates they are to be omitted from the toolpath. To maintain compatabiltiy with existing GPGs the old "SRTRCT" statement will still be readable from a file. The settings of the statement will be converted to a functionally equivalent form of the new "SAPPRT" statement whenever the old statment is read. 2-8 ICEM DON V1.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.4 TAPE3 RECOVERY UTILITY ---------------------------------------------~-------- -------------- 2.4 TAPE3 RECOVERY UTILITY A TAPE3 restore utility is provided to assist in the recovery of parts damaged by system failure or other catastrophic events. Please see Section 7.0 for a more detailed description of this utility. --- - -- -.- - ------------_._. --- ...----- 3-1 ICEM DDN V1.65 Software Release Bulletin June, 1988 3.0 PSR CORRECTIONS INCLUDED IN THIS SSU 3.0 PSR CORRECTIONS INCLUDED IN THIS SSU This section contains a cumulative list of problems resolved in V1.65. The full text descriptions can be obtained through SOLVER. PRIORITY CODE: C U S M= CRITICAL URGENT SERIOUS MINOR PSRS CORRECTED IN DDN Vl.65 PSR II PRI AD2B229 AD2B246 AD2B257 AD2B260 AD2B274 AD22470 AD22547 AD22706 AD22764 AD22789 AD23036 AD23351 AD23384 AD23470 AD23503 AD23520 AD23562 AD23568 AD23577 AD23578 AD23588 AD2A775 AD2B099 AD2BI07 AD2B289 C C C C C C C C C C C C C C C C C C C C C U U U U DESCRIPTION CLFILE GENERATION DOESN'T OUTPUT ARCSLP IN APT4 CLFILES SURFACE MILLING ABORTS WITH "TABLES FULL" MESSAGE PART INTEGRITY SOMETIMES REMOVES ENTITIES WHICH ARE DISPLAYED CORRECTLY PART ON TAPE3 DID NOT CONVERT TO NOS/VE VIEW BOUNDARY TOPS MAY BE UNCONDITIONALLY RESET (LOWERED) TRASHED TAPE3 WON'T RETRIEVE EXISTING PARTS OR CREATE NEW ONES FILLET DOESN'T WORK BETWEEN AN ARC AND A 2-DEGREE LINE FAN POINTS AND INTERSECTION POINTS ON AN ELLIPSE ARE INCORRECT CORRUPT TAPE3 CAUSED BY THE NOS DIRECT ACCESS FILE LIMITS HORIZ LEADER LINE ON DATUM FEATURE SYMBOLS BECOMES "SLANTED" BY 1.60 PART FILING LEAVES VACANT SPACE PATTERN UPDATE FROM 1.62 TO 1.63 DOESN'T WORK UNA:B:tE TO XFER HOST PART SHARING FILES FROM NOS TO IWOS 2.1 DDN 1.63 SECOND +/- SIGN WILL BE STACKED ON THE FIRST LINE - WRONG TOLERANCE STACKING PROBLEMS IN Vl.64, CORRUPTS DATA ENTITIES ARE MISSING FROM A DRAWING AFTER CONVERSION TO NOS/VE NC POINT/POINT PLACES GOTO RETRACT AT START & END OF TOOLPATH CANNOT RENEW PART TWICE IN THE NOS-NOS/VE MIGRATION UTILITIES SOME FILES FAIL MIGRATION IN PARTA (15.3.7) FILLET SURFACE IS STILL BROKEN - WILL NOT GENERATE FULL SURF. ICEH DATA MIGRATION UTILITY V2.0.0 FAILS AFTER PROCESSING AN IPARTD INTERSECTION POINT BETWEEN DRAFT CURVE AND LINE IS INCORRECT UNABLE TO RESTORE IPARTD PARTS WITH 4 DIGIT SHEET NUMBERS PLANE THROUGH PT PERP TO TWO PLANES IS NOT WORKING IDENTIFY ATTRIBUTE ONLY WORKS IN VIEW OF DEFINITION OF ENTITY 3-2 ICEM DDN V1.65 Software Release Bulletin June, 1988 3.0 PSR CORRECTIONS INCLUDED IN THIS SSU AD22368 AD22411 AD22765 AD22766 AD22974 AD23088 AD23130 AD23301 AD23306 AD23354 AD23355 AD23383 AD23417 AD23432 AD23438 AD23471 AD23472 AD23486 AD23516 AD23542 AD23550 AD23591 AD2A728 AD22995 AD22999 AD23213 AD23262 AD23339 AD23405 AD23462 AD23468 AD23504 AD23505 AD23510 AD23554 AD2A698 AD2A96 0 AD23367 AD23488 U U U U U U U U U U U U U U U U U U U U u U S S S S S S S S S S S S S M M M M (11.8)MODIFY ANGLES GIVES UNPREDICTABLE RESULTS NOTE PARALLEL TO ARC NOT FUNCTIONING CORRECTLY WITH USER DEFINED CHAR TEXT IN FRONT AND BACK VIEWS OF 3D PATTERN IS DISPLAYED AT SAME TIME PARALLEL DIMENSIgNS MOYE WHEN MODIFIED Fs16s2s3 ¢ . i6.2.11 RECTANGULAR COORDINATES DO NOT WORK WHEN AUTO TAIL LOC - OFF NOT MEETING ANSI-1982 STANDARD/DEC.PL ONMM SURFACE SYMBOLS DESIRE MODAL TO SET SYSTEM TOLERANCE TO 0 DASH CREATES A NEW TOLERANCE IF IT APPEARS BEFORE A +- TOLERANCE SECTION LINING CANNOT BE MODIFIED ON DATUM TARGETS WHEN CONTINUING AFTER SUSPEND, MSTRING DOES NOT WORK UPDATE OLD PARTS FROM Vl.50 THRU Vl.62 ROTATE 3-D PART (SURFACES INCLUDED) CAUSED PROBLEMS TABLES FULL ERROR MESSAGE CAUSED BY EXCESSIVE DORMANT ENTITIES ICEM DDN N/C POINT TO POINT TOOLPATH GENERATION ASSUMPTION THAT THE FIRST LINE OF A DIMENSION WILL CONTAIN A TOLERANCE PRE 1.64 LAYOUTS WILL NOT DISPLAY TOP .EDGE OF DDN DATA RADIAL/DIAMETER DIMENSION STACKING OF KEY-TN T~XT OPTIM DOESN'T OUTPUT CORREtI oOiPdt FOR DDNUTIL TO PROCESS PART NAME AND SHEET NO ON PART INTEGRITY REPORT GROUP ENTITIES WITH ATTRIBUTES ASSIGNED ARE DELETED BY PART RENEW ON NOS AND AOS/BAD ERROR MESSAGES - TEXT DELTA FROM TEXT F.12.l1 CREATES CORRUPT ENTITIES THAT HAD ATTRIBUTES ATTACHED TO THEM USERS MAY INADVERTANTLY DEFINE PATTERN LIB FILES AS GLOBAL PART FILES UNABLE TO CREATE PATTERN (16.2.11.3) VERTICAL RECT. COORD. DlMEN. FAIL UNLESS AUTO TAIL IS ON SUSPEND CAUSES MSTRING FILE TO BECOME INACCESSABLE FOR RESUMED SESSION ICEM DDN 1.62 + TEK 4111 TERMINAL NOS TAPE3 FILE SIZE SOMETIMES GROWS VERY LARGE EVEN FOR SMALL DRAWINGS MODIFICATION OF FILLET ANGLE CAUSES INTEGRITY ERRORS AFTER THE SUSPEND FUNCTION THE TABLET SHOULD MAINTAIN THE DEFINE NAME MSTRINGS IN GPL PROGRAM DISALLOW MENU PICKS PROGRAMMED IN TFILE NOTE COMMAND PRODUCES A SPACE AND i. SIGN IN CHARACTER POSe 183/184 FILE FOR EVALUATION: PLOT FILE CREATION FLAKY, FILE/253 PRUS TO 6310 DDN 157 TOOLPATH NON-STANDARD POSTPROCESSOR WORDS LOST WHEN UPGRADING THROUGH A POINT,TANGENT TO A CURVE DOES NOT WORK WITH A SPLINE IN GPL ARC THROUGH 3 PTS CREATES LINE WITHOUT WARNING USER -PRINTOUT FOR 5.6. 7 IS INCONS·ISTENT WI~H ·REF MANUAL GPL COMPILER VERSION IS NOT CONSISTANT WITH DDN VERSION 1.63 ARC THRU 3 POINTS (F.ll.7) GENERATES LINE UNDER CERTAIN CONDITIONS 4-1 ICEM DDN V1.65 Software Release Bulletin June, 1988 4.0 COMPATIBILITIES 4.0 COMPATIBILITIES 4.1 VERSION NUMBERS OF RELATED ICEM APPLICATIONS The ICEM DDN 1.65 SSU 1S compatible Application Products under NOS 2: with the following DRAM VI.1 HASCO V1.1 ICEM BEND Vl.2 ICEM Engineering Data Library (EDL) V1.2.7 ICEM Facilities V1.41 ICEM Hydraulics VI.3 ICEM Kinematics VI.O ICEM Plastimould VI.l ICEM Solid Modeler Vl.13 IGES Translators V2.23 LINCAGES V1.2 MOLDFLOW V4.0 MOLDSTAR V3.0 4.2 ICEM DDN VERSION 2.0 ICEM DDN Version 1.65 enhancem_ent...L in the compatibilitY to ICEl1 MIGRATION UTILITY. refer to sections 5.2 contains some PSR fixes and additional Part Integrity area to ensure upward' V2.0 through the use of. the ICEM DATA For information on these corrections, and 5.3. You must use ICEM DATA MIGRATION UTILITY V2.0.2 and ICEM DDN V2.0.2 if you are uSlng the Tolerance Special Character Symbols for ANSI. 4-2 ICEM DDN Vl.65 Software Release Bulletin June, 1988 4.0 COMPATIBILITIES 4.3 ICEM DDN UNDER IWOS 4.3 ICEM DDN UNDER IWOS Users of both NOS- and IWOS-based DDN must use the following versions to ensure compatibility and translation between the two systems: IWOS: DDN 1.65 NOS: DDN 1.65 If you perform part sharing between NOS and IWOS systems, both NOS and IWOS systems must use the same version. A part can be "updated" from pre-1.65 to 1.65, but once the part is at 1.65, it cannot be read by a pre-1.65 version of ICEM DDN. The 1.65 part sharing utilities will be provided when ICEM DON 1.65 is released on IWOS. 5-1 ICEM DDN V1.65 Software Release Bulletin June, 1988 5.0 NOTES AND CAUTIONS 5.0 NOTES AND CAUTIONS 5.1 VERSION 1.65 VIEW CLIPPING This section only applies to pre-V1.64 parts that are into V1.65. brought With the screen size reduction that was done in V1.65, all views with the top boundary beyond the new screen boundary will appear clipped when first displayed in Vl.65. This is a necessary side effect of the V1.65 tablet/screen realignment. To correct the display, an auto max-min (Z.II) operation can be performed. (Note that for view layouts, the zoom mode should be "Entire Layout.") If you are using a different zoom scale, the scale can be easily adjusted by selecting ENTER SCALE (Z.8) and entering the following: tf'c.95 This expression tells DDN to multiply the current zoom scale by the amount of the screen size reduction. The sequence, Z(tab)8(tab)H*.95, can be programmed into an MSTRING and used with an input trace script to readjust saved zoom scales in a semi-automated manner. Please note that these readjustment operations are not required; they are desirable only if data typically displayed in the upper portion of the screen appears- .. clipped in the SSU. If you are using this SSU only for the purpose of migration to ICEM V2, and you are not planning to use the part in Vl.65, no benefit is gained by doing zoom scale readjustments prior ·to migration. Parts created in or updated to V1.64 (or any Vl.64 not be affected. BeU) will 5-2 ICEM DON V1.65 Software Release Bulletin June, 1988 5.0 NOTES AND CAUTIONS 5.2 PART INTEGRITY REPORT 5.2 PART INTEGRITY REPORT A column titled ACTION has been added to the part integrity report. The possible actions are RMV (for removed) or MOD (for modified). In previous versions corrupt entities were always removed during part renew. It is now possible to internally modify some corrupt entities rather than having to remove them. The part name and sheet number have been added to the banner of the part integrity report that is written to the file PRBRPLS when using the LF control card parameter. 5.3 PART INTEGRITY PSR FIXES Corrections to part integrity have been made in response to common problems encountered by customers ·in the migration process. These problems manifested themselves in various ways ranging from errors in ~he part integrity report to failure in migration. The following problems were corrected: o o o o o o o o duplicate sequence numbers zero-length line compatibility with V2.0.2 incorrect entity form numbers extra GRAPL entities invalid number of views incorrect COMMON values bad TAB2 and TAB3 data incorrect view updating 5.4 POST PROCESSOR WORD LIBRARY UPDATE New capability has been added to version 1.65 that will allow better updating of toolpaths regarding post processor words. Before 1.65 some of the post processor words would be replaced with asterisks in the updated toolpath. This new capability only affects toolpaths being updated from a pre-l.60 version of ICEMDDN to version 1.65. Toolpaths already created in, or updated to, a 1.6x version of ICEMDDN will not be affected. 5-3 ICEM DDN V1.65 Software Release Bulletin June, 1988 5.0 NOTES AND CAUTIONS 5.4 POST PROCESSOR WORD LIBRARY UPDATE When updating capability if: too1paths, you may benefit from this - You have TAPE3 files that contain parts with a mixture of versions and at least one version is older than 1.60. - You use more than one version of ICEM DDN and one of the versions is older than 1.60. The benefit will affect you should you decide to update the pre-1.60 part. 5.4.1 HOW PART UPDATE HANDLES TOOLPATH PPLIB WORDS BEFORE 1.65 ICEMDDN versions 1.60 and newer use a different post processor word library ( PPLIB ) than pre-1.60 versions. When a part is updated from a pre-l.60 version to a 1.60 or newer version, a new 1.6x PPLIB is created. The new PPLIB is just a copy of the old one. Both the old and new version of the PPLIB will now be on the UTF of the TAPE3. Part update will then use the new PPLIB to check all words in any toolpath being updated. All subsequent part updates will now use the new 1.6x PPLIB. Since PPLIBs are stored on the UTF all the parts of a TAPE3 share the same PPLIB. A problem can arise if the new PPLIB is modified. Part update assumes. the new 1.6x version of the PPLIB contains all the words that are in the pre-l.60 toolpaths. If a word is in an old toolpath, and not in the new PPLIB, part update will replace the word with asterisks in the updated toolpath. 5.4.2 HOW PART UPDATE HANDLES TOOLPATH PPLIB WORDS IN 1.65 In 1.65, part update uses the pre-1.60 version of the PPLIB if the part is pre-1.60. This means that part update does not assume that the 1.6x PPLIB contains all the words used by the old toolpaths. Any toolpath PPLIB word that is in the pre-1.60 PPLIB will be in the updated toolpath. If a PPLIB word is used by an old toolpath and not in the pre-1.60 PPLIB, the word will be replaced in the updated toolpath by the major word subclass code placed between asterisks. Once a toolpath exists in a 1.60 or newer version, the new capability is not used. It is only used when the version of ICEMDDN is 1.65 and the part is older than 1.60. 5-4 ICEM DON V1.65 Software Release Bulletin June, 1988 5.0 NOTES AND CAUTIONS 5.4.2 HOW PART UPDATE HANDLES TOOLPATH PPLIB WORDS IN 1.65 If you have toolpaths in parts older than 1.60 you should consider the following three points regarding part update. a) Part update in version 1.65 uses the pre-1.60 PPLIB to update pre-1.60 parts. The pre-1.60 PPLIB should contain all the PPLIB words used by the toolpaths that you plan to update. b) Updating all parts on a TAPE3 at the same time is the best way of migrating to a new version. This method guards against'PPLIB words of toolpaths appearing as asterisks in the updated toolpaths. c) Part update may be slower when updating pre-1.60 parts containing toolpaths to version 1.65. This is due to the increased overhead needed to use the older PPLIB. If you are updating a large number of toolpaths the additional time needed may be significant. Updating to any 1.6x version before using version 1.65 may be faster. 5.5 SURFACE MILLING CHANGES a) Closed boundary is no longer used in conjunction with a surface. When a surface is selected in response to the CONTROL SURFACE menu the CUTPATH type menu will not be displayed. Closed boundary represents a subset of tool control offered by the containment processing in surface milling. Since all the capability of the closed boundary exists in containment, this represents no loss in functionality. b) When a sarface is selected as the control. surface, the CUT DIRECTION menu will no longer appear. The" cut direction for a toolpath will be parallel with the U or V surface display paths. Whether the U or V paths are used is determined by indicating the start and end of the first cut with the graphics cursor. 5-5 ICEM DDN Vl.65 Software Release Bulletin June, 1988 5.0 NOTES ANO CAUTIONS 5.6 3 AXIS FLANGE FEATURE REMOVED 5.6 3 AXIS FLANGE FEATURE REMOVED The menu item 17.13 3 AXIS FLANGE CUTTING has been blanked due to removal of this feature. Other numerical control features in ICEM DON allow the same too1paths to be generated. 5.7 USING MSTRINGS AFTER SUSPEND Prior to version 1.65, re-entering a suspended ICEMDDN session would cause an error with tablet MSTRINGS. Attempting to execute a tablet square containing an MSTRING would result in an error message. The error message would notify the user that the MSTRING was not found. All defined MSTRINGS would In release 1.65 this problem has been become inoperable. corrected. 5.8 DECREASE OF TAPE3 Prior to version deleted entities space remained space is removed 1.65, if a working part became smaller due to and was subsequently filed, the extra unused on the TAPE3. In version 1.65, this extra whenever a part is reduced in size. 6-1 ICEM DON V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.0 POST-1.62 ICEM MANUAL CHANGES 6.1 CONTINUED TOOLPATH STATEMENTS IN CL FILE GENERATION Treatment 'of generation: a. continued toolpath statements in CL file The use of continuation and appended comment symbols The continuation symbol is a single $ sign. All text following the single dollar sign is considered comment. The following line is considered to be the continuation of the current toolpath statement. The appended text symbol is a double dollar sign $$. All text following the double dollar sign is considered comment. The statement is considered to end before the $$. Note that $ $ will be treated as a $ and not as a $$. The continuation and appended comment symbols are ignored in PARTNO, PPRINT, and INSERT statements. They are treated as part of the text of the statement. The use of continuation on motion statements, circle statements, multax statements is invalid and is ignored at CL file creation. b. New 'error messages The following new error me. sages concerning continued toolpath statements have been added for output in the CL Print file. ** ** ** ** ** ** ** ERROR ERROR ERROR ERROR ERROR ERROR ERROR ** ** ** ** *-Jc ** ** ILLEGAL CONTINUATION HINUS NOT FOLLOWED BY NUMBER EXPECTED COMMA, FOUND EXPECTED SLASH, FOUND UNEXPECTED END OF LINE EXPECTED WORD OR NUMBER, FOUND RECORD EXCEEDS MAXIMUM LENGTH " ... _ . - - - - - - - - _ . ........ . 6-2 ICEM DON V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.1 CONTINUED TOOLPATH STATEMENTS IN CL FILE GENERATION Excerpt of a sample CL Print file : 1 ICEM NC CLPRINT DON 1.64 PARTNO PPRINT THIS IS A TEST FOR CONTINUATION ($) AND APPENDED COMMENTS ($$). MODE $ THE NEXT TOKEN MUST BE A SLASH /AVOID,2. $$ END OF THIS PP STATEMENT MODE/AVOID $ A',' IS EXPECTED BUT NOT GIVEN 20. $$ ERRONEOUS CONTINUATION LINE ** ERROR. ** EXPECTED COMMA, FOUND 20. MODE,AAXIS,ADJUST $$ MAJOR WORD NOT FOLLOWED BY A / ** ERROR ** EXPECTED SLASH, FOUND , 6.2 GPL MSTRNG MANUAL CHANGE On page 8-4 of Revi~ion C of the immediately below the blocked format and its description. Replace NORTN with NORTRN in both description. ICEM GPL for NOS manual, NOTE is the MSTRNG statement the format and parameter 6.3 GPL SPLINE MANUAL CHANGE On page 13-7 of Revision C of the ICEM GPL for NOS manual, the third sentence in the second paragraph should read as follows: A minimum of three points and a maximum of 100 points can be specified. 6.4 GPL PREEIX MANUAL CHANGE On page 19-18 of Revision C of the ICEM GPL for NOS manual, the following text should be added at the end of the second paragraph: Although the reverse slant is the default prefix character, it is also the default "new line" character. Since the "new line" character takes precedence over the prefix character, the PREFIX statement must always be used to to change the default when a special symbol character is used. 6-3 ICEM DON Vl.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.5 CURVE MESH SURFACE MANUAL CHANGE 6.5 CURVE MESH SURFACE MANUAL CHANGE In the ICEM DDN ADVANCED DESIGN for NOS manual, replace the description under 15.3.6 Curve Mesh Surface with the following: In the INDICATE CURVES description: FIXED CURVES INDICATE CURVES Use the graphics cursor to select the fixed curves in an ordered manner. Fixed curves can be lines, arcs, conics, two-dimensional splines, composite curves, point sets, three-dimensional splines, or machining curves. Fixed curves cannot be selected end-to-end. Curves that lie end-to-end should be redefined as a composite curve before selection as a fixed curve. You must select a least 2, but not more than 30 fixed curves. VARIABLE CURVES INDICATE CURVES Use the graphics cursor to select the variable curves in an ordered manner. Variable curves,like fixed curves, can be of any type. Variable curves that lie end-to-end should be redefined as a composite curve before selection as a variable curve. You must select at lease 2, but not more than 30 variable curves under the following restriction: If you select "1. WITH TWIST VECTORS," the product of the number of fixed curves times the number of variable curves cannot exceed 203. =- If you select "2.' LINEARLY BLENDED," the product cannot exceed 50~; 6.6 NEW ICEM DDN CONTROL CARD PARAMETERS 'RO' AND 'LF' The following should be added to the list of optional ICEM DDN parameter settings found on pages 1-11 through 1-16 of the ICEM Design/Drafting Introduction and System Controls manual. 6-4 ICEM DON Vl.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.6 NEW ICEM DON CONTROL CARD PARAMETERS 'RO' AND 'LF' LF List To File. Writes to specific local files some of the lists displayed on the screen during an ICEM DON session. Listings will also be displayed on the screen unless the RO (Repaint Off) parameter is set. Default: Off. LF Sets List To File on. The following local files are produced when the respective list is generated from an ICEM DDN menu pick and LF is on. These files are always appended to, not overwritten. The list generated on the local file is always a complete list even if In' or '[' are entered at the continue listing prompt for screen display. A message indicates success or failure in writing to the local list file. ENTLS GPARTLS GUTFLS IPARTLS PARTLS PRBRPLS UTFLS RO Database part entity list: (f.6.6.1.3). Global parts file list: (f.6.l.1.3), (f.6.1.2.3). Global VTF file list: (f.6.5.4.3). Independent parts file list: (f.6.1.9), (f.6.1.10). Database file (TAPE3) parts list: (f.6.1.3), also by entering 'list' when creating a new, or retrieving an existing, TAPE3 part. Problem report list: (f.6.1.11.1)~ (f.6.1.11.2). Database VTF list: (f.6.5.1). Repaint Off. Disables redrawing of the display area and the generation of new entities in the display area. R entered as a function key will have no effect. Default: Off. RO Disables redrawing. Repaint Off is on. With Repaint Off enabled, specific li"sts which can also be written to local file. will not be generated to the display area. See the LF parameter to determine which lists· can be generated to local files. 6-5 ICEM DON V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.7 CLFILE TRANSLATION 6.7 CLFILE TRANSLATION ° This utility to translate the binary formatted CL data from the neutral format CL file and vice versa is included with the 1.65 release of ICEM DON, however, it is executed directly from the operating system level. Alternate input and output files can be used as the first two parameters on the execution statement. The alternate input file contains the same data as would be entered at an interactive session. The execution statement is as follows: ICEMCLT[,ALTIN] [tALTOUT] All data files needed should be local. Upon execution, an entry banner is displayed, showing the current version of the release. ICEM CL FILE TRANSLATOR COPYRIGHT CONTROL DATA CORPORATION 1987 REVISION 1.0 ICEM DON 1.64 (NOTE - The CL File Translator that was provided for ICEM DON 1.64 also works for ICEM DDN 1.65) The system then displays the SELECT TRANSLATOR FUNCTION menu with the GOrrent settings: ---SELECT TRANSLATOR FUNCTION 1.EXIT 2.GENERATE BINARY CL FILE 3.GENERATE NEUTRAL CL FILE 4.BINARY CL DATA FORMAT S.BINARY CL FILE NAME 6.NEUTRAL CL FILE NAME - APT IV - CLFILE - CLTAPE Enter: 1 To end the translator session. _ _ _ _ _ _ _ _ _ _ , __ " 0'-" ",,,,_, ,_,,, __ ,,. ____ _ 6-6 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.7 CLFILE TRANSLATION 2 To generate a binary CL file from a neutral format CL data file. If you choose option 2, the system displays: GENERATING (format) CL FILE (filename) FROM NEUTRAL CL FILE (filename) The CL file with the set file name is generated from the neutral CL data file with the set name. Any data already in the CL file is overwritten, even if generated in the same session. After a successful translation the following message appears: nn RECORDS WRITTEN TO THE CLFILE NO ERRORS ENCOUNTERED You are then returned to the main menu. After an unsuccessful translation, one of the following messages appears: a) b) c) NEUTRAL DATA FILE NOT RECOGNIZED CHECK FILE NAME OR FILE HEADER Action - Check if the correct file name is set. - Check if the file header was corrupted (see neutral file format definition). Result - No CL data written to CL file. NEUTRAL DATA FILE EMPTY OR NOT FOUND CHECK FILE NAME CHECK IF FILE IS LOCAL Acti1)n: - Check if the correct file name is set. - Check if the file is local Result - No CL data written to CL file. NEUTRAL DATA FILE IS CORRUPT AT OR AROUND RECORD record number CHECK FILE NAME OR EDIT ERRORS Action: - Check if the correct file name is set. - May occur after manual editing. 6-7 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.7 CLFILE TRANSLATION Result: 3 - Check CL file contents. To generate a neutral format CL data file from a binary CL file. If you choose option 3, the system displays: GENERATING NEUTRAL CL FILE (filename) FROM (format) CL FILE (filename) The neutral CL data file with the set name is generated from the CL fi~e with the set name. Any data already in the neutral data CL file is overwritten, even if generated in the same session. After a successful translation, the following message appears: nn RECORDS WRITTEN TO THE CLFILE NO ERRORS ENCOUNTERED You are then returned to the main menu. After an unsuccessful translation, one of the following messages appears: a) END OF CL FILE ENCOUNTERED BEFORE FINI CHECK CL FILE FOR FINI, CHECK CL FILE NAME, FORMAT AND CONTENT. Action: - Check if the CL file contains a FINI. - Check if the correct CL file name is set. - Check if the correct CL data format was chosen. - Check if the file is available and contains the expected data. Result: - Check neutral format CL data file. b) BINARY FILE READ ERROR CHECK FILE NAME, FORMAT AND CONTENT Action: - Check if the correct CL data format was chosen. - Check if the file contains data. Result: No neutral format CL data generated. 4 To be prompted for binary CL file format, the system displays the following menu. Enter 1 to return to the main menu 6-8 ICEM DON Vl.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.7 CLFILE TRANSLATION without changing the format. Enter 2 or 3 to select the desired format. Enter] or [ to return to the main menu without changing the format. ---SELECT BINARY CL FILE FaRHAT 1.EXIT 2.CDC APT III 3.CDC APT IV 5 To be prompted for the binary CL file name, the system displays: ENTER CL'DATA FILE NAME Enter a valid file name. ? Enter or [ if the current file name is to be retained. To be prompted for the neutral format CL data file name, the system displays: ENTER NEUTRAL FORMAT CL DATA FILE NAME ? Enter a valid file name, Enter ] or [ if the current file name is to be retained. If an invalid file name is entered, the system displays: FILE NAME NOT VALID In this case, the original file name is retained. 6.7.1 ALTERNATE INPUT FILE FORMAT The contents of an alternate input file must be identical to the data that would be entered in an interactive session at the main menu and performing the desired translation(s). Examples: 1. A neutral file CLFILE has to be translated to an APT IV binary CL File CLTAPE. In an interactive session, at the main menu, first a 2 is entered to generate the binary CL file. Then a 1 is entered to end the session 6-9 ICEM DON V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.7.1 ALTERNATE INPUT FILE FORMAT The alternate input file contains 2 lines: 2 1 2. An APT III binary CL file CLTAP1 has to be translated to a neutral format CL File CLNEUT. In an interactive session, at the main menu, the following is entered: 4, change the binary CL file format 3 , set the format to APT III 5 , change the binary CL file name CLTAP1 , the binary CL file name 6 , change the neutral CL file name CLNEUT , the neutral CL file name 2 , generate the neutral CL file 1 , exit. The alternate input file contains 8 lines: 4 3 5 CLTAP1 6 CLNEUT 2 1 6.7.2 NEUTRAL FORMAT DEFINITION An APT CL File consists of a set of data records. Each data record has an integer and real part. The integer part contains general information as the type, number and length of the record. The real data part contains the specific record data, in ~al, integer or character form. Y To be able to transfer this data from one operating system to another, it is written out in a neutral format on an ASCII file. The file is a sequential, formatted file, containing character data. The file contains variable length records, lines, with a maximum length of 130 characters. ". - - - _ .................. _.•.•..- 6-10 ICEM DON Vl.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.7.2.1 Definitions 6.7.2.1 Definitions data type specifier: single upper case character, indicating the data type of the data in the following field. Three data type specifiers are defined: I: F: A: preceeds an integer number data field preceeds an floating point number data field preceeds a character data field data field: fixed length character string containing the data corresponding to one logical CL data word. The length is data type dependent. data element: a data type specifier followed by the data field. integer data element: the data specifier I followed by a fixed length character representation of an integer number. e.g.: I 2000 represents the integer 2000 in a ten character integer data field. floating point data element: the data specifier F followed by a fixed length character representation of a floating number in exponential format: A one character sign field, a normalized fixed length mantissa without decimal point, 'a one character sign field and a fixed length exponent. . e.g.: F+5000000000000000+0001 represents the floating point number 5. with a 16 character mantissa and a 4 character exponent. character data element: the data specifier A followed by a fixed length character string. The length is always 6. e.g.: ACL OAT represents the string 'CL OAT' 6-11 ICEM DDN Vl.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.7.2.1 Definitions 6.7.2.2 File header The file header serves three purposes: 1. Define the end of record character. 2. Define the formats of the record data for integer, floating point and character data. 3. Prevent backspacing from the first record. The file header consists of 11 characters: position(s) definition/purpose 1 2 3-4 5 6 7-8 9 10 11 value end of record character integer format specifier integer field length floating format specifier exponent field length mantissa field length character format specifier character field length end of record character range any character except I,F,A I 10 F 4 16 A 6 I 1-10 F 1-5 1-20 A 6 must be the same as pos 1 The standard file header record for CL file in the ICEM DON environment: ;II0F416A6; 6.7.2.3 CL data record A CL data record is a concatenation of data elements spanning one or more 1 ines 0 f 130 charac t ers or 1 es.s and wi th the end of record character al the last character. A data element must be fully contained on one line. 6.7.2.4 End of file record The end of the file is indicated by a null record. A null record consists of a one character line, the end of line character. The standard end of file record for CL file in the ICEM DDN 6-12 ICEM DDN V1.6S Software Rel'ease Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.7.2.4 End of file record environment will then be: Note that the end of record character as the only data on a line does not necessarily constitute a null record. It could be the closing character of a record spanning one or more previous lines. 6.7.2.S Ex~mple APT representation: PARTNO EXAMPLE OF A NEUTRAL CL DATA FILE FROM/O,O,O GOTO/S,5,S FINI Neutral CL data file ( the line length is limited to 70 for the example ): ;I10F416A6; 1045A EXAMPALE OF AA NEUT 20001 91 11 ARAL CLADATA FAILE I 81 21 SOOOI 3A I 0 F+OOOOOOOOOOOOOOOO+OOOOF+OOOOOOOOOOOOOOOO+OOOOF+OOOOOO0000000000+0000; I 81 31 SOOOI SA I 0 F+5000000000000000+0001F+5000000000000000+0001F+SOOOOO0000000000+0001; I 31 41 140001 0; I 6.7.3 CL FI~ STRUCTURE The CL File consists of a sequential set of records. Each record is defined by a record class, a sub code and further instructions. The clqss groups similar types of records and is also called the record type. Listed below are the standard defined record formats: Wn = word n of the current record Wl record sequence number, refer to the physical formats for details 6-13 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.7.3 CL FILE STRUCTURE Record Type 2000: Post processor Commands WI = record sequence number W2 2000 W3 major word sub code (see postprocessor library, major word codes) W4 minor word codes and/or parameters (see postprocessor library, minor word codes) Specific Formats: PPRINT, PARTNO, 'INSERT: W4... up to 66 characters of text, blank filled on the right ARCSLP: W3 = 1029 (Default) W4 = START W5 = s,slope W6 ENDARC W7 e,slope, W8 RADIUS, W9 = r, WI0 = CCLW or CLW Record Type 3000: Surface Data Circle records are the only surface data carried through into a CL file: WI W2 = W3 W4 W5 W6 W7 W8 W9 WI0= Wl!= W12= W13= W14= W15= record sequence number 3000 2 Surface Use Indicator (Drive Surface) 1 Surface Condition Indicator (TO) 4 Surface Type Indicator (CIRCLE) 9 Number of words in the canonical form Surface name (Blank) " 0 Surface name subscript xc yc Coordinates of the circle center zc i j Circle plane normal k r Circle radius Record Type 5000: Directions, Points and Parameters WI = W2 = W3 W4 W5 W6 W7 W8 = W9 WI0= record sequence number 5000 = 4 GODLTA 3, , FROM Point or Vector name (Blank) Name subscript 0 xv xp yp yv zp zv i i (id. ) j (Mul tax only) J 5 GO TO xp (1) yp (1) zp (1) ip (1) jp (1) = 6 Continuation xp (n+1) yp (n+1) zp (n+1) ip(n+1) jp (n+l) (id. ) .._----_.. ----- ~. (id. ) 6-14 ICEM DDN Vl.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.7.3 CL FILE STRUCTURE Wll= k ... (Additional point coordinate sets for W3 W5 +n W6 +n W7 +n W8 +n W9 +n WI0+n kp-(n+ 1) kp (1) k k 5 or 6 only) xp(n) yp(n) zp (n) ip (n) jp (n) kp (n) (id. ) xp (2n) yp (2n) zp (2n) ip (2n) jp (2n) kp (2n) (id. ) A maximum numbe"r of 240 reals is written out in a GOTO or Continuation record. Record Type 6000: ARELEM Flags, Specifications, and Parameters WI W2 W3 record sequence number 6000 4 INTOL 5 OUTTOL W5 = t tolerance Record Type 9000: ARELEM WI W2 W3 W5 Parameters record sequence number 9000 2 MULTAX 0 OFF 1 ON And for an ISO standard CL file: WI record sequence number W2 = 9000 UNITS W3 = 9 W4 171 liM 172 CM 173 INCH =174 FT W5 n scaling factor or null Record Type 14000: Termination WI W2 W3 record sequence number 14000, FINI 0 6-15 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.8 IPARTD SAVE 6.8 IPARTD SAVE Following the Independent Save information on page 2-21 of the ICEM Design/Drafting Data Management manual, insert: "A maximum of 90 parts may be saved on a single IPARTD file. If you attempt to save more than 90 parts, the system will issue an error message and will not save the part onto the IPARTD file." 6.9 IPARTD MODALS In order to provide increased flexibility in the IPARTD feature, menu 6.1.12 IPARTD MODALS has been added. This menu item currently contains one new modal, the COMBINING VIEWS modal. The following documentation on IPARTD MODALS should be inserted after page 2-25 of the ICEM Design/Drafting Data Management manual: 6.1.12 IPARTD MODALS With ICEM DDN V1.65, there is a modal available for use in restoring IPARTD files. Additional modals may be added if necessary. The current modal setting is displayed to the right of the modal. ---IPARTD MODALS 1.C0MB1NING VIEWS current modal ~etting Enter: 1 ] or [ To change the COMBINING VIEWS modal. To return to the PART MANAGEMENT menu. 6-16 ICEM DDN Vl.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.9 IPARTD MODALS If you select I.COMBINING VIEWS, the following menu will be displayed: ---COMBINING VIEWS l.COMBINE VIEWS WHEN RESTORING 2.DO NOT COMBINE VIEWS WHEN RESTORING Enter: 1 To combine views with identical view matrices when res'toring parts from IPARTD. 2 To not combine views with identical view matrices when restoring. This is the system default. ] To return to the PART MANAGEMENT menu. [ To return to the IPARTD MODALS menu. If you choose to combine views, an entity displayed in any of the combined views will be displayed in the resultant view. The view names of the eliminated views will be unavailable after they have been combined. Most users will not want their views combined. View combining was motivated by a very old IGES problem which has long since been resolved. 6.10 TAPE9 PLOT FILE OPTIMIZER With some plotters, especially pen plotters, it is desirable to optimize the graphics data on the plot file before plotting it on the d~ice. The Plot Optimizer sorts ..thegraphics data and removes duplicate, collinear, and zero-length lines, thus reducing pen motion and increasing plotter throughput. A number of parameters are available for controlling the level of ·optimization. To execute command: the Plot File Optimizer, enter the following OPTIM [, paraml] [, param2] [, param3] , ••. [, paramN] where 6-17 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.10 TAPE9 PLOT FILE OPTIMIZER I Input plot file. Default input plot file name is TAPE9. o Output plot file. Default output plot file name is TAPE9. ZERO Zero length vector optimization. Valid values are ON and OFF. The default is OFF. When ZERO-ON, the optimizer removes zero length vectors. DUP Duplicate vector optimization. Valid values are ON and OFF. The default is OFF. When DUP=ON, the optimizer removes duplicate vectors. COIN Coincident vector optimization. Valid values are ON and OFF. The default is OFF. When COIN=ON, the optimizer combines collinear and overlapping lines. Note that COIN=ON removes a larger set of plot file vectors, since it combines a group of vectors into a single vector. PC Pen change optimization. Valid values are ON and OFF. The default is OFF. When PC=ON, the optimizer reduces the number of pen change commands on the plot file. This option is useful when it is known that the target plotting device stores its pens in a carousel, making frequent pen changes costly. GRID Grid square optimization. Valid values are ON and OFF. The default is OFF. When GRID=ON, the optimizer places a grid over the plot to improve optimizer performance. Vectors are eliminated from the plot file based on the grid square which contains their endpoints. With GRID-OFF, the optimizer removes a larger set of vectors at the expense of more processing time. STATS Staffstics option. Valid values are . ON and OFF. The default is OFF. When STATS=ON, optimization statistics are written to the job's output file. This option provides information that the installer can use in determining appropriate settings for the ZERO, DUP, COIN, PC and GRID parameters. It should be turned off for production runs. Depending on hardware and software factors involved in the plotting processes, adjustments to ZERO, DUP, COIN, PC, and GRID should be made, allowing for appropriate trade-offs between optimizer processing time and plotter throughput time. ----._.--_ ......... __ .• 6-18 ICEM DON V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.10 TAPE9 PLOT FILE OPTIMIZER Diagnostic messages are written to the file "OPTERR." 6.10.1 OPTIM RESTRICTIONS The program makes use of the temporary files 'ZZZZTXT,' 'ZZZZT9A,' and 'ZZZZT90,' so neither the input or the output file should have these names. 6.10.2 OPTIM ERROR MESSAGES CAN'T OPEN INTERNAL SCRATCH FILE. This message occurs during initialization when the scratch file is being opened. The usual cause is that the file already exists in an unknown format, or a system error. CAN'T OPEN PLOT FILE FOR READING. This message occurs during initialization when the input file is being opened. The usual cause is that the file does not exist. CAN'T OPEN PLOT FILE FOR WRITING. This message occurs when the output file is being opened. CHARACTER COUNT < O. This message occurs when a text command character count that is less than zero. is found with a CHARACTER COUNT EXCEEDS MAXIMUM. This message occurs when a text command is found with a character count that exceeds the maximum (currently limited to 200 by UNIPLOT). 6-19 ICEM DON V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.10.2 OPTIM ERROR MESSAGES CHARACTER STRING TOO LONG. This message occurs whe'n a text command is found wi th a character string that is longer than the maximum. This can only occur on NOS, since on NOS the string is stored in 6/12 format and the number of characters needed to represent an ASCII string may be up to twice as many as on an ASCII machine. COMMAND TYP~ NOT SUPPORTED. This message occurs while the plot commands are being read from the input file. This message will appear if the input file contains commands other than move, draw, change pen, end-of-plot, end-of-file, or text commands. DUPLICATE VECTOR OPTION INVALID. This message occurs if the DUP parameter is other than OFF or ON. set to a value ERROR OCCURRED OPENING LIST FILE An error occurred trying to open the file which contains fatal error messages. ERROR OCCURRED READING PLOT FILE. This message occurs while the plot commands are being read from the input file. The usual cause is that the input file is not formatted correctly. -= GRID OPTION INVALID. This message occurs other than OFF or ON. if the GRID parameter is set to a value INVALID PARAMETER. This message occurs when an unknown control card parameter keyword is passed to the optimizer • _ - - - - - - - - - _.. _._ ...... . 6-20 ICEM DON V1.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.10.2 OPTIM ERROR MESSAGES KEYWORD = VALUE EXPECTED. This message occurs during initialization when any control card parameter information is passed to the optimizer using a form other than 'keyword=value'. PEN CHANGE OPTION INVALID. This message occurs other than OFF or ON. if the PC parameter is set to a value PLOT FILE VERSION NOT SUPPORTED. This message occurs during validation of the header. The usual cause is the header is missing. PLOT OPTIMIZER ABORT. plot file UNKNOWN CAUSE. Message is self-explanatory. PREMATURE END OF PLOT FILE. This message occurs while the plot commands are being read from the input file. The cause is that the end of input file is sensed before the end of plot file command is found. STATISTICS OPTION INVALID. This message occurs if the STATS parameter is set to a value other than OFF or ON. -= ZERO LENGTH VECTOR OPTION INVALID. This message occurs other than OFF or ON. if the ZERO parameter is set to a value 6-21 ICEM DON V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.11 INCREMENTAL POINTS ON ELLIPSES AND HYPERBOLAS 6.11 INCREMENTAL POINTS ON ELLIPSES AND HYPERBOLAS Following the text on page 1-22 of the ICEM Design/Drafting Basic Construction for NOS manual, add the following note: "If an of by you desire evenly spaced incremental points along ellipse or hyperbola, a Bezier Curve representation the ellipse or hyperbola can be used. This is done using F.15.2.7.1.4 CONVERSION to approximate the curv~ by a Bezier curve. (This function does not change the initial curve in any way.) Evenly spaced incremental points can then be placed along the Bezier curve." 6.12 MSTRNG STATEMENT IN GPL The following note should be added to page Design/Drafting GPL for NOS manual: 8-4 of the ICEM "Caution should be used when GPL programs which contain MSTRNG statements are initiated from a programmed tablet square. None of the tablet square commands following the GPL program name will be executed." 6.13 CHAIN SELECT TOLERANCE The following menu item should be added under MODALS on page 2-18 of the ICEM Design/Drafting Introduction and System Controls for NOS manual: 10.CHAIN SELECT TOLERANCE 0.001 to 0.000000001 inch The following note should be added to .page 2-21 of the ICEM Design/Drafting Introduction and System Controls for NOS manual: 6-22 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.13 CHAIN SELECT TOLERANCE 10 If you select 10.CHAIN SELECT TOLERANCE from the Modals menu, you can set the tolerance that is used by chain select to identify contiguous entities. The system displays: CHAIN SELECT TOL = n.nnnn When the modal is selected, its current value is displayed. Enter the desired chain select tolerance. The default value is 0.001 inch (0.0254 millimeter). Valid input is between 0.001 inch .(0.0254 mm) and 0.000000001 inch (0.000000025 mm). If invalid input is entered, an error message is output and the system reprompts you for a valid chain select tolerance. The following menu item should be added under DISPLAY SELECTION SYSTEM MODALS on page 3-29 of the ICEM Design/Drafting Introduction and System Controls for NOS manual: 11.CHAIN SELECT TOLERANCE 0.001 The following menu item should be added under CHAIN SELECT MODALS on page 3-30 of the ICEM Design/Drafting Introduction and System Controls for NOS manual: 4.CHAIN SELECT TOLERANCE 0.001 Enter 4 to change the chain select tolerance value The following note should be added to page 3-31 of the ICEM Design/Drafting Introduction and System Controls for NOS manual: If you select 4.CHAIN SELECT TOLERANCE from the Chain Select Modals menu, you can set the tolerance that is used by chain select to identify contiguous entities. The system displays: CHAIN SELECT TOL = n.nnnn When the modal is selected, its current value is displayed. Enter the desired chain select tolerance. The default value is 0.001 inch (0.0254 millimeter). Valid input is betw~en 0.001 inch (0.0254 mm) and 0.000000001 inch (0.000000025 mm). If invalid input is entered, an error message is output and the system reprompts you for a valid chain select tolerance. 6-23 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.14 TOLERANCE SPECIAL CHARACTER SYMBOLS FOR ANSI 6.14 TOLERANCE SPECIAL CHARACTER SYMBOLS FOR ANSI The following symbols should be added to Table I-Ion page 1-7 of the ICEM Design/Drafting Drafting Functions for NOS manual: Character Entry Symbol Symbol Name \+ + Plus for tolerancing Minus for tolerancing . \- The following note should be added to page 1-94 of Design/Drafting Drafting Functions for NOS manual: the ICEM "ICEM DON will always create tolerances from the tolerance menu so that the text will display as stacked. Text to be displayed nons tacked on a single line may be added with the modify text menu (16.13.6)." -= ----- ....... -._.._._." 7-1 ICEM DON V1.65 Software Release Bulletin June, 1988 7.0 NOS TAPE3 RESTORE UTILITY 7.1 INTRODUCTION This document describes how the NOS TAPE3 Restore Utility works. The program restores a damaged TAPE3 by reading the damaged parts and copying them off onto the file TAPE2. The part index and the first sector are reconstructed and updated. This utility is useful when the part file is truncated, the part index lost, or the first sector is overwritten. ICEMDDN will abort ;f the first sector is overwritten. If the part is truncated and/or the part index is lost, ICEMDDN will indicate that there are no parts, bad parts, or a bad index on the TAPE3. It is recommended that an experienced analyst work with such part files to determine the appropriateness of using the CONVT3 program, to help insure proper recovery of as many parts as possible, and to investigate the original cause of the problem. 7.2 APPLICABLE DOCUMENTS The format of the TAPE3 file is documented in V1.64 System Programmer's Reference Manual. the ICEM DON 7.3 PROGRAM DESCRIPTION The program reads the damaged part file and looks for a correctly formatted first sector. If the first sector is incorrect, a new one is generated and the user is informed. The program~hen looks for part separators and copies each part and file first sec· -r off to TAPE2. After the last part is found, the part index .1 generated and the first sector part length is updated. Inactive parts can also be found in the part file. Because the part index is the usual area of the part file to be lost, CONVT3 cannot tell dormant parts from active ones. Thus, more than one copy of a part can be recovered. In order to uniquely identify duplicate parts, a program-generated name is appended to the the front of these part names. The last 10 characters of the 70 character part name are dropped. This is necessary in order to guarantee that the part name is unique. .. 7-2 ICEM DON V1.65 Software Release Bulletin June, 1988 7.0 NOS TAPE3 RESTORE UTILITY 7.3 PROGRAM DESCRIPTION Each part will have the name "RESTORExxx" as the first characters of the part name. The xxx starts at 1 increases by 1 for each part on the file. ten and 7.4 INSTALLATION OF CONVT3 There are two ways that CONVT3 can be installed: 1. The program can be SYSEDITed into the operating system or built into. the deadstart file so that the user simply enters "CONVT3" to execute it. 2. The program can be executed by entering the file name. by attaching the file and 7.5 CONVT3 PROGRAM EXECUTION This program requires the damaged part file be local and named TAPE3. The program will generate a new part file named TAPE2. The damaged parts should be brought up with ICEMDDN to verify if they are correct. A run through part renew or part check is recommended. When a part file is damaged because of an unknown bug, hardware failure, or track limit, the parts on the par~ file can be harmed in any number of ways. Therefore, it is important to check the part to find what is damaged. It is possible that a bad part can cause the ICEMDDN product to abort. These parts should be deleted from the recovered part file. 7.6 NOTES AND CAUTIONS When CONVT3 = program patterns are dropped. is run, the UTF data and pre-Vl.60 ., 7-3 ICEM DDN Vl.65 Software Release Bulletin June, 1988 7.0 NOS TAPE3 RESTORE UTILITY 7.7 CONVT3 PROGRAM OUTPUT 7.7 CONVT3 PROGRAM OUTPUT The CONVT3 program lists the parts being processed as follows: PROCESSING = part name SHEET = sheet number part name SHEET sheet number NUMBER OF PARTS = number of parts TAPE2 LENGTH = length of tape2 RESTORATION COMPLETE - RESTORED PARTS ON TAPE2 STOP RESTORATION COMPLETE The CONVT3 program issues the following error messages: Message Description and Error Handling EMPTY OR IMPROPERLY FORMATTED TAPE3 and/or NO PARTS FOUND - ABORT The file TAPE3 does not have a ICEMDDN first sector on it and no parts were found before the end of the record. READ ERROR - ABORT or WRITE ERROR - ABORT An unrecovered disk error occurred on a CONVT3 working file. This is an informative message , that the beginning of the part file was ~ver~r{tten or an incorrect file was used as input to the CONVT3 program. The CONVT3 program will generate a new first sector on TAPE2 and continue scanning for parts. FIRST SECTOR OF TAPE3 IS NOT CORRECTLY FORMATTED and FIRST SECTOR RECONSTRUCTED end CONTROL DATA CORPORATION ICEM DDN Version 1.65.0.00 SOFTWARE RELEASE BULLETIN NOS 2.5.3 Operating System Level: Date: Level 688 June, 1988 DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Control· Data Corporation gives the user permission to reproduce this document. Please call the following-HOTLINE numbers if you have any problems or questions: 1-800-345-9903 1-612-851-4131 U.S. and Canada International Additional information pertinent to this release may be found in SOLVER Installation Bulletins for ICEM products. *** URGENT *** Please make this document available to all ICEM DDN users. SMD131838 1 June, 1988 Table of Contents 1.0 INTRODUCTION 1-1 2.0 VERSION 1.65 FEATURE REVIEW 2.1 SELECTION TOLERANCE IN CHAIN SELECT • • • • 2.2 TOLERANCE SPECIAL CHARACTER SYMBOLS FOR ANSI . 2.2.1 CREATING TOLERANCES VIA MENU 16.13.4.1 •. 2.2.2 UPDATING DIMENSION TEXT CONTAINING TOLERANCES 2.2.3 MODIFYING TEXT WITH TOLERANCE SPECIAL CHARACTER SYMBOLS • • • • . . . • • . • • • 2.2.4 NOTES AND CAUTIONS . . . • . • . • . • . 2.3 POINT TO POINT GPG ENHANCEMENT . . . • . 2.4 TAPE3 RECOVERY UTILITY • . . . . 2-1 2-1 2-2 2-3 2-4 3.0 PSR CORRECTIONS INCLUDED IN THIS SSU . 3-1 4.0 4.1 4.2 4.3 4-1 4-1 4-1 4-2 COMPATIBILITIES . . . . . . . . VERSION NUMBERS OF RELATED ICEM APPLICATIONS. ICEM DDN VERSION 2.0 .... ICEM DDN UNDER IWOS • • . . • . 5.0 NOTES AND CAUTIONS . . • • 5.1 VERSION 1.65 VIEW CLIPPING. • • • • 5.2 PART INTEGRITY REPORT . • • • • 5.3 PART INTEGRITY PSR FIXES _. . 5.4 POST PROCESSOR WORD LIBRARY UPDATE 5.4.1 HOW PART UPDATE HANDLES TOOLPATH • • • • . • . 2-5 2-6 2-6 2-8 5-1 5-1 5-2 5-2 5-2 PPLIB WORDS BEFORE 1 • 65 . . . . . . . . . . . . . . . . . 5.4.2 HOW PART UPDATE HANDLES TOOLPATH PPLIB WORDS IN 1.65 5.5 SURFACE MILLING CHANGES • . . . 5.6 3 AXIS FLANGE FEATURE REMOVED . . • . . • . . 5.7 USING MSTRINGS AFTER SUSPEND 5.8 DECREASE OF TAPE3 • • • • • • • . • • • 6.0 POST-1.62 ICEM MANUAL CHANGES • • • • . • • . 6.1 CONTINUED TOOLPATH STATEMENTS IN CL FILE GENERATION 6.2 GPL MSTRNG MANUAL CHANGE • . • • • • • • • • . 6.3 GPL SPLINE MANUAL CHANGE . • • •. • ••. 6.4 GPL PREFIX MANUAL CHANGE • • • • • 6.5 CURVE MESH SURFACE MANUAL CHANGE • 6.6 NEW ICEM DDN CONTROL CARD PARAMETERS 'RO' AND 'LF' 6.7 CLFILE TRANSLATION • • • • • • • 6.7.1 ALTERNATE INPUT FILE FORMAT 6.7.2 NEUTRAL FORMAT DEFINITION 6.7.2.1 Definitions • • • . 6.7.2.2 File header • • • • 6.7.2.3 CL data record 6.7.2.4 End of file record . • • • . 6.7.2.5 Example • • • • 6.7.3 CL FILE STRUCTURE 5-3 5-3 5-4 5-5 5-5 5-5 6-1 6-1 6-2 6-2 6-2 6-3 6-3 6-5 6-8 6-9 6-10 6-11 6-11 6-116-12 6-12 2 June, 1988 6.8 IPARTD SAVE . . . . . . . . . • . . 6.9 IPARTD MODALS . . . . . . . . . . • . . 6.10 TAPE9 PLOT FILE OPTIMIZER. . . . • . . 6.10.1 OPTIM RESTRICTIONS 6.10.2 OPTIM ERROR MESSAGES . • • . 6.11 INCREMENTAL POINTS ON ELLIPSES AND HYPERBOLAS 6.12 MSTRNG STATEMENT IN GPL . . . . • . • • . . . 6.13 CHAIN SELECT TOLERANCE • • . • • • . . . 6.14 TOLERANCE SPECIAL CHARACTER SYMBOLS FOR ANSI 6-15 6-15 6-16 6-18 6-18 6-21 6-21 6-21 6-23 7.0 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7-1 7-1 7-1 7-1 7-2 7-2 7-2 7-3 NOS TAPE3 RESTORE UTILITY INTRODUCTION . . . . . . • . . APPLICABLE DOCUMENTS . . . . • PROGRAM DESCRIPTION . . . . INSTALLATION OF CONVT3 . CONVT3 PROGRAM EXECUTION NOTES AND CAUTIONS . . CONVT3 PROGRAM OUTPUT --- .... _._-_..._..._-_ ... _-- 1-1 ICEM DON V1.65 Software Release Bulletin June, 1988 1.0 INTRODUCTION 1.0 INTRODUCTION This SOFTWARE RELEASE BULLETIN (SRB) is designed to inform site analysts and ICEM DON users of PSR/RSE corrections and enhancements which are contained in the ICEM DON V1.65 Software System Update (SSU). In addition, this document contains relevant comments and descriptions of changes which should be· made to the ICEM DON V1.62 Reference Manuals. Any information not included in this SRB but pertaining to the SSU is documented on a SOLVER Installation Bulletin. This SSU includes all corrections from the V1.64 Batched Critical Updates (BCUs) and supersedes all previous NOS ICEM V1.6 releases. ------------, "._",., ,." "" -""-""-'". 2-1 ICEM DDN V1.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.0 VERSION 1.65 FEATURE REVIEW 2.1 SELECTION TOLERANCE IN CHAIN SELECT A new modal in menus F.1.ll.2.4, E.7.l0, and F.l.ll.l enables the user to modify the tolerance used by chain select to identify contiguous entities. These tolerances are used for all entity selections made via ch~in select. Chain Selection Modals in Entity Selection Control have been increased to four items (F.I.II.2.4). --- CHAIN SELECT MODALS I.CHAIN SELECT MODE 2.CHAIN SELECTN METHOD 3.DISALLOW PRESELECTED CURVES 4.CHAIN SELECT TOLERANCE Modals in .Entity (E.7.l0). E/D SCREEN OFF 0.001 Selection have been increased to ten items --- MODALS I.REPEAT INCLUDE/EXCLUDE 2.CONSTRAINT SET DURATION 3.SELECTION MODIFICATION 4.SINGLE SELECT FROM GROUP 5.CHAIN SELECT MODE 6.CHAIN SELECT METHOD 7.DISALLOW PRESELECTED CURVES 8.ATTENTION INDICATORS 9.CONSTRAINT SET LEVEL 10.CHAIN SELECT TOLERANCE ON ONCE OFF OFF E/D SCREEN OFF ON CUR 0.001 Display Modal Status in Entity Selection increased to eleven items (F.I.l1.1). Control has been 2-2 ICEM DDN Vl.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.1 SELECTION TOLERANCE IN CHAIN SELECT SELECTION SYSTEM MODALS 1.CHAIN SELECT MODE 2.CHAIN SELECT METHOD 3.DISALLOW PRESELECTED CURVES 4.SINGLE SELECT FROM GROUP 5.ATTENTION POINT OF LINES 6.REPEAT INCLUDE/EXCLUDE 7.CONSTRAINT SET DURATION 8.SELECTION MODIFICATION 9.SELECTION METHOD 10.HIGHLIGHTING METHOD ll.CHAIN SELECT TOLERANCE E/D SCRN OFF OFF MID ON ONCE OFF SCRN ATT IN 0.001 When the modal is selected, its current value is displayed. The default value is 0.001 inch (0.0254 millimeter). Valid input is between 0.001 inch (0.0254 mm) and 0.000000001 inch (0.000000025 mm). If invalid input is entered, an error message is output and the system reprompts you for a valid chain select tolerance. 2.2 TOLERANCE SPECIAL CHARACTER SYMBOLS FOR ANSI Two Special Character Symbols have been added to allow greater flexibility when creating tolerances in ANSI dimensions. The additional Special Characters are used to control when tolerances should be displayed as stacked. See Table A, Special Character Symbols, for the list of all predefined characters and associated symbols. - -- ---------------- ---------------.---------_._._---_._-- .._---- .. .... _ _.---------_ ... _-- ------------- (c /)-/ ./'/j/li"/ .f 2-3 ICEM DON V1.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.2 TOLERANCE SPECIAL CHARACTER SYMBOLS FOR ANSI TABLE A SPECIAL CHARACTER SYMBOLS Character Entry Symbol Name \0 \L \0 \R \S \B \C Depth Left Bracket Diameter Right Bracket Square Counterbore Countersink Degree Plus/minus Plus for tolerancing Minus for tolerancing Prefix character All other characters \ \@ \+ \- \\ \c When using ICEM DON to place dimensions in a working drawing it is common to have tolerances and other combinations of plus or minus signs in drafting text display as stacked. At times stacking should not be done, however. The following shows an example of each. Linear dimension with tolerance and Radius dimension with thread callout <---- +.010 5.000 ----> <---- .500-20UNC-3B -.000 2.2.1 CREATING TOLERANCES VIA MENU 16.13.4.1 When creating tolerances that are not equal using the tolerance menu, the Special Character Symbol for the tolerancing plus or tolerancing minus sign will be added into the dimension text. (Equal and opposite tolerances will continue to use the plus/minus sign \@ representation). The 2-4 ICEM DDN Vl.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.2.1 CREATING TOLERANCES VIA MENU 16.13.4.1 presence of the tolerancing Special Character Symbols signify that the text would be displayed as stacked, like the linear dimension shown on the previous page. ICEM DDN will always create tolerances from the tolerance menu so that the text will display as stacked. Text to be displayed nons tacked on a single line may be added with the modify text menu (16.13.6). 2.2.2 UPDATING DIMENSION TEXT CONTAINING TOLERANCES All dimension drafting entities containing tolerances will be updated to use the Tolerance Special Character Symbols. ICEM DDN will examine the text associated with the dimension to determine if tolerances are present. If tolerances are encountered,the plus or minus signs located within the text will be replaced with the Special Character 'Symbols for'a plus or minus tolerance. On NOS, the character count for the string will be incremented by two for each pair of tolerances, because the Special Character Symbols require a two character representation. When searching for tolerances, ICEM DDN will only allow character string representations signifying tolerances that could have been created automatically. Whether they were actually created by the tolerance menu or by the modify text menu is irrelevant since they are processed identically. The following criteria are used when searching for tolerance strings: 1. Notes and Labels are excluded. 2. Only numerics are allowed (i.e. 0123456789)-alphabetic or other characters are not allowed, with a few exceptions outlined below. 3. Spaces within tolerances are not allowed. The only exceptions are metric zero tolerances which display as "0" and fractional formats which use spaces in the numerator or denominator portion of the text. A space is used as a delimiter between the second tolerance and any suffix or trailing text. 4. Special character symbols are not allowed. 2-5 ICEM DDN V1.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.2.2 UPDATING DIMENSION TEXT CONTAINING TOLERANCES 5. Degree symbols, foot marks, and inch marks are allowed. 6. Each line of text will be processed to locate tolerances. In the past, tolerancing was restricted to only the first line of text. 7. Only one pair of tolerances is allowed per line within the dimension. Only the first pair of tolerances encountered on a line will be updated to use the Tolerance Special Character Symbols. I The criteria mentioned above are only applicable within the substrings of dimension text that could be interpreted as tolerances. It is possible that portions of dimension text may get incorrectly updated, either because ICEM DDN thought a tolerance was found or the text substrings could not be validated as tolerances. These occurrences will be rare and are easily reversed using the modify text menu. 2.2.3 MODIFYING TEXT WITH TOLERANCE SPECIAL CHARACTER SYMBOLS The Tolerance Special Character Symbols may be used within any drafting entity just like any of the previous Special Character Symbols. When placed within dimensions only, the Tolerance Special Character Symbol signals that a tolerance follows and that the text should be displayed as stacked. When used within other drafting entities, the current Prefix Character will display with the Tolerance Special Character Symbol to allow these symbols to be recognized and removed easily. Stacked tolerances must be paired within a line. If only one Tolerance Special Character Symbol is present within a line, no text will display stacked. In addition, the current Prefix Character will display with the Tolerance Special Character Symbol. This will enable any mismatched Tolerance Special Character Symbols entered by hand to be recognized and corrected easily. - - - - - - - - - -. .- - - - . - - - - - - - - - - - - - - - - - - - - - - - - - 2-6 ICEM DDN V1.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.2.3 MODIFYING TEXT WITH TOLERANCE SPECIAL CHARACTER SYMBOLS Text may be displayed as stacked within any line of text. dimension Only one pair of tolerances is allowed on a single line of dimension text. Extra occurrences of Tolerance Special Character Symbols will display with the current Prefix Character so that the text may be corrected. When tolerances are used along with suffix or other trailing text, a space must be used as a delimeter between the second tolerance and the suffix or trailing text. When the unprefixed plus or minus sign is used, the text will be displayed as it was entered, with no stacking or adding of the current Prefix Character. 2.2.4 NOTES AND CAUTIONS It is recommended that the Prefix Character be changed from slash (\) under the following the default reverse circumstances: 1. If dimensioning is being done with fractions, the reverse slash is used in the fraction text representation, causing problems interpreting the dimension text. 2. GPL uses the reverse slash to signal the beginning of a new line. Because of this conflict, the Special Character Symbols will be processed incorrectly during GPL programs. The Prefix Character may be changed in menu SET PREFIX. 16.1.1.5 SPECIAL- 2.3 POINT TO POINT GPG ENHANCEMENT A new statement has been created for the point to point generation parameter group. The new statement "SAPPRT" replaces the statement "SRTRCT". Previously the "SRTRCT" statement offered no control over the first and last retract plane moves. The "SAPPRT" statement has the same funtionality 2-7 ICEM DDN Vl.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.3 POINT TO POINT GPG ENHANCEMENT of the "SRTRCT" statement plus control over the first and last retract plane moves. To more completely describe the tool motion offered by the "SAPPRT" statement the menu that is used to set "SAPPRT" options has been renamed. The menu entitled RETRACTION BETWEEN POINTS that appears in the point to point modify GPG menu has been renamed APPROACH/RETRACT. Selection options of the APPROACH/RETRACT menu remain the same as the RETRACTION BETWEEN POINTS menu: 1. 2. 3. 4. NONE CLEARANCE RETRACT PLANE PROMPT The following question will appear when NONE or CLEARANCE 1S selected from the APPROACH/RETRACT menu to indicate if the first and last retract moves are to be included in the toolpath: MOVE TO THE RETRACT PLANE BEFORE THE FIRST POINT AND AFTER THE LAST POINT ? The format of the "SAPPRT" statement is very similar to the old "SRTRCT" statement. The only difference is a YES or NO appearing after the minor word NONE or CLEARANCE. The possible settings of the "SAPPRT" statement are as follows: SAPPRT/NONE,YES SAPPRT/CLEAR,YES SAPPRT/RETRCT SAPPRT/NONE,NO SAPPRT/CLEAR,NO SAPPRT/PROMPT The YES and NO values appearing after NONE and CLEAR control the first and last retract moves. YES indicates the first and last move are wanted in the toolpath, and NO indicates they are to be omitted from the toolpath. To maintain compatabiltiy with existing GPGs the. old "SRTRCT" statement will still be readable from a file. The settings of the statement will be converted to a functionally equivalent form of the new "SAPPRT" statement whenever the old statment is read. 2-8 ICEM DDN Vl.65 Software Release Bulletin June, 1988 2.0 VERSION 1.65 FEATURE REVIEW 2.4 TAPE3 RECOVERY UTILITY 2.4 TAPE3 RECOVERY UTILITY A TAPE3 restore utility is provided to assist in the recovery of parts damaged by system failure or other catastrophic events. Please see Section 7.0 for a more detailed description of this utility. 3-1 ICEM DDN V1.65 Software Release Bulletin June, 1988 3.0 PSR CORRECTIONS INCLUDED IN THIS SSU 3.0 PSR CORRECTIONS INCLUDED IN THIS SSU This section contains a cumulative list of problems resolved in V1.65. The full text descriptions can be obtained through SOLVER. PRIORITY CODE: C U S M= CRITICAL URGENT SERIOUS MINOR PSRS CORRECTED IN DDN V1.65 PSR II PRI AD2B229 AD2B246 AD2B257 AD2B260 AD2B274 AD22470 AD22547 AD22706 AD22764 AD22789 AD23036 AD23351 AD23384 AD23470 AD23503 AD23520 AD23562 AD23568 AD23577 AD23578 AD23588 AD2A775 AD2B099 AD2B107 AD2B289 C C C C C C C C C C C C C C C C C C C C C U U U U DESCRIPTION CLFILE GENERATION DOESN'T OUTPUT ARCSLP IN APT4 CLFILES SURFACE MILLING ABORTS WITH "TABLES FULL" MESSAGE PART INTEGRITY SOMETIMES REMOVES ENTITIES WHICH ARE DISPLAYED CORRECTLY PART ON TAPE3 DID NOT CONVERT TO NOS/VE VIEW BOUNDARY TOPS MAY BE UNCONDITIONALLY RESET (LOWERED) TRASHED TAPE3 WON'T RETRIEVE EXISTING PARTS OR CREATE NEW ONES FILLET DOESN'T WORK BETWEEN AN ARC AND A 2-DEGREE LINE FAN POINTS AND INTERSECTION POINTS ON AN ELLIPSE ARE INCORRECT CORRUPT TAPE3 CAUSED BY THE NOS DIRECT ACCESS FILE LIMITS HORIZ LEADER LINE ON DATUM FEATURE SYMBOLS BECOMES "SLANTED" BY 1.60 PART FILING LEAVES VACANT SPACE PATTERN UPDATE FROM 1.62 TO 1.63 DOESN'T WORK UNABLE TOXFER HOST PART SHARING FILES FROM NOS TO IWOS 2.1 DDN 1.63 SECOND +/- SIGN WILL BE STACKED ON THE FIRST LINE - WRONG TOLERANCE STACKING PROBLEMS IN V1.64, CORRUPTS DATA ENTITIES ARE MISSING FROM A DRAWING AFTER CONVERSION TO NOS/VE NC POINT/POINT PLACES GOTO RETRACT AT START & END OF TOOLPATH CANNOT RENEW PART TWICE IN THE NOS-NOS/VE MIGRATION UTILITIES SOME FILES FAIL MIGRATION IN PARTA (15.3.7) FILLET SURFACE IS STILL BROKEN - WILL NOT GENERATE FULL SURF. IeEM DATA MIGRATION UTILITY V2.0.0 FAILS AFTER PROCESSING AN IPARTD INTERSECTION POINT BETWEEN DRAFT CURVE AND LINE IS INCORRECT UNABLE TO RESTORE IPARTD PARTS WITH 4 DIGIT SHEET NUMBERS PLANE THROUGH PT PERP TO TWO PLANES IS NOT WORKING IDENTIFY ATTRIBUTE ONLY WORKS IN VIEW OF DEFINITION OF ENTITY 3-2 ICEM DDN V1.65 Software Release Bulletin June, 1988 3.0 PSR CORRECTIONS INCLUDED IN THIS SSU AD22368 AD22411 AD22765 AD22766 AD22974 AD23088 AD23130 AD23301 AD23306 AD23354 AD23355 AD23383 AD23417 AD23432 AD23438 AD23471 AD23472 AD23486 AD23516 AD23542 AD23550 AD23591 AD2A728 AD22995 AD22999 AD23213 AD23262 AD23339 AD23405 AD23462 AD23468 AD23504 AD23505 AD23510 AD23554 AD2A698 AD2A96 0 AD23367 AD23488 U (11.8)MODIFY ANGLES GIVES UNPREDICTABLE RESULTS U NOTE PARALLEL TO ARC NOT FUNCTIONING CORRECTLY WITH USER DEFINED CHAR U TEXT IN FRONT AND BACK VIEWS OF 3D PATTERN IS DISPLAYED AT SAME TIME U ~ARAL~.J;:L DIMENSIONS MO.VE WHEf{_MODIF.IED-E.._16_."2 •. 3~ U [672.11 RECTANGULAR COORDINATES DO NOT WORK WHEN AUTO TAIL LOC - OFF U NOT MEETING ANSI-1982 STANDARD/DEC.PL ON MM SURFACE SYMBOLS U DESIRE MODAL TO SET SYSTEM TOLERANCE TO 0 U DASH CREATES A NEW TOLERANCE IF IT APPEARS BEFORE A +- TOLERANCE U SECTION LINING CANNOT BE MODIFIED ON DATUM TARGETS U WHEN CONTINUING AFTER SUSPEND, MSTRING DOES NOT WORK U UPDATE OLD PARTS FROM V1.50 THRU V1.62 U ROTATE 3-D PART (SURFACES INCLUDED) CAUSED PROBLEMS U TABLES FULL ERROR MESSAGE CAUSED BY EXCESSIVE DORMANT ENTITIES U ICEM DDN N/C POINT TO POINT TOOLPATH GENERATION U ASSUMPTION THAT THE FIRST LINE OF A DIMENSION WILL CONTAIN A TOLERANCE U PRE 1.64 LAYOUTS WILL NOT DISPLAY TOP ,EDGE OF DDN DATA U RADIAL/DIAMETER DIMENSION STACKING OF KEY.:::IN__TEXT U OPTIM DOESN'T OUTPUT CORR~lliltpUT-F6R' DDNUTi'L TO PROCESS U PART NAME AND SHEET NO ON PART INTEGRITY REPORT U GROUP ENTITIES WITH ATTRIBUTES ASSIGNED ARE DELETED BY PART RENEW U ON NOS AND AOS/BAD ERROR MESSAGES - TEXT DELTA FROM TEXT U F.12.11 CREATES CORRUPT ENTITIES THAT HAD ATTRIBUTES ATTACHED TO THEM S USERS MAY INADVERTANTLY DEFINE PATTERN LIB FILES AS GLOBAL PART FILES S UNABLE TO CREATE PATTERN S (16.2.11.3) VERTICAL RECT. COORD. DlMEN. FAIL UNLESS AUTO TAIL IS ON S SUSPEND CAUSES MSTRING FILE TO BECOME INACCESSABLE FOR RESUMED SESSION S ICEM DDN 1.62 + TEK 4111 TERMINAL S NOS TAPE3 FILE SIZE SOMETIMES GROWS VERY LARGE EVEN FOR SMALL DRAWINGS S MODIFICATION OF FILLET ANGLE CAUSES INTEGRITY ERRORS S AFTER THE SUSPEND FUNCTION THE TABLET SHOULD MAINTAIN THE DEFINE NAME S MSTRINGS IN GPL PROGRAM DISALLOW MENU PICKS PROGRAMMED IN TFILE S NOTE COMMAND PRODUCES A SPACE AND i. SIGN IN CHARACTER POSe 183/184 S FILE FOR EVALUATION: PLOT FILE CREATION FLAKY, FILE/253 PRUS TO 6310 S DDN 157 TOOLPATH NON-STANDARD POSTPROCESSOR WORDS LOST WHEN UPGRADING S THROUGH A POINT,TANGENT TO A CURVE DOES NOT WORK WITH A SPLINE IN GPL M ARC THROUGH 3 PTS CREATES LINE WITHOUT WARNING USER M PRINTOUT FOR 5.6.7 IS INCONSISTENT WITH REF MANUAL M GPL COMPILER VERSION IS NOT CONSISTANT WITH DDN VERSION 1.63 M ARC THRU 3 POINTS (F.11.7) GENERATES LINE UNDER CERTAIN CONDITIONS 4-1 ICEM DDN V1.65 Software Release Bulletin June, 1988 4.0 COMPATIBILITIES 4.0 COMPATIBILITIES 4.1 VERSION NUMBERS OF RELATED ICEM APPLICATIONS The ICEM DDN 1.65 SSU is compatible Application Products under NOS 2: with the following DRAM Vl.l HASCO VI.l ICEM BEND VI.2 ICEM Engineering Data Library (EDL) VI.2.7 ICEM Facilities VI.41 ICEM Hydraulics VI.3 ICEM Kinematics VI.O ICEM Plastimould VI.l ICEM Solid Modeler VI.13 IGES Translators V2.23 LINCAGES Vl.2 MOLDFLOW V4.0 MOLDSTAR V3.0 4.2 ICEM DDN VERSION 2.0 ICEM DDN Version 1.65 enhancements in the compatibility to ICEM MIGRATION UTILITY. refer to sections 5.2 contains some PSR fixes and additional Part Integrity area to ensure upward' V2.0 through the use of the ICEM DATA For information on these corrections, and 5.3. You must use ICEM DATA MIGRATION UTILITY V2.0.2 and ICEM DDN V2.0.2 if you are using the Tolerance Special Character Symbols for ANSI. 4-2 ICEM DON V1.65 Software Release Bulletin June, 1988 4.0 COMPATIBILITIES 4.3 ICEM DDN UNDER IWOS 4.3 ICEM DDN UNDER IWOS Users of both NOS- and IWOS-based DON must use the following versions to ensure compatibility and translation between the two systems: IWOS: DON 1.65 NOS: DDN 1.65 If you perform part sharing between NOS and IWOS systems, both NOS and IWOS systems must use the same version. A part can be "updated" from pre-1.65 to 1.65, but once the part is at 1.65, it cannot be read by a pre-1.65 version of ICEM DON. The 1.65 part sharing utilities will be provided when ICEM DON 1.65 ~s released on IWOS . ... ..... ........ .... - " ........ _-_ .. _..... _..............._... _ ......._.....- ...... _ ..... _.. _............._.._--_._.. - .... _-_..-._--_ ....... _.. __.. _-_ ..- _ .. ....... _._._ .. _--_..__. _ - - - - - - - - - - - - - - - - - - - - - 5-1 ICEM DDN V1.65 Software Release Bulletin June, 1988 5.0 NOTES AND CAUTIONS 5.0 NOTES AND CAUTIONS 5.1 VERSION 1.65 VIEW CLIPPING This section only applies to pre-V1.64 parts that are into V1.65. brought With the screen size reduction that was done in V1.65, all views with the top boundary beyond the new screen boundary will appear clipped when first displayed in V1.65. This is a necessary side effect of the V1.65 tablet/screen realignment. To correct the display, an auto max-min (Z.ll) operation can be performed. (Note that for view layouts, the zoom mode should be "Entire Layout.") If you are using a different zoom scale, the scale can be easily adjusted by selecting ENTER SCALE (Z.8) and entering the following: 11'1: .95 This expression tells DDN to multiply the current zoom scale by the amount of the screen size reduction. The sequence, Z(tab)8(tab)H*.95, can be programmed into an MSTRING and used with an input trace script to readjust saved zoom scales in a semi-automated manner. Please note that these readjustment operations are not required; they are desirable only if data typically displayed in the upper portion of the screen appears clipped in the SSU. If you are using this SSU only for the purpose of migration to ICEM V2, and you are not planning to use the part in VI.65, no benefit is gained by doing zoom scale readjustments prior to migration. Parts created in or updated to VI.64 (or any V1.64 not be affected • . .... ,._ ... ---" .. BCU) will _-_.._-,.... .._.._.. _._--_._-._._.. _--_... --_. __...._._-_._ .._----_. __ ._------_._.. _ - - - - - - - - - - - - - - - - - - - - - - - - _ ,",' 5-2 ICEM DON V1.65 Software Release Bulletin June, 1988 5.0 NOTES AND CAUTIONS 5.2 PART INTEGRITY REPORT 5.2 PART INTEGRITY REPORT A column titled ACTION has been added to the part integrity report. The possible actions are RMV (for removed) or MOD (for modified). In previous versions corrupt entities were always removed during part renew. It is now possible to internally modify some corrupt entities rather than having to remove them. The part name and sheet number have been added to the banner of the part integrity report that is written to the file PRBRPLS when using the LF control card parameter. 5.3 PART INTEGRITY PSR FIXES Corrections to part integrity have been made in response to common problems encountered by customers ·in the migration process. These problems manifested themselves in various ways ranging from errors in the part integrity report to failure in migration. The following problems were corrected: o o o o o o o o duplicate sequence numbers zero-length line compatibility with V2.0.2 incorrect entity form numbers extra GRAPL entities invalid number of views incorrect COMMON values bad TAB2 and TAB3 data incorrect view updating 5.4 POST PROCESSOR WORD LIBRARY UPDATE New capability has been added to version 1.65 that will allow better updating of toolpaths regarding post processor words. Before 1.65 some of the post processor words would be replaced with asterisks in the updated toolpath. This new capability only affects toolpaths being updated from a pre-l.60 version of ICEMDDN to version 1.65. Toolpaths already created in, or updated to, a 1.6x version of ICEMDDN will not be affected. 5-3 ICEM DDN V1.65 Software Release Bulletin June, 1988 5.0 NOTES AND CAUTIONS 5.4 POST PROCESSOR WORD LIBRARY UPDATE When updating capability if: toolpaths, you may benefit from this - You have TAPE3 files that contain parts with a mixture of versions and at least one version is older than 1.60. - You use more than one version of ICEM DDN and one of the versions is older than 1.60. The benefit will affect you should you decide to update the pre-l.60 part. 5.4.1 HOW PART UPDATE HANDLES TOOLPATH PPLIB WORDS BEFORE 1.65 ICEMDDN versions 1.60 and newer use a different post processor word library ( PPLIB ) than pre-1.60 versions. When a part is updated from a pre-1.60 version to a 1.60 or newer version, a new 1.6x PPLIB is created. The new PPLIB is just a copy of the old one. Both the old and new version of the PPLIB will now be on the UTF of the TAPE3. Part update will then use the new PPLIB to check all words in any toolpath being updated. All subsequent part updates will now use the new 1.6x PPLIB. Since PPLIBs are stored on the UTF all the parts of a TAPE3 share the same PPLIB. A problem can arise if the new PPLIB is modified. Part update assumes the new 1.6x version of the PPLIB contains all the words that are in the pre-l.60 toolpaths. If a word is in an old toolpath, and not in the new PPLIB, part update will replace the word with asterisks in the updated toolpath. 5.4.2 HOW PART UPDATE HANDLES TOOLPATH PPLIB WORDS IN 1.65 In 1.65, part update uses the pre-1.60 version of the PPLIB if the part is pre-1.60. This means that part update does not assume that the 1.6x PPLIB contains all the words used by the old toolpaths. Any toolpath PPLIB word that is in the pre-1.60 PPLIB will be in the updated too1path. If a PPLIB word is used by an old toolpath and not in the pre-1.60 PPLIB, the word will be replaced in the updated toolpath by the major word subclass code placed between asterisks. Once a toolpath exists in a 1.60 or newer version, the new capability is not used. It is only used when the version of ICEMDDN is 1.65 and the part is older than 1.60. 5-4 ICEM DDN V1.65 Software Release Bulletin June, 1988 5.0 NOTES AND CAUTIONS 5.4.2 HOW PART UPDATE HANDLES TOOLPATH PPLIB WORDS IN 1.65 If you have toolpaths in parts older than 1.60 you should consider the following three points regarding part update. a) Part update in version 1.65 uses the pre-1.60 PPLIB to update pre-1.60 parts. The pre-1.60 PPLIB should contain all the PPLIB words used by the toolpaths that you plan to update. b) Updating all parts on a TAPE3 at the same time is the best way of migrating to a new version. This method guards against PPLIB words of toolpaths appearing as asterisks in the updated toolpaths. c) Part update may be slower when updating pre-1.60 parts containing toolpaths to version 1.65. This is due to the increased overhead needed to use the older PPLIB. If you are updating a large number of toolpaths the additional time needed may be significant. Updating to any 1.6x version before using version 1.65 may be faster. 5.5 SURFACE MILLING CHANGES a) Closed boundary is no longer used in conjunction with a surface. When a surface is selected in response to the CONTROL SURFACE menu the CUTPATH type menu will not be displayed. Closed boundary represents a subset of tool control offered by the containment processing in surface milling. Since all the capability of the closed boundary exists in containment, this represents no loss in functionality. b) When a surface is selected as the control surface, the CUT DIRECTION menu will no longer appear. The cut direction for a toolpath will be parallel with the U or V surface display paths. Whether the U or V paths are used is determined by indicating the start and end of the first cut with the graphics cursor. - - - - - ------ -----------,- ,- --------------------------- 5-5 ICEM DDN V1.65 Software Release Bulletin June, 1988 5.0 NOTES AND CAUTIONS 5.6 3 AXIS FLANGE FEATURE REMOVED 5.6 3 AXIS FLANGE FEATURE REMOVED The menu item 17.13 3 AXIS FLANGE CUTTING has been blanked due to removal of this feature. Other numerical control features in ICEM DDN allow the same toolpaths to be generated. 5.7 USING MSTRINGS AFTER SUSPEND Prior to version 1.65, re-entering a suspended ICEMDDN session would cause an error with tablet MSTRINGS. Attempting to execute a tablet square containing an MSTRING would result in an error message. The error message would notify the user that the MSTRING was not found. All defined MSTRINGS would become inoperable. In release 1.65 this problem has been corrected. 5.8 DECREASE OF TAPE3 Prior to version deleted entities space remained space is removed 1.65, if a working part became smaller due to and was subsequently filed, the extra unused on the TAPE3. In version 1.65, this extra whenever a part is reduced in size. - - - - - - - -_. -_._---_.-.-..._..- . 6-1 ICEM DON V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.0 POST-1.62 ICEM MANUAL CHANGES 6.1 CONTINUED TOOLPATH STATEMENTS IN CL FILE GENERATION Treatment of generation: a. continued toolpath statements in CL file The use of continuation and appended comment symbols The continuation symbol is a single S sign. All text following the single dollar sign is considered comment. The following line is considered to be the continuation of the current toolpath statement. The appended text symbol is a double dollar sign SS. All text following the double dollar sign is considered comment. The statement is considered to end before the SS. Note that S S will be treated as a S and not as aSS. The continuation and appended comment symbols are ignored in PARTNO, PPRINT, and INSERT statements. They are . treated as part of the text of the statement. The use of continuation on motion statements, circle statements, multax statements is invalid and is ignored at CL file creation. b. New 'error messages The following new error messages concerning continued toolpath statements have been added for output in the CL Print file. ** ** ** ** ** ** 'Ide ERROR ERROR ERROR ERROR ERROR ERROR ERROR ** ** ** ** *'Ie -Ie * ** ILLEGAL CONTINUATION MINUS NOT FOLLOWED BY NUMBER EXPECTED COMMA, FOUND EXPECTED SLASH, FOUND UNEXPECTED END OF LINE EXPECTED WORD OR NUMBER, FOUND RECORD EXCEEDS MAXIMUM LENGTH - - - - - - _ . -----_..... - ....... ...._ .... - . _ - - - - - - - - - - - - - - _ 6-2 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.1 CONTINUED TOOLPATH STATEMENTS IN CL FILE GENERATION Excerpt of a sample CL Print file : 1 ICEM NC CLPRINT DDN 1.64 PARTNO PPRINT THIS IS A TEST FOR CONTINUATION ($) AND APPENDED COMMENTS ($$). MODE $ THE NEXT TOKEN MUST BE A SLASH /AVOID,2. $$ END OF THIS PP STATEMENT MODE/AVOID $ A I , I IS EXPECTED BUT NOT GIVEN 20. $$ ERRONEOUS CONTINUATION LINE -Id: ERROR *-1: EXPECTED COMMA, FOUND 20. MODE,AAXIS,ADJUST $$ MAJOR WORD NOT FOLLOWED BY A / ** ERROR ** EXPECTED SLASH, FOUND 6.2 GPL MSTRNG MANUAL CHANGE On page 8-4 of Revi~ion C of the immediately below the blocked format and its description. ICEM GPL for NOS manual, NOTE is the MSTRNG statement Replace NORTN with NORTRN in both description. the format and parameter 6.3 GPL SPLINE MANUAL CHANGE On page 13-7 of Revision C of the ICEM GPL for NOS manual, the third sentence in the second paragraph should read as follows: A minimum of three points and a maximum of 100 points can be specified. 6.4 GPL PREFIX MANUAL CHANGE On page 19-18 of Revision C of the ICEM GPL for NOS manual, the following text should be added at the end of the second paragraph: Although the reverse slant is the default prefix character, it is also the default "new line" character. Since the "new line" character takes precedence over the prefix character, the PREFIX statement must always be used to to change the default when a special symbol character is used. - - - - - _ . _ . - . -..... .. _..... _ -----_._.-.-.- ._._... _.. __ ..._ - - - - - - - - - - - _ . 6-3 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.5 CURVE MESH SURFACE MANUAL CHANGE 6.5 CURVE MESH SURFACE MANUAL CHANGE In the ICEM DDN ADVANCED DESIGN for NOS manual, replace the description under 15.3.6 Curve Mesh Surface with the following: In the INDICATE CURVES description: FIXED CURVES INDICATE CURVES Use the graphics cursor to select the fixed curves in an ordered manner. Fixed curves can be lines, arcs, conics, two-dimensional splines, composite curves, point sets, three-dimensional splines, or machining curves. Fixed curves cannot be selected end-to-end. Curves that lie end-to-end should be redefined as a composite curve before selection as a fixed curve. You must select a least 2, but not more than 30 fixed curves. VARIABLE CURVES INDICATE CURVES Use the graphics cursor to select the variable curves in an ordered manner. Variable curves, like fixed curves, can be of any type. Variable curves that lie end-to-end should be redefined as a composite curve before selection as a variable curve. You must select at lease 2, but not more than 30 variable curves under the following restriction: . If you select "1. WITH TWIST VECTORS," the product of the number of fixed curves times the number of variable curves cannot exceed 203. If you select "2. LINEARLY BLENDED," the product cannot exceed 509. 6.6 NEW ICEM DDN CONTROL CARD PARAMETERS 'RO' AND 'LF' The following should be added to the list of optional ICEM DDN parameter settings found on pages 1-11 through 1-16 of the ICEM Design/Drafting Introduction and System Controls manual. 6-4 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.6 NEW ICEM DDN CONTROL CARD PARAMETERS 'RO' AND 'LF' LF List To File. Writes to specific local files some of the lists displayed on the screen during an ICEM DDN session. Listings will also be displayed on the screen unless the RO (Repaint Off) parameter is set. Default: Off. LF Sets List To File on. The following local files are produced when the respective list is generated from an ICEM DDN menu pick and LF is on. These files are always appended to, not overwritten. The list generated on the local file is always a complete list even if 'n' or '[' are entered at the continue listing prompt for screen display. A message indicates success or failure in writing to the local list file. ENTLS GPARTLS GUTFLS IPARTLS PARTLS PRBRPLS UTFLS RO Database part entity list: (f.6.6.1.3). Global parts file list: (f.6.1.1.3), (f.6.1.2.3) • Global UTF file list: (f.6.5.4.3). Independent parts file list: (f.6.1.9), (f.6.1.10) • Database file (TAPE3) parts list: (f.6.1.3), also by entering 'list' when creating a new, or retrieving an existing, TAPE3 part. Problem report list: (f.6.1.11.1), (f.6.1.11.2). Database UTF list: (f.6.5.1). Repaint Off. Disables redrawing of the display area and the generation of new entities in the display area. R entered as a function key will have no effect. Default: Off. RO Disables redrawing. Repaint Off is on. With Repaint Off enabled, specific lists which can also be written to local files will not be generated to the display area. See the LF parameter to determine which lists· can be generated to local files. 6-5 ICEM DON V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.7 CLFILE TRANSLATION 6.7 CLFILE TRANSLATION This utility to translate the binary formatted CL data from the neutral format CL file and vice versa is included with the 1.65 release of ICEM DON, however, it is executed directly from the operating system level. Alternate input and output files can be used as the first two parameters on the execution statement. The alternate input file contains the same data as would be entered at an interactive session. The execution statement is as follows: ICEMCLT [,ALTIN] [,ALTOUT] All data files needed should be local. Upon execution, an entry banner is displayed, showing the current version of the release. ICEM CL FILE TRANSLATOR COPYRIGHT CONTROL DATA CORPORATION 1987 REVISION 1.0 ICEM DDN 1.64 (NOTE - The CL File Translator that was provided for ICEM DON 1.64 also works for ICEM DON 1.65) The system then displays the SELECT TRANSLATOR FUNCTION menu with the current settings: ---SELECT TRANSLATOR FUNCTION 1.EXIT 2.GENERATE BINARY CL FILE 3.GENERATE NEUTRAL CL FILE 4.BINARY CL DATA FORMAT 5.BINARY CL FILE NAME 6.NEUTRAL CL FILE NAME - APT IV - CLFILE - CLTAPE Enter: 1 To end the translator session • ....__ ...._.. __ - _ _ - _ . .. .. 6-6 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.7 CLFILE TRANSLATION 2 To generate a binary CL file from a neutral format CL data file. If you choose option 2, the system displays: GENERATING (format) CL FILE (filename) FROM NEUTRAL CL FILE (filename) The CL file with the set file name is generated from the neutral CL data file with the set name. Any data already in the CL file is overwritten, even if generated in the same session. After a successful translation the following message appears: nn RECORDS WRITTEN TO THE CLFILE NO ERRORS ENCOUNTERED You are then returned to the main menu. After an unsuccessful translation, one of the following messages appears: a) b) c) NEUTRAL DATA FILE NOT RECOGNIZED CHECK FILE NAME OR FILE HEADER Action - Check if the correct file name is set. - Check if the file header was corrupted (see neutral file format definition). Result - No CL data written to CL file. NEUTRAL DATA FILE EMPTY OR NOT FOUND CHECK FILE NAME CHECK IF FILE IS LOCAL Action: - Check if the correct file name is set. - Check if the file is local Result - No CL data written to CL file. NEUTRAL DATA FILE IS CORRUPT AT OR AROUND RECORD record number CHECK FILE NAME OR EDIT ERRORS Action: - Check if the correct file name is set. - May occur after manual editing. - - - _ . . .__._----- .._. __ ._._-_. - - - - - - - - - 6-7 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.7 CLFILE TRANSLATION Result: - Check CL file contents. To generate a neutral format CL data file from a binary CL file. If you choose option 3, the system displays: 3 GENERATING NEUTRAL CL FILE (filename) FROM (format) CL FILE (filename) The neutral CL data file with the set name is generated from the CL file with the set name. Any data already in the neutral data CL file is overwritten, even if generated in the same session. After a successful translation, the following message appears: nn RECORDS WRITTEN TO THE CLFILE NO ERRORS ENCOUNTERED You are then returned to the main menu. After an unsuccessful translation, one of the following messages appears: a) END OF CL FILE ENCOUNTERED BEFORE FINI CHECK CL FILE FOR FINI, CHECK CL FILE NAME, FORMAT AND CONTENT. Action: - Check if the CL file contains a FINI. - Check if the correct CL file name is set. - Check if the correct CL data format was chosen. - Check if the file is available and contains the expected data. Result: - Check neutral format CL data file. BINARY FILE READ ERROR CHECK FILE NAME, FORMAT AND CONTENT b) Action: - Check if the correct CL data format was chosen. - Check if the file contains data. Result: No neutral format CL data generated. 4 To be prompted for binary CL file format, the system displays the following menu. Enter 1 to return to the main menu --- ---------------------------- - - - - - - - - - 6-8 ICEM DDN Vl.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.7 CLFILE TRANSLATION without changing the format. Enter 2 or 3 to select the desired format. Enter] or [ to return to the main menu without changing the format. ---SELECT BINARY CL FILE FORMAT I.EXIT 2.CDC APT III 3.CDC APT IV 5 To be prompted for the binary CL file name, the system displays: ENTER CL DATA FILE NAME Enter a valid file name. ? Enter or [ if the current file name is to be retained. To be prompted for the neutral format CL data file name, the system displays: ENTER NEUTRAL FORMAT CL DATA FILE NAME ? Enter a valid file name, Enter ] or [ if the current file name is to be retained. If an invalid file name is entered, the system displays: FILE NAME NOT VALID In this case, the original file name is retained. 6.7.1 ALTERNATE INPUT FILE FORMAT The contents of an alternate input file must be identical to the data that would be entered in an interactive session at the main menu and performing the desired translation(s). Examples: 1. A neutral file CLFILE has to be translated to an APT IV binary CL File CLTAPE. In an interactive session, at the main menu, first a 2 is entered to generate the binary CL file. Then a 1 is entered to end the session . __..... __ .._._-----_.--",,," ---------- ---" ""_ __ - - - - - - - .. " ....... ... 6-9 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.7.1 ALTERNATE INPUT FILE FORMAT The alternate input file contains 2 lines: 2 1 2. An APT III binary CL file CLTAP1 has to be translated to a neutral format CL File CLNEUT. In an interactive session, at the main menu, the following is entered: 4, change the binary CL file format 3 , set the format to APT III 5 , change the binary CL file name CLTAP1 , the binary CL file name 6 , change the neutral CL file name CLNEUT , the neutral CL file name 2 , generate the neutral CL file 1 , exit. The alternate input file contains 8 lines: 4 3 5 CLTAP1 6 CLNEUT 2 1 6.7.2 NEUTRAL FORMAT DEFINITION An APT CL File consists of a set of data records. Each data record has an integer and real part. The integer part contains general information as the type, number and length of the record. The real data part contains the specific record data, in real, integer or character form. " To be able to transfer this data from one operating system to another, it is wri tten out in a neutral format on an ASCII file. The file is a sequential, formatted file, containing character data. The file contains variable length records, lines, with a maximum length of 130 characters. 6-10 ICEM DON V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.7.2.1 Definitions 6.7.2.1 Definitions data type specifier: single upper case character, indicating the data type of the data in the following field. Three data type specifiers are defined: I: F: A: preceeds an integer number data field preceeds an floating point number data field preceeds a character data field data field: fixed length character string containing the data corresponding to one logical CL data word. The length is data type dependent. data element: a data type specifier followed by the data field. integer data element: the data specifier I followed by a fixed length character representation of an integer number. e.g.: I 2000 represents the integer 2000 in a ten character integer data field. floating point data element: the data specifier F followed by a fixed length character representation- of a floating number in exponential format: A one character sign field, a normalized fixed length mantissa without decimal point, a one character sign field and a fixed length exponent. e.g.: F+5000000000000000+0001 represents the floating point number 5. with a 16 character mantissa and a 4 character exponent. character data element: the data specifier A followed by a fixed length character string. The length is always 6. e.g.: ACL DAT represents the string 'CL DAT' 6-11 ICEM DDN Vl.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.7.2.1 Definitions 6.7.2.2 File header The file header serves three purposes: 1. Define the end of record character. 2. Define the formats of the record data for integer, floating point and character data. 3. Prevent backspacing from the first record. The file header consists of 11 characters: position(s) definition/purpose 1 2 3-4 5 6 7-8 9 10 11 value end of record character integer format specifier integer field length floating format specifier exponent field length mantissa field length character format specifier character field length end of record character range any character except I,F,A I 10 F 4 16 A 6 I 1-10 F 1-5 1-20 A 6 must be the same as pos 1 The standard file header record for CL file in the ICEM DDN environment: ;II0F416A6; 6.7.2.3 CL data record A CL data record is a concatenation of data elements spanning one or more lines of 130 characters or less and with the end of record character as the last character. A data element must be fully contained on one line. 6.7.2.4 End of file record The end of the file is indicated by a null record. A null record consists of a one character line, the end of line character. The standard end of file record for CL file in the ICEM DDN - ---------------------- --- - - - - - - - - - - - - ------------------- 6-12 ICEM DDN Vl.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.7.2.4 End of file record environment will then be: Note that the end of record character as the only data on a line does not necessarily constitute a null record. It could be the closing character of a record spanning one or more previous lines. 6.7.2.5 Example APT representation: PARTNO EXAMPLE OF A NEUTRAL CL DATA FILE FROM/O,O,O GOTO/5,5,5 FINI Neutral CL data file ( the line length is limited to 70 for the example ): ;II0F416A6; I 91 II 20001 1045A EXAMPALE OF AA NEUT ARAL CLADATA FAILE I 81 21 50001 3A I 0 F+OOOOOOOOOOOOOOOO+OOOOF+OOOOOOOOOOOOOOOO+OOOOF+OOOOOO0000000000+0000; I 81 31 50001 5A I 0 F+5000000000000000+0001F+5000000000000000+0001F+5000000000000000+0001; I 31 41 140001 0; 6.7.3 CL FILE STRUCTURE TheCL File consists of a sequential set of records. Each record is defined by a record class, a sub code and further instructions. The clqss groups similar types of records and is also called the record type. Listed below are the standard defined record formats: Wn WI word n of the current record record sequence number, refer to the physical formats for details . __._--------_._----_ .. - ------ 6-13 ICEM DDN Vl.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.7.3 CL FILE STRUCTURE Record Type 2000: WI W2 W3 W4 Post processor Commands record sequence number 2000 major word sub code (see postprocessor library, major word codes) minor word codes and/or parameters (see postprocessor library, minor word codes) Specific Formats: PPRINT, PARTNO, INSERT: W4... up to 66 characters of text, blank filled on the right ARCSLP: W3 = 1029 (Default) W4 = START W5 = s,slope W6 ENDARC W7 e,slope, W8 RADIUS, W9 = r, WI0 = CCLW or CLW Record Type'3000: Surface Data Circle records are the only surface data carried through into a CL file: WI W2 W3 W4 W5 W6 W7 W8 W9 WI0= Wll= W12= W13= W14= W15= record sequence number 3000 2 Surface Use Indicator (Drive Surface) 1 Surface Condition Indicator (TO) 4 Surface Type Indicator (CIRCLE) 9 Number of words in the canonical form Surface name (Blank) " 0 Surface name subscript xc yc Coordinates of the circle center zc i j Circle plane normal k r Circle radius Record Type 5000: Directions, Points and Parameters WI W2 W3 W4 W5 W6 W7 W8 W9 WIO= record sequence number 5000 = 4 GODLTA 3 FROM r r Point or Vector name (Blank) Name subscript 0 xp xv yp yv zv zp i i (id. ) (Mul tax only) J J 5 GOTO 6 Continuation xp (1) yp (1) zp (1) ip (1) jp (1) xp (n+l) yp (n+l) zp (n+l) ip (n+l) jp (n+l) (id. ) (id. ) 6-14 ICEM DDN Vl.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.7.3 CL FILE STRUCTURE Wll= k ... kp (1) k (Additional point coordinate sets for W3 W5 +n W6 +n W7 +n W8 +n W9 +n WI0+n k kp·(n+l) 5 or 6 only) xp(n) yp (n) zp (n) ip (n) jp (n) kp (n) (id. ) xp (2n) yp(2n) zp (2n) . ip (2n) jp (2n) (id. ) kp(2n) A maximum number of 240 reals is written out in a GOTO or Continuation record. Record Type 6000: ARELEM Flags, Specifications, and Parameters WI W2 W3 W5 record sequence number 6000 4 INTOL 5 OUTTOL t tolerance Record Type 9000: ARELEM WI W2 W3 W5 Parameters record sequence number 9000 2 MULTAX 0 OFF 1 ON And for an ISO standard CL file: WI W2 W3 W4 W5 record sequence number 9000 UNITS 9 171 MM 172 CM 173 INCH 174 FT n scaling factor or null Record Type 14000: Termination WI W2 W3 record sequence number 14000, FINI 0 ._---_.._.__ .... _.._-_ .... .._------_.-.. _. - - - - - 6-15 ICEM DDN Vl.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.8 IPARTD SAVE 6.8 IPARTD SAVE Following the Independent Save information on page 2-21 of the ICEM Design/Drafting Data Management manual, insert: "A maximum of 90 parts may be saved on a single IPARTD file. If you attempt to save more than 90 parts, the system will issue an error message and will not save the part onto' the IPARTD file." 6.9 IPARTD MODALS In order to provide increased flexibility in the IPARTD feature, menu 6.1.12 IPARTD MODALS has been added. This menu item currently contains one ne~ modal, the COMBINING VIEWS modal. The following documentation on IPARTD MODAlS should be inserted after page 2-25 of the ICEM Design/Drafting Data Management manual: 6.1.12 IPARTD MODALS With ICEM DDN Vl.65, there is a modal available for use 1n restoring IPARTD files. Additional modals may be added if necessary. The current modal setting is displayed to the right of the modal. ---IPARTD MODALS I.COMBINING VIEWS current modal setting Enter: 1 ] or [ - - _..._. __........_.... _--- To change the COMBINING VIEWS modal. To return to the PART MANAGEMENT menu. 6-16 ICEM DON Vl.65 Software Release Bulletin June, 1988 6.0 POST-I.62 ICEM MANUAL CHANGES 6.9 IPARTD MODALS If you select I.COMBINING VIEWS, the following menu will be displayed: ---COMBINING VIEWS I.COMBINE VIEWS WHEN RESTORING 2.00 NOT COMBINE VIEWS WHEN RESTORING Enter: 1 To combine views with identical view matrices when restoring parts from IPARTD. 2 To not combine views with identical view matrices when restoring. This is the system default. ] To return to the PART MANAGEMENT menu. To return to the IPARTD MOOALS menu. If you choose to combine views, an entity displayed in any of the combined views will be displayed in the resultant view. The view names of the eliminated views will be unavailable after they have been combined. Most users will not want their views combined. View combining was motivated by a very old IGES problem which has long since been resolved. 6.10 TAPE9 PLOT FILE OPTIMIZER With some plotters, especially pen plotters, it is desirable to optimize the graphics data on the plot file before plotting it on the device. The Plot Optimizer sorts the graphics data and removes duplicate, collinear, and zero-length lines, thus reducing pen motio~ and increasing plotter throughput. A number of parameters are available for controlling the level of optimization~ To execute command: the Plot File Optimizer, enter the following OPTIM[,param1] [,param2] [,param3] , ••. [,paramN] where 6-17 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.10 TAPE9 PLOT FILE OPTIMIZER I Input plot file. Default input plot file name is TAPE9. o Output plot file. Default output plot file name is TAPE9. ZERO Zero length vector optimization. Valid values are ON and OFF. The default is OFF. When ZERO=ON, the optimizer removes zero length vectors. DUP Duplicate vector optimization. Valid values are ON and OFF. The default is OFF. When DUP=ON, the optimizer removes duplicate vectors. COIN Coincident vector optimization. Valid values are ON and OFF. The default is OFF. When COIN=ON, the optimizer combines collinear and overlapping lines. Note that COIN=ON removes a larger set of plot file vectors, since it combines a group of vectors into a single vector. PC Pen change optimization. Valid values are ON and OFF. The default is OFF. When PC=ON, the optimizer reduces the number of pen change commands on the plot file. This option is useful when it is known that the target plotting device stores its pens in a carousel, making frequent pen changes costly. GRID Grid square optimization. Valid values are ON and OFF. The default is OFF. When GRID=ON, the optimizer places a grid over the plot to improve optimizer performance. Vectors are eliminated from the plot file based on the grid square which contains their endpoints. With GRID=OFF, the optimizer removes a larger set of vectors at the expense of more processing time. STATS Statistics option. Valid values are ON and OFF. The default is ·OFF. When STATS=ON, optimization statistics are written to the job's output file. This option provides information that the installer can use in determining appropriate settings for the ZERO, DUP, COIN, PC and'GRID parameters. It should be turned off for production runs. Depending on hardware and software factors involved in the plotting processes, adjustments to ZERO, DUP, COIN, PC, and GRID should be made, allowing for appropriate trade-offs between optimizer processing time and plotter throughput time. _ _.... .. __.__ ._._ _._--_.- ........ _ . _ - - ... 6-18 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.10 TAPE9 PLOT FILE OPTIMIZER Diagnostic messages are written to the file "OPTERR." 6.10.1 OPTIM RESTRICTIONS The program makes use of the temporary files 'ZZZZTXT,' 'ZZZZT9A,' and 'ZZZZT90,' so neither the input or the output file should have these names. 6.10.2 OPTIM ERROR MESSAGES CAN'T OPEN INTERNAL SCRATCH FILE. This message occurs during initialization when the scratch file is being opened. The usual cause is that the file already exists in an unknown format, or a system error. CAN'T OPEN PLOT FILE FOR READING. This message occurs during initialization when the input file is being opened. The usual cause is that the file does not exist. CAN'T OPEN PLOT FILE FOR WRITING. This message occurs when the output file is being opened. CHARACTER COUNT < O. This message occurs when a text command character count that is less than zero. is found with a CHARACTER COUNT EXCEEDS MAXIMUM. This message occurs when a text command is found with a character count that exceeds the maximum (currently limited to 200 by UNIPLOT). 6-19 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.10.2 OPTIM ERROR MESSAGES CHARACTER STRING TOO LONG. This message occurs when a text command is found with a character string that is longer than the maximum. This can only occur on NOS, since on NOS the string is stored in 6/12 format and the number of characters needed to represent an ASCII string may be up to twice as many as on an ASCII machine. COMMAND TYPE NOT SUPPORTED. This message occurs while the plot commands are being read from the input file. This message will appear if the input file contains commands other than move, draw, change pen, end-of-plot, end-of-file, or text commands. DUPLICATE VECTOR OPTION INVALID. This message occurs if the DUP parameter is other than OFF or ON. set to a value ERROR OCCURRED OPENING LIST FILE An error occurred trying to open the file which contains fatal error messages. ERROR OCCURRED READING PLOT FILE. This message occurs while the plot commands are being read from the input file. The usual cause is that the input fil~ is not formatted correctly. GRID OPTION INVALID. This message occurs other than OFF or ON. if the GRID parameter is set to a value INVALID PARAMETER. This message occurs when an unknown control card parameter keyword is passed to the optimizer. "."" _. -"._----"-" " ... " - - - - - 6-20 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.10.2 OPTIM ERROR MESSAGES KEYWORD = VALUE EXPECTED. This message occurs during initialization when any control card parameter information is passed to the optimizer using a form other than 'keyword=value'. PEN CHANGE OPTION INVALID. This message occurs other than OFF or ON. if the PC parameter is set to a value PLOT FILE VERSION NOT SUPPORTED. This message occurs during validation of the header. The usual cause is the header is missing. PLOT OPTIMIZER ABORT. plot file UNKNOWN CAUSE. Message is self-explanatory. PREMATURE END OF PLOT FILE. This message occurs while the plot commands are being read from the input file. The cause is that the end of input file is sensed before the end of plot file command is found. STATISTICS OPTION INVALID. This message occurs if the STATS parameter is set to a value other than OFF or ON. ZERO LENGTH VECTOR OPTION INVALID. This message occurs other than OFF or ON. · _ •• _ _ _ _ _ _ 0. _ _ _ _ _ _ if the ZERO parameter is set to a value 6-21 ICEM DON V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.11 INCREMENTAL POINTS ON ELLIPSES AND HYPERBOLAS 6.11 INCREMENTAL POINTS ON ELLIPSES AND HYPERBOLAS Following the text on page 1-22 of the ICEM Design/Drafting Basic Construction for NOS manual, add the following note: "If you desire evenly spaced incremental points along an ellipse or hyperbola, a Bezier Curve representation of the ellipse or hyperbola can be used. This is done by using F.15.2.7.1.4 CONVERSION to approximate the curve by a Bezier curve. (This function does not change the initial curve in any way.) Evenly spaced incremental points can then be placed along the Bezier curve." 6.12 MSTRNG STATEMENT IN GPL The following note should be added to page Design/Drafting GPL for NOS manual: 8-4 of the ICEM "Caution should be used when GPL programs which contain MSTRNG statements are initiated from a programmed tablet square. None of the tablet square commands following the GPL program name will be executed." 6.13 CHAIN SELECT TOLERANCE The following menu item should be added under MODALS on page 2-18 of the ICEM Design/Drafting Introduction and System Controls for NOS manual: 10.CHAIN SELECT TOLERANCE 0.001 to 0.000000001 inch The following note should be added to page 2-21 of the ICEM Design/Drafting Introduction and System Controls for NOS manual: "". ,,- _._-""""------,,." . " .. _.. " ... _.... __. , , - - - - - - - 6-22 ICEM DDN V1.65 Software Release Bulletin June, 1988 6.0 POST-1.62 ICEM MANUAL CHANGES 6.13 CHAIN SELECT TOLERANCE 10 If you select 10.CHAIN SELECT TOLERANCE from the Modals menu, you can set the tolerance that is used by chain select to identify contiguous entities. The system displays: CHAIN SELECT TOL = n.nnnn When the modal is selected, its current value is displayed. Enter the desired chain select tolerance. The default value is 0.001 inch (0.0254 millimeter). Valid input is between 0.001 inch (0.0254 mm) and 0.000000001 inch (0.000000025 mm). If invalid input is entered, an error message is output and the system reprompts you for a valid chain select tolerance. The following menu item should be added under DISPLAY SELECTION SYSTEM MODALS on page 3-29 of the ICEM Design/Drafting Introduction and System Controls for NOS manual: 11.CHAIN SELECT TOLERANCE 0.001 The following menu item should be added under CHAIN SELECT MODALS on page 3-30 of the ICEM Design/Drafting Introduction and System Controls for NOS manual: 4.CHAIN SELECT TOLERANCE 0.001 Enter 4 to change the chain select tolerance value The following note should be added to page 3-31 of the ICEM Design/Drafting Introduction and System Controls for NOS manual: If you select 4.CHAIN SELECT TOLERANCE from the Chain Select Modals menu, you can set the tolerance that is used by chain select to identify contiguous entities. The system displays: CHAIN SELECT TOL = n.nnnn When the modal is selected, its current value is displayed. Enter the desired chain select tolerance. The default value is 0.001 inch (0.0254 millimeter). Valid input is between O.OOl,inch (0.0254 mm) and 0.000000001 inch (0.000000025 mm). If invalid input is entered, an error message is output and the system reprompts you for a valid chain select tolerance. 6-23 ICEM DDN Vl.65 Software Release Bulletin June, 1988 6.0 POST-l.62 ICEM MANUAL CHANGES 6.14 TOLERANCE SPECIAL CHARACTER SYMBOLS FOR ANSI 6.14 TOLERANCE SPECIAL CHARACTER SYMBOLS FOR ANSI The following symbols should be added to Table I-Ion page 1-7 of the ICEM Design/Drafting Drafting Functions for NOS manual: Character Entry Symbol Symbol Name \+ \- + Plus for tolerancing Minus for tolerancing The following note should be added to page 1-94 of Design/Drafting Drafting Functions for NOS manual: the ICEM "ICEM DDN will always create tolerances from the tolerance menu so that the text will display as stacked. Text to be displayed nons tacked on a single line may be added with the modify text menu (16.13.6)." - - - - - - - - - . - . _ . _ . _..... __ .... _._._---_.. - 7-1 ICEM DDN V1.65 Software Release Bulletin June, 1988 7.0 NOS TAPE3 RESTORE UTILITY 7.1 INTRODUCTION This document describes how the NOS TAPE3 Restore Utility works. The program restores a damaged TAPE3 by reading the damaged parts and copying them off onto the file TAPE2. The part index and the first sector are reconstructed and updated. This utility is useful when the part file is truncated, the part index lost, or the first sector is overwritten. ICEMDDN will abort if the first sector is overwritten. If the part is truncated and/or the part index is lost, ICEMDDN will indicate that there are no parts, bad parts, or a bad index on the TAPE3. It is recommended that an experienced analyst work with such part files to determine the appropriateness of using the CONVT3 program, to help insure proper recovery of as many parts as possible, and to investigate the original cause of the problem. 7.2 APPLICABLE DOCUMENTS The format of the TAPE3 file is documented in V1.64 System Programmer's Reference Manual. the ICEM DDN 7.3 PROGRAM DESCRIPTION The program reads the damaged part file and looks for a correctly formatted first sector. If the first sector is incorrect, a new one is generated and the user is informed. The program then looks for part separators and copies each part and the first sector off to TAPE2. After the last part is found, the part index is generated and the first sector part length is updated. Inactive parts can also be found in the part file. Because the part index is 'the usual area of the part file to be lost, CONVT3 cannot tell dormant parts from active ones. Thus, more than one copy of a part can be recovered. In order to uniquely identify duplicate parts, a program-generated name is appended to the the front of these part names. The last 10 characters of the 70 character part name are dropped. This is necessary in order to guarantee that the part name is unique. - - - _ .........•- - - - - 7-2 ICEM DDN V1.65 Software Release Bulletin June, 1988 7.0 NOS TAPE3 RESTORE UTILITY 7.3 PROGRAM DESCRIPTION Each part will have the name "RESTORExxx" as the first characters of the part name. The xxx starts at 1 increases by 1 for each part on the file. ten and 7.4 INSTALLATION OF CONVT3 There are two ways that CONVT3 can be installed: 1. The program can be SYSEDITed into the operating system or built into the deadstart file so that the user simply enters "CONVT3" to execute it. 2. The program can be executed by entering the file name. by attaching the file and 7.S CONVT3 PROGRAM EXECUTION This program requires the damaged part file be local and named TAPE3. The program will generate a new part file named TAPE2. The damaged parts should be brought up with ICEMDDN to verify if they are correct. A run through part renew or part check is recommended. When a part file is damaged because of an unknown bug, hardware failure, or track limit, the parts on the part file can be harmed in any number of ways. Therefore, it is important to check the part to find what is damaged. It is possible that a bad part can cause the ICEMDDN product to abort. These parts should be deleted from the recovered part file. 7.6 NOTES AND CAUTIONS When CONVT3 program patterns are dropped. ---_._.__.-. __ . _ - _ . . ....•.. . .. - .. --............. - .. is run, -----.------ the UTF data __._._ _... _._ --_. .. and pre-Vl.60 ---- ... 7-3 ICEM DDN V1.65 Software Release Bulletin June, 1988 7.0 NOS TAPE3 RESTORE UTILITY 7.7 CONVT3 PROGRAM OUTPUT 7.7 CONVT3 PROGRAM OUTPUT The CONVT3 program lists the parts being processed as follows: PROCESSING = part name SHEET = sheet number part name SHEET = sheet number NUMBER OF PARTS = number of parts TAPE2 LENGTH = length of tape2 RESTORATION COMPLETE - RESTORED PARTS ON TAPE2 STOP RESTORATION COMPLETE The CONVT3 program is'sues the following error messages: Message Description and Error Handling EMPTY OR IMPROPERLY FORMATTED TAPE3 and/or NO PARTS FOUND - ABORT The file TAPE3 does not have a ICEMDDN first sector on it and no parts were found before the end of the record. READ ERROR - ABORT or WRITE ERROR - ABORT An unrecovered disk error occurred on a CONVT3 working file. FIRST SECTOR OF TAPE3 IS NOT CORRECTLY FORMATTED and FIRST SECTOR RECONSTRUCTED This is an informative message that the beginning of the part file was overwritten or an incorrect file was used as input to the CONVT3 program. The CONVT3 program will generate a new first sector on TAPE2 and continue scanning for parts. end •.. _.... _._--_... _ - - - - . - - - - _ . _ . _ ....__ .. __ _._-_._-_..... _ - - - - - - - - - .. ---------------_ ... _._._ ....... .-.. - ._-_ _._ •._-_._... __._ - CON T R 0 L .. ...__.•.... DAT A _----_ ....... _--_ ......... _. . _.-..... - - - - - _ . __ ._ ..----------- -.--- .. _..... _ . _ - - - - - . COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 06/27/88 6R285 2043520008 102716 PAGE 1 OF 2 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) SHIP TO SOLD TO ***************** * PACKING COpy * ***************** COMPUTER PERIPHERALS INC. ATTN: C.W. MARTOCELLO/VFDZON 2621 VAN BUREN AVE. NORRISTOWN, PA 19446 COMPUTER PERIPHERALS INC. ATTN: C.W. MARTOCELLO/VFDZON 2621 VAN BUREN AVE. NORRISTOWN, PA 19446 CUSTOMER P.O. TRANSMIT NO DEPT SALES REP ACCOUNT SUBMITTER SELLING OFFICE INSTALLING OFFICE FXX FXX PRODUCT NUMBER RELEASE LEVEL D830-122 688B SYSTEM TYPE SYSTEM SERIAL CY830 00618 DIVISION CODE PROJECT NUMBER FACILITY CODE VFDZON 0150/ PRODUCT NAME VER PROD QTY ICEM IGES TRNSLTR 223 1 COMPONENT NUMBER COMPONENT NAME VER COMP TY COMP UNIT TYPE MN QTY PRICE REL38A SMD131461 SMD131973 SMD131974 77987785 IGESV223 INSTALL BULLETIN INSTALL INSTR IGES URB INSTALL SURVEY 223 600 MEMO 223 MEMO 223 MEMO MEMO EXTND EXTND CP BACKPRICE QTY AV ORDER 0.00 0.00 0.00 0.00 0.00 1 1 1 1 1 ORDER PROCESSING CHARGE 0.00 5 PRODUCT CHARGE 0.00 H830-110 688A REL68 REL68C SMD131461 ICEM DESIGN/DRAFT ICEMDD ICEMGPL INSTALL BULLETIN FREIGHT 165 2400 165 600 1 1 1 1 1 165 0.00 0.00 0.00 0.00 0.00 S S S S S 1 1 S 1 0.00 0.00 1 S 1 0.00 0.00 *COMPONENT DUPLICATED IN THIS ORDER* SHIPPED FROM SMD 1227-7240 ROUTING- SURFACE AIR CONTROL DATA CORPORATION SOFTWARE MANUFACTURING AND DIST. 4201 N. LEXINGTON AVE. ARDEN HILLS, MINNESOTA 55126-6198 VIA NUMBER OF PIECES PACKED BY GROSS WEIGHT FREIGHT COST BILL OF LADING CON T R 0 L DAT A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER 'SCMA 06/27/88 6R285 2043520008 102716 PAGE 2 OF 2 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) PRODUCT NUMBER RELEASE LEVEL H830-110 688A PRODUCT NAME VER PROD QTY ICEM DESIGN/DRAFT 165 1 COMPONENT NUMBER COMPONENT NAME VER COMP TY COMP UNIT TYPE MN QTY PRICE SMD131838 SMD131839 77987785 ICEM DDN SRB INSTALL INSTR INSTALL SURVEY 165 MEMO 165 MEMO EXTND EXTND CP BACKPRICE QTY AV ORDER 0.00 1 S 1 0.00 0.00 0.00 1 S 1 *COMPONENT DUPLICATED IN THIS ORDER* ORDER PROCESSING CHARGE 0.00 PRODUCT CHARGE 0.00 TOTAL ORDER PROCESSING CHARGE 0.00 9 TOTAL PRODUCT CHARGE 0.00 2 TOTAL ORDER CHARGE 0.00 MISCELLANEOUS CONTENTS: 002 001 4 600 - 2400 - - -...... " .._....... . ._------ ... _.- ._ .. U.S. DOLLARS CON T R 0 L DA T A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 06/27/88 6R285 2043520008 102716 <~ PAGE 1 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) SHIP TO SOLD TO ***************** * PACKING COPY * ***************** COMPUTER PERIPHERALS INC. ATTN: C.W. MARTOCELLO/VFDZON 2621 VAN BUREN AVE. NORRISTOWN, PA 19446 COMPUTER PERIPHERALS INC. ATTN: C.W. MARTOCELLO/VFDZON 2621 VAN BUREN AVE. NORRISTOWN, PA 19446 CUSTOMER P.O. TRANSMIT NO DEPT SALES REP ACCOUNT SUBMITTER SELLING OFFICE INSTALLING OFFICE SYSTEM TYPE SYSTEM SERIAL FXX FXX CY830 00618 PRODUCT NUMBER RELEASE LEVEL D830-122 688B DIVISION CODE VFDZON 0150/ PRODUCT NAME VER ICEM IGES TRNSLTR 223 PROJECT NUMBER FACILITY CODE PROD QTY 1 COMPONENT NUMBER COMPONENT NAME VER COMP TY COMP UNIT TYPE MN QTY PRICE REL38A SMD131461 SMD131973 SMD131974 77987785 IGESV223 INSTALL BULLETIN INSTALL INSTR IGES URB INSTALL SURVEY 223 600 MEMO 223 MEMO 223 MEMO MEMO EXTND EXTND CP BACKPRICE QTY AV ORDER 0.00 0.00 0.00 0.00 0.00 1 1 1 1 1 ORDER PROCESSING CHARGE 0.00 5 PRODUCT CHARGE 0.00 H830-110 ICEM DESIGN/DRAFT 688A REL68 REL68C SMD131461 1 1 1 1 1 ICEMDD ICEMGPL INSTALL BULLETIN 165 2400 165 600 FREIGHT 165 0.00 0.00 0.00 0.00 0.00 S S S S S 1 1 S 0.00 1 0.00 1 S 1 0.00 0.00 *COMPONENT. DUPLICATED IN THIS ORDER* SHIPPED FROM SMD 1227-7240 ROUTING- SURFACE AIR CONTROL DATA CORPORATION SOFTWARE MANUFACTURING AND DIST. 4201 N. LEXINGTON AVE. ARDEN HILLS, MINNESOTA 55126-6198 VIA NUMBER OF PIECES PACKED BY GROSS WEIGHT FREIGHT COST BILL OF LADING - - - - _..........._._._.__ ._ .... _.._---_.... - CON T R 0 L ; DATE 06/27/88 DA T A COR P 0 RAT ION ASSEMBLY NO CORPORATE FILE NUMBER SCMA 6R285 2043520008 102716 PAGE 2 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) PRODUCT NUMBER RELEASE LEVEL H830-110 688A PRODUCT NAME VER PROD QTY ICEM DESIGN/DRAFT 165 1 COMPONENT NUMBER COMPONENT NAME VER COMP TY COMP UNIT TYPE MN QTY PRICE SMD131838 SMD131839 77987785 ICEM DDN SRB INSTALL INSTR INSTALL SURVEY 165 MEMO 165 MEMO EXTND EXTND CP BACKPRICE QTY AV ORDER 0.00 0.00 1 S 0.00 0.00 1 S *COMPONENT DUPLICATED IN THIS ORDER* 1 1 ORDER PROCESSING CHARGE 0.00 PRODUCT CHARGE 0.00 4 TOTAL ORDER PROCESSING CHARGE 0.00 9 TOTAL PRODUCT CHARGE 0.00 2 TOTAL ORDER CHARGE 0.00 U.S. DOLLARS MISCELLANEOUS CONTENTS: 002 001 - - - .. - - - ... , 600 - 2400 .......-... _-----_._._----_ .... _•. --'-'" - ...... .......... _ ...-.- ...... _ - - _.._....... . .... --- .... _--- - - - - - - - INSTALLATION BULLETIN INFORMATION (:.LO/21/t=37 ) **** **** IMPORTANT - PLEASE FOLLOW THE BELOW PROCEDURE 8EFORE INSTALLING THIS PRODUCT **** **** Control Data Corporation provides its customers with an on-line method of obtaining current infor~ation about its products. One of the on-line information sources is called an INSTALLATION BULLETIN. An Installation Bulletin can contain information helpful in installing and executing Control Data products. Before installing this product, please contact your local Control Data office or follow the below procedure to determine if an Installation Bulletin exists. 1. The on-line system resides in the Control Data Sunnyvale California facility. You will need a terminal and 300 or 1200 baud modem. Please dial: 2. When the computer system answers your call sound) , enter: (carriage return key) enter: (carriage return key) 3. The system will respond with: FAMILY: (a high pitched SMD131461 INSTALLATION BULLETIN INFORMATION Page 2 4. EntE?r: 5. The system will respond with: !I SOL'v/EF~, SOL 'v/EI:~ (carriage return key) O',jER ••• 6. Enter: 7. The system will respond with: Please enter your site code and password: Site Password (carriage return key) CDCC 1M, 9P2PI< 9. (carriage return key) The system will respond with the following menu: Your choices are: 1 Search PSR Data Base Retrieve Installation Bulletins Report a new problem or change an existing PSR to end this session BYE HELP i of you "'Jan t 119 I P Enter your main menu choice: 10. 2 Enter~: (carriage return key) 11. The system will respond with the below menu: Installation Bulletins are avail~ble for: .1 I CEM ~~ ICEIYJ 2.(>.(:) CARRIAGE RETURN for main menu En~er your IS choice: INSTALLATION BULLETIN INFORMATION Page 3 ..... 1':'·\ Enter: 1 (carl'- iage rf.:?tul'-n key) or 2 (carr- iage rooe·turn kE'Y) 13. The system will respond with the below menu: Rt:? I 8c::,se: I CEi"1 1 Display all Installation Bulletins 2 Display all Installation Bulletins entered or changed since a specified date 3 Display all new or changed IEs since your last 18 retrieve (YV/MM/DD) 4 Display topic index for this release CARRIAGE RETURN for previous menu Enter your IB choice: 14. Enter: 1 (carriage return key) 15. The system will respond by printing all Installation Bulletins for the ICEM products. The system will occasionally pause to allow the reading of a p~ge of text. To continue, enter the carriage return key. 16. Once the system has printed all Installation menu in step 11 above wi 11 appear-. . Ent.er' : Bulletin5~ the (carriage return key) 17. The system will respond with the menu in step 9 above. 18. Enter: BYE (carriage return key) 19. The system will then log you off. telephone call. You may now disconnect the end _.__ ._-----_ .._-_ . .- . - - - - .,.',.'---'---'. - - - - Control Data Corporation IGEM IGES TRANSLATOR Version 2.23 Operating System Level: NOS 2.5.3 Level 688 June 1988 Installation Instructions Disclaimer ICEM IGES should be installed only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Note Please contact the appropriate hotline if you have questions concerning installation. USA em Canada International 800 612 345-9903 851-4131 Control Data Corporation gives the user permission to reproduce this document. SMD131973 ._-_ _._--------_.._ - - - ... --_._._-------- Control Data Corporation ICEM IGES Translator Version 2.23 Installation Instructions 1 June 1988 " 1.0 DESCRIPTION ICEM IGES Translators allows the user to receive and/or transfer geometry-based information between non-CDC CAD/CAM systems and the ICEM system. ICEM IGES runs under NOS 2. 2.0 HARDWARE REQUIREMENTS ICEM IGES Translators requires the minimum hardware configuration for NOS. 3.0 RELEASE MATERIALS The IGES Translators are released on 9-track tape (VSN=REL38A). The following files are included: File File File File File File 4.0 1: 2: 3: 4: 5: 6: INSTALL IGPROC IGESICT IGESCIT IGESVER IGESLST the IGES installation procedure the IGES execution procedure file the IGES Postprocessor - IGES to IPARTD translator the IGES Preprocessor - IPARTD to IGES translator an IGES file - used for verification testing a translator list file - used for verification testing INSTALLATION PROCEDURE ICEM IGES is installed by executing the install procedure which is the first file on the IGES tape; the installation must be run interactively. It is recommended that ICEM IGES be installed on user number APPLLlB with a user index of 377774. The installation procedure creates the following files and makes them permanent on the installation catalog: Indirect-access file Direct-access files IGESICT IGESCIT IGPROC The installer must be sure that the permanent files do not exist with the same names as the files generated in the installation procedure. ----_. __ ......... _-------_._-_.. ....•._.. _----_. " Control Data Corporation ICEM IGES Translator Version 2.23 Installation Instructions • 2 June 1988 To install IGES on APPLLlB, enter the following commands from the System Console: X.DIS. SUI,377774. LABEL,TAPE,R,L=IGESV223,VSN=REL38A,F=I,D=PE. COPYBF,TAPE,INSTALL INSTALL. DROP. • To install IGES on a user number other than APPLLlB, log onto that user number using any terminal and enter the following commands: LABEL,TAPE,R,L=IGESV223,VSN=REL38A,F=I,D=PE. COPYBF,TAPE,INSTALL INSTALL,user_number. (user_number is the user number that you are logged onto.) Edit the file, IGPROC, to modify the default for the AUN parameter. Change the user number from APPLLlB to the NOS user number that the files actually reside in. 5.0 • A successful installation is indicated with the following message: "INSTALLATION COMPLETE; VERIFY GOOD". • An unsuccessful installation is indicated with the following message: "INSTALLATION ABORTED." VERIFICATION PROCEDURE The installation procedure performs a verification test to assure a correct installation ICEM IGES. The "INSTALLATION COMPLETE; VERIFY GOOD" message indicates that the ve~ification test was successful. No further verification testing is necessary . . .... _._--_ __ ....... ... -_.------ ... CONTROL DATA CORPORATION ICEM DDN VERSION 1.65 INSTALLATION INSTRUCTIONS NOS Operating System Level: NOS 2 Level 688 Date: 6/88 DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Control Data Corporation gives the user permission to reproduce this document. SMD131839 4197c I. Index Section I Release Description Page 1 Section II Tape Formats and Files Page 2 Section III Installation Instructions ICEM DDN Design/Drafting Package Page 4 ICEM DDN Advanced Design Package Page 5 ICEM DDN Numerical Control Package Page 6 Section IV lCEM DDN Verification Instructions Page 7 Section V Plotter Verification Page 7 9 APPENDICIES Appendix A International Drafting Standards Page Appendix B Terminal Set-up Procedures Page 11 Appendix C GPL and GTGT Execution Page 15 Appendix D Cyber 800 Tuning Guide for ICEM DDN Page 16 CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 688' I. 1 6/88 Release De$cription lCEM DDN is a computer-aided design and computer-aided manufacturing (CAD/CAM) system that runs under the NOS and NAM/IAP communications package. lCEM Design/Draftinq Packaqe The lCEM Design/Drafting file contains overlays for Basic Geometry, ANSI Mechanical Drafting, and Geometric Analysis. For International Drafting Standards, see Appendix A. ICEM Advanced Design Package The ICEM Advanced Design consists of all the overlays in the ICEM Design/Drafting plus additional overlays for Advanced Design. ICEM Numerical Control Package The leEM Numerical Control consists of all overlays in ICEM Design/Drafting and ICEM Advanced Design, plus additional overlays for Numerical Control. ICEM GPL ICEM GPL is a high level computer language designed to provide a user with features of the ICEM DDN product. The features are provided parametrically from within algorithms. The leEM GPL system within the standard programs must first interpreted by ICEM consists of two parts: an interpreter located ICEM DDN and a stand-alone compiler. Source GPL be compiled before those programs can be DDN. The lCEM GPL compiler is provided with the purchase of any portion of lCEM DDN (Design/Drafting, Advanced Design, or Numerical Control). Hardware Requirements lCEM DDI requires the minimum hardware configuration for NOS and NAM/IAP. A maximum field length of 170,300 octal is required for execution. The user station is a Tektronix 4014 or 4016 with Extended Graphics, Tektronix 4105, 4107, 4109, 4113, 4114, 4115, or 4125, lEW 790 with TEKEM and Control Data Corporation 721. - - - - - - , ... '-''''''-'-' ._--- ----- -------------- CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 68S' II. 2 6/88 Tape Formats and Files All tapes are nine-track made with a density of 1600 cpi (D=PE) • All tapes are ANSI-labeled and in INTERNAL format (LB=KL,F=I) • VSN=REL68 L=ICEMDD VSN=REL68A L=ICEMAn #1 #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #1 #2 #3 INSTALL lCEMDDN ,. DDNSRB ' DDNVER " DDWIT' DDNUTIL ~ OPTIM I VERUTIL' TAPE9 ICEMCLT' CONVT3 I VSN=REL68C L=ICEMGPL VSN=REL68B L=ICEMNC INSTALL ICEMAn COPYLDR #1 ' #2 #1 INSTALL #2 ICEMNC #3 COPYLDR #4 PPFULL 1#3 1#4 , #5 · #6 #7 #8 INSTALL GPL GTGT GOLIB PFX1660 PFX6016 XREC170 XTRX170 I Description of Files (I) Indirect Access File (D) Direct Access File COPYLDR' (I) is a copy utility used in the integration of the Advanced Design or Numerical Control overlays into ICEM DDN Design/Drafting. DDNSRB (D) is a text file containing the Software Release Bulletin. This document explains the new features and provides general information regarding this release. DDNUTIL (I) is the relocatable binary for the interface between ICEM DDN draw files and UNIPLOT/UNlPOST., DDNVER (I) is a CCL verification procedure file for the installation test of lCEM DDN. DDWIT (I) is a verification script input file for ICEM DDN. GOLIB (D) is the absolute binary for the ICEM GPL interface. GPL (D) is the absolute binary of the ICEM GPL Compiler. ----- - - - - - - _.• " . ,- . ---- -_.- ------- - ---- - -- - - - - - - -._-_.- --- CONTROL DATA CORPORATION lCEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 688· (D) GTGT * ICEMAn lCEMDDN ....•.•.... 6/88 is the GRAPL-to-GPL Translator. See Appendix C for info~tion on how to use this translator. is the module of Advanced Design overlays only. It is integrated into lCEMDDN upon the execution of the INSTALL Procedure on tape REL68A. is the absolute binary for lCEM DON zero overlay and the primary overlays. lCEMNC * is the module of Numerical Control overlays. It is integrated into lCEMDDN upon the execution of the INSTALL procedure on tape REL68B. INSTALL * is a CCL procedure to transfer the files on tape to disk under the user number under which the procedure is executed. The files are stored as either Direct (D) access files or as INDIRECT (I) access files depending on file size. All files are unloaded as PUBLIC, READ-ONLY files. OPTIM (0) Plot file Optimizer PFXl660 (0) is the absolute binary for translating CYl20 to CYl70 IPARTD part. files. PFX60l6 (0) is the absolute binary for translating CYl70 to CYl20 IPARTD part files. PPFULL (0) is a text file containing expounded PP word library. TAPE9 (I) is a verification data file for DDNUTIL and OPTIM. VERUTIL (I) is a CCL verification procedure file for the installation test of lCEM DDN plotter interface. XREC170 ('I) is an absolute binary needed for IPARTO file to file transferring when using HAMLET. XTRX170 (I) is an absolute binary needed for IPARTO file to file transferring when using HAMLET. PPFULL (I) Is a text file containing expanded PP word library. ICEMCLT (D) CLFlLE translator. CONVT3 (0) TAPE3 restore utility. * . (0) 3 These files are temporary files used during the execution of the INSTALL procedure • _ . ._ - - - - - - ---- - - --------------- CONTROL DATA CORPORATION ICEM DON INSTALLATION INSTRUCTIONS NOS 2 Level 688· 4 6/88 III. Installation Instructions Installation of lCEM DON Design/Drafting only Two tapes are needed to install the complete ICEM DDN Design/Dra~tinq package. They are REL68 and REL68C. The tapes can be installed on any user number, however, it is recommended they be installed on user number APPLLIB from the console. The instructions assume the tapes are being installed from the console. If not, begin at the LABEL command and disregard the DROP at the end. X.DIS SUI,377774. LABEL,TAPE,VSN=REL68,L=ICEMDD,D=PE,F=I,NT. BEGIN, , TAPE. DROP. Informational notes are displayed on the screen during the installation. The INSTALL procedure for REL68 will prompt the user when REL68C needs to be mounted on the tape drive. See Section IV for lCEM DDN Verification instructions. See Section V for lCEM DDN Plotter Interface Verification. See Appendix D, Section 3.2 for comments concerning having ICEM DDN as system resident. CONTROL DATA CORPORATION ICEM DON INSTALLATION INSTRUCTIONS NOS 2 Level 688· 5 6/88 Installation of ICEM DON Advanced Design and Design/Drafting Three tapes are needed to install the ICEM DON Advanced Design package. They are REL68, REL68A and REL68C. The tapes can be installed on any user number, however, it is recommended they be installed on user number APPLLIB from the console. If not, begin at the LABEL command and disregard the DROP at the end. X.DIS SUI,377774. LABEL,TAPE,VSN=REL68A,L=ICEMAD,D=PE,F=I,NT. BEGIN, , TAPE. DROP. Informational messages are displayed on the screen as necessary. The INSTALL procedure for REL68A will prompt the user when REL68 and REL68C need to be mounted on the tape drive. See Section IV for ICEM DON Verification instructions. See Section V for ICEM DON Plotter Interface Verification. See Appendix 0, Section 3.2 for comments concerning having ICEM DON as system resident. - - - _ .._. - ----,..- . _ - - - - - , - - "......_" .. .._,_._,---, CONTROL DATA CORPORATION ICEM DON INSTALLATION INSTRUCTIONS NOS 2 Level 688' 6 6/88 Installation of ICEM DON Numerical Control, Advanced Design and Design/Drafting Four tapes are needed to install the ICEM DON Numerical Control package. They are REL68, REL68A, REL68B and REL68C. The tapes can be installed on any user number, however, it is recommended they be installed on user number APPLLIB from the console. The instructions assume the tapes are being installed from the console. If not, begin at the LABEL command and disregard the DROP at the end. X.DIS SUI,377774. LABEL,TAPE,VSN=REL68B,L=ICEMNC,D=PE,F=I,NT. BEGIN, , TAPE. DROP. messages are displayed on the screen as. necessary. The INSTALL procedure for REL68B will prompt the user when REL68A, REL68C, and REL68 need to be mounted on the tape drive. Info~tional See Section IV for ICEM DDN Verification instructions. See Section V for ICEM DON Plotter Interface Verification. See Appendix D, Section 3.2 for comments concerning having ICEM DON as system resident. CONTROL DATA CORPORATION ICEM DON INSTALLATION INSTRUCTIONS NOS 2 Level 688 . IV. 7 6/88 Verification of the ICEM DON (all packages) Log into NQS using one of the valid terminal types. Valid terminal types and set-up information can be found in APPENDIX B. In the instructions below, the use of 'username' should be replaced with the user number where the files were installed. The use of 'baudrate' should be replaced by the first digit of the baud rate of the communications line. For example, 3 is the baud rate of 300, 1 is the baud rate of 1200, etc. The use of 'te~inal type' should be replaced by the user's type of te~inal. The default is T4014. The terminal type specified must be one of the valid terminal types listed on page 3. GET ,DDNVER/UN=' username' • DDNVER,'baudrate','username', 'terminal type'. the request for input. It is being supplied by the verification input file. The output is emulating a Tektronix 4014 terminal. The result should match the display in figure ICEM DON-I. Ign~re V. Verification of the ICEM DON Plotter Interface Log into NOS using one of the valid terminal types. Valid terminal types and set-up information can be found in APPENDIX B. In the instructions below, the use of 'username' should be replaced with the user number where the files were installed and where UNIPLOT/UNIPOST files reside. It is assumed ICEM DON plotter interfacer files are inst'alled on the same user number as UNIPLOT/UNIPOST. GET, VERUTIL/UN=' username' • VERUTIL,'username'. The procedure VERUTIL executes UNIPOST. following manner. AUTOMATIC HARDCOPy (Y/N) ? 2 •.. 4. 6. 4010 ASYNCHRONOUS 4014 ASYNCHRONOUS 4014 EGM ASYNCHRONOUS ENTER BAUD RATE UNIPOST will prompt you in the Specify Y if a hardcopy is desire~ and is available; specify N if not. Specify 6 as Tektronix terminal type. Enter the baud rate of the communication line (example 1200, 9600, etc ). ? The screen will display the CDC logo (ICEM DON-I). When the logo is drawn, crosshairs will appear. Press any key (A through Z) and the screen will clear and return you to NOS • . NOTE: Refer to the UNIPLOT Reference for additional information • .. .... .... - ._._'..".'_._-"--_.- - .. ----- -.--- - - .. Manua~ CONTROL DATA CORPORATION ICEM DON INSTALLATION INSTRUCTIONS NOS 2 Level 688- . 8 6/88 CONTROL DATA leEM DON FIGURE IeEM DDN - 1 CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 688 . 9 6/88 APPENDIX A INSTALLATION INSTRUCTIONS International Drafting Standards o Drafting Standard (DIN) library and installation instructions are available by contacting the Control Data CAE software development manager in Frankfurt, Germany. Ger.man - o French Drafting Standard library is unavailable. Questions may be answered by the Control Data CAE software development manager, Paris. - o Control Data France 27 Cours Des Petites Ecuries B.P. 139 77315 Marne LaVallee, Cedex 2 France . British Drafting Standard library is unavailable. Questions may be answered by the Control Data design/drafting analyst in London. - o Control Data GMBH Stresemannallee 30 6000 Frankfurt Main 70 West Germany Control Data Limited Control Data House 179-199 Shaftesbury Avenue London WC2H SAX Swedish Drafting Standard library and installa!ion instructions are available by contacting the design/drafting analyst in Goteborg, Sweden. - -Control CAD/CAM Box 10, S-40120 Sweden - - _ ..... _-_._- . Data AB Applications Baldersgatan 4 Gothenburg ........ _._... - ...._ - - - _ .._... _-- - - - - - - - - - _ .__._ ..... _..._.._._ .._--- CONTROL DATA CORPORATION ICEK DDN INSTALLATION INSTRUCTIONS NOS 2 Level 688' o Japanese Drafting Standard library and installation instructions are available by contacting the design/drafting analyst in Tokyo, Japan. - o Control Data Japan, LTD. Sunshine Bldg., 27th F. 1-1 Higashi-Ikebukuro 3-Chome Toshima-Ku Tokyo 170, Japan Chinese Drafting Standard Library and installation instructions are available by contacting the design/drafting analyst in Tokyo, Japan. - Control Data Japan, LTD. Sunshine Bldg., 27th F. 1-1 Higashi-Ikebukuro 3-Chome Toshima-Ku Tokyo 170, Japan 10· 6/88 CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 688' 11 6/88 APPENDIX B TERMINAL SET UP PROCEDURES The te~inal used for the installation of ICEM DDN must be initialized. Instructions for initializing the 4014, 4016, 4105, 4107, 4109, 4113, 4114, 4115, and 4125 Tektronix te~inals follow. Please refer to IEW790 with TEKEM manuals for 790 terminal initialization. TEKTRONIX 4014 and 4016 TERMINALS. 1. The following installation. a. b. c. d. te~inal strapping options are for initial terminal ECHO - ON GIN terminators - CR only CR effect - CR LF effect - LF 2. Turn the terminal power on. The 4014 POWER switch is on the front lower right corner of the pedestal stand. The 4016 POWER switch is located on the right side of the terminal head. The green POWER indicator, located on the keyboard, will light when power is switched on. 3. Allow the terminal to warm up. Warm up is complete when pressing the RESET PAGE key completely clears the screen. 4. Set the ASCII/ALT switch to the ASCII position. • 5. Initialize the OPTION •1 or OPTION 20 according to the procedure below, as applicable. ,6. To obtain the small character size, set the terminal to LOCAL mode. Press. the ESC key and the; (semicolon) key together and return to LINE mode. 7. Dial the appropriate telephone number, if applicable. 8. Press the RETURN key to obtain the login FAMILY message • . _.- - - - - - - - _ . CONTROL DATA CORPORATION ICEM DON INSTALLATION INSTRUCTIONS NOS 2 Level 688' 12 6/88 OPTION 1 INITIALIZATION 1. Select the appropriate baud rate switch setting using the BAUD RATE switch located at the rear of the pedestal stand. 2. Set the HALF I FULL DUPLEX switch to FULL. 3. Set the INTF/OFF/AUX switch to INTF. 4. Set the TTY LOCK key. OPTION 20 INSTALLATION - - NOTE - If the terminal is equipped with both the OPTION 1 and the OPTION 20, set the INTF/OFF/AUX switch of the OPTION 1 to OFF. (Asynchronous lines only). Place the terminal in LOCAL mode. Press the SHIFT key and the CNTL key together. While both the SHIFT and CNTL keys are depressed, press and release the RESET key; then press the P key and release all keys. Place the terminal in LINE mode. Set the CODE EXPANDER switch to OFF. TEKTRONIX 4105, 4107, 4113, 4114, 4115 and 4125 TERMINALS Complete the following to set up the Tektronix 4113, 4114, 4115 or 4125 terminal. 1. Tum the terminal power on by pushing the POWER button. 2. Allow the terminal to initialize (some keys on the keyboard remain lit until the terminal has completed its initialization). 3. Press the SET UP key so the terminal operating modes can be changed at the keyboard. An asterisk (*) should appear to the left of the cursor • . 00_- __ .___ .. ____ oo _ _ _ •• _. _ _ _ _ _ _ _ _ _ _• _ _ _ • _ _ _ _ _ _ _ _ _ __ CONTROL DATA CORPORATION Iem! DDN INSTALLATION INSTRUCTIONS NOS 2 Level 688· 4. 13 6/88 Enter: STA to display the released terminal status settings. 5. Ensure the terminal has the following settings. The remaining Tektronix 4105, 4107, 4109, 4113, 4114, 4115, and 4125 terminal status settings will either be set by ICEM DON or will not affect the operation of ICEM DON. To change a setting, reenter the new setting. Status 4105, 4107, 4109 4113, 4114, 4115, 4125 TBSTATUS emulation only Not Applicable Out for 4014 TBHEADER CHARS Not Applicable Out for 4014 140 140 Yes Yes LOCK KEYBOARD No No SNOOPY No No BAUDRATE Applicable Baud Rate Applicable Baud Rate FLAGGING INPUT EOLSTRIbG Not Applicable Not Applicable BLOCRMOOE No No (4113 only) 100 100 emulation only RLINE LENGTH • INPUT CONTROL DATA CORPORATION ICEM DON INSTALLATION INSTRUCTIONS NOS 2 Level 688' 14 6/88 Status. 4105, 4107, 4109 4113, 4114, 4115, 4125 QUEUESIZE 8100 8100 DUPLEX Not Applicable Full (4113 only) XMTDELAY 0 O· XMTLIMIT Applicable Baud Rate Applicable Baud Rate Without Echoplex NL NL With Echoplex LF LF BYPASS CANCEL • -- - - - - - - _ _ _ _ _ _ _ ._. _ _ _ _ - _ _ _ _ ow ___ • _ _ _ _ _ _ _ _ __ --- - - - - - - - - -- - - - - - ----------- CONTROL DATA CORPORATION ICEM DON INSTALLATION INSTRUCTIONS NOS 2 Level 68S· 15 6/88 APPENDIX C Using the GPL Compiler into NOS using one of the valid terminal types. Valid terminal types and set-up information can be found in APPENDIX B. In the instructions below, the use of 'username' should be replaced with the user number where the files were installed. In addition, 'source program' should be replaced by the file name of your GPL program; 'grapl program' should be replaced by your translated GRAPL program file name; 'output file name' should be replaced by our output file name (default is OUTPUT); 'list file name' should be replaced by the file name you wish the translated program to be put on. Log To create a new GPL object library: ATTACH,GPL/UN='username'. GET, 'source program'. GPL,I='source program',L=GPLLIST. DEFlNE,GPLLIB. LIBEDIT,B=GPLOBJ,P=GPLLIB,C,Z.I*BUILD GPLD. REWIND,*. To add additional compiled programs to an existing GPL object library: ATTACH,GPL/UN='username'. GET, 'source program'. GPL,I='source program',L=GPLLIST. ATTACH,GPLLIB/M=W. LIBEDIT,B=GPLOBJ,P=GPLLIB,C,Z.I*BUILD GPLD. REWIND,·. • Using the GRAPL to GPL Translator GTGT Example: ATTACH,GTGT IUN=' username ' GEr, 'grapl program' GTGT,I='grapl program',O='output file',L='list file' -NarETHE TRANSLATION IS NOT ALWAYS 100%. FOR REMARKS IN THE GPL SOURCE OUTPUT. (For more information, see Appendix F of the ICEM GPL Reference Manual. ) CHECK ......... - ................ - ...•. __ . _ - - - - - - - - - - - - - - - - - - - - - - - - - - _ . .. CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 68S' 16 6/88 APPENDIX D CYBER 800 TUNING GUIDE FOR ICEM DDN 1 800 Tuning Guide for IeEM DON 6/Se Table of Contents 1.0 INTRODUCTION: • • • • • 1.1 BACKGROUND - PROBLEMS. 1-1 1-1 2.0 OVERVIEW OF 800'S • 2.1 800 FEATURES 2.2 800 MEMORY USE •• 2-1 2-1 2-2 3 • 0 TUN ING METHODS 3.1 STEPS FOR TUNING 3.2 DON SYSTEM RESIDENT •••• 3.3 DON OVERLAYS IN CENTRAL KEMORY • • • • 3.4 CPU BOUND 800 • • • • • • • • • • 3.5 CPO READING • • • • • • • • •• .•• J. • 3.5.1 SYSTEM PARAMETERS AND EST CONFIGURATION. 3.5.2 SYSTEM CONTROL INFORMATION • • • • • ••• 3.5.3 INTERVAL SAMPLE • • • • • • • • 3.6 PROBE • ~ .. • • • • • • • • • • • 3.7 CONSOLE WATCHING • • • • • • • • 3-1 3-1 3-2 3-2 3-4 3-4 3-5 3-5 3-6 3-7 3-7 4.0 PERMANENT/TEMP FILE ALLOCATION 4-1 5.0 EDL TUNING 5-1 6.0 CONCLUSION 6-1 7.0 APPENDIX " ••• 7-1 ... 1-1 800 Tuning Guide for ICEK DON o/tsti -------------------------------------------------------------------1.0 INTRODUCTION: 1.0 INTRODUCTION: 1.1 BACKGROUND - PROBLEMS This guide will explore possible solutions to some common tuning situations. of the The main problem is that users are expecting to set-up and play the hardware/software with no adjustments. This practice causes the site to run with the default setup parameters wh~ch were built for a small job environment. DDN is usually overlay bound and has a rather large field length. Depending on the disk configuration, the site is usually disk bound due to overlay "loading and swapping DON to disk. In the cases where the site has a lot of memory, the memory is not being utilized because no one has designated it as a "DE" equipment for DDN overlays and/or a swap device. Because system analysts don't have a quantitative method of ascertaining what tuning functions cause improvements, tuning is not attempted. By using'CPD, CTIME, RTlME, and ICEM DON trace files, an objective index of performance can be obtained and improvements made. 2-1- 800 Tuning Guide for leEK DDN 6/88 ------------------------------------------------------------------~ 2.0 OVERVIEW OF 800'S -------------------------------------------------------------------2.0 OVERVIEW OF-800'S 2.1 800 FEATURES The 800 has the following feature.: * The 800 has a high .peed central proce.sing unit that run. with a memory that can be very large - 2 to 128 megabyte. (262 thousand to 16 Killion central memory word.). * The cache memory speed. up effective memory cycle. * * Peripheral processor. operate at 4 time. the original PPU speed. * J The 800 microcoded instruction set allows both NOS and NOS/vE operating systems to exist and run in the same machine (dual state) •. The range of ability for each machine has more than one dimension. As you go up the line in CPU power, the memory size can also be upgraded. The following chart shows the different models and the allowed memory size option. and multiple CPU option: MODEL 810 810A 815 825 830 830A 835 840 845 850 855 860 870 990 990E 995E MEMORY SIZE OPTION (Megabyte.) 2 4 8 12 16 32 64 96 128 -X -X XX X X X X X X X X X X X X X X X X X .: X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Dual CPU NO NO NO NO YES YES NO NO NO NO YES YES YES YES NO YES 2-2 800 Tuning Gu~~e for leEK DON 6/88 2.0 OVERVIEW OF 800'5 2. 1 800 FEATURES The 840A; 8S0A, 860A and 870A have an I/O 20 PPUs and 24 channels •. subsystem of In dual state only one processor can be executing in the CYBER 170 mode. Currently 16 megabytes is the maximum memory that use. NOS can It is the meaory expansion characteristic that is most interesting for large applications like DON. It has been observed that customers are overlooking the ability of the 800 to use this me.ory in many different ways. 2.2 800 MEMORY USE The 800 memory can be used in the following ways: (1) Job area - the job execution area is normally about 262K but can be bigger or smaller. Don't allocate more job area than it is possible to use (i.e. job area <- number of control points x max job length). (2) 5wap area - Rather than roll the job to disk, it can be swapped from me.ory to .e.ory to avoid the disk accesses. (3) System resident - specific overlays and/or PPU programs can be stored and retrieved from memory to avoid disk·accesses. (4) Buffer area for buffered disks. (5) NOS/VE execution area. All the above a ••ory allocations are controlled. by deadstart parametera in the CKR, EQPD, and IPRD decks. The EQPDxx entry for UEK is - ttEQ005-DE,ST-ON,ET-EK,5Z-4000." (1 million words of UEM). The IPRDxx entry for the .econdary rollout threshold is - "5RST-2000" ( The maximum of 200,000 job field length will be rolled to the .econdary rollout). 3-1 800 Tuning Guide for IeEM DON 6/88 -----------------------------------------~-------------------------- 3.0 TUNING METHODS -------------------------------------------------------------------3.0 TUNING METHODS 3.1 STEPS FOR TUNING The following is a summary of the steps one can go through tune 800s for ICEM DDN: to 1) Run CPO - Find what the bottlenecks are. Tune by making NOS 90nfiguration chang.s such as system resident and channel/disk configuration (see section 3.5). Check disk use percentages from the CPD run. 50-60% is pretty high. Moving overlays to CM or UEM and/or allowing ICEM DDN to run as system resident will help speed up the product and decrease disk access. Also, try to arrange your configuration so that equal access is occurring across all disk channels. Avoid channel 0 because'it cannot be alternated in each mass storage device Equipment Status Table (EST) entry. 2) Run ICEM DON with the T option on and collect overlay load numbers (CT file) for a given script. The IT file, resulting from the T option run is used for input (I-lfn) so that the run can be repeated for comparison after each tuning attempt (base timing). A program included in the appendix counts and sorts the counts by overlay for each overlay that was loaded during the script execution. 3) Based on CPO and the CT counts, move selected overlays into CM (Central Memory) and/or UEM (Unified Extended Memory). In level 630 of NOS a limited number of overlays can be put in CM, and near 400K the sYlt .. hanas. The work around is to put additional overlays "in UEK. At this level of the system, there does not leem to be any perforaance difference between overlay loading from CM or t1EK. 4) Recheck re.pon•• ti.e by running a script in a quiet system with CTIHE and RTlHE control card. on each side of the ICEM DON call. The.e numbers will tell you the amount of CPU time and real time used to make the run. Also, rerun CPO to check what is happening to the syste. resource.. There is a Timesharing Instrumentation Package which .easures °response time, think time and transaction rates of lAP (LOS Publication number 15190016). This package will show how tunina hal affected response time. 3-2 800 Tuning Guide for ICEK DON 6/88 -----------~----------------~--------------------------------------- 3.0 TUNING METHODS 3.2 DON SYSTEM RESIDENT 3.2 DDN SYSTEM RESIDENT The advantage of having DON system resident is that when it is in the system, more than one copy of the code is available from multiple disk channels. Also, selected overlays can be resident in Qt. Don't bother aoving ICEM DDN to the system if you have only one channel to disk .and you don't want to move over.lays to CM or UEK. Also, remember that ICEM DDN will increase your system file by about lOOK PRUs on each device that is designated as a system device. On small capacity disk systems put ICEM DON on the deadstart tape rather than on a permanent file which is SYSEDITed after deadstart. This will save lOOK PRUs of permanent file space. GPL overlays must be on a local file at execution time for GPL users. It currently does not run any other way. Make an entry in the·LIBDxx deck of "*FL ABS/ICEMDDN-6560" so that it will execute from the system. file. 3 • 3 DDN OVERLAYS IN CENTRAL MEMORY The proble. with NOS 800 performance is caused by DON having to load overlays from the disk. Generally, if the most frequently called overlays can reside in memory, the disk accesses will be much lower. If all the overlays that are called are put in memory, a script will run as well as it would on NOS/VE (virtual environment). Of course, the data caching VQD't be •• good a. VE but the performance should be considerably better than before the overlays were put in CM. 3-3 800 Tuning Guide for leEK DON 6/88 ----------------~--------------------------------------------------- l.O TUNING METHODS 3.3 DON OVERLAYS IN CENTRAL MEMORY -------------------------------------------------------------------Following is an example of the performance improvement on an 855 with the overlays in CM and other numbers showing relative performance: SYSTEM ------ Running time CPU time Comment ------- ------------ --------13 12 48 78 DDN1S3 on 844s (System file) ODNISl on FHO's 830 NOS/VE 810 NOS/VE 374 18 78 138 760 NOS 760 NOS 371 291 7 7 DDN1S7 on 844s (System file) DDN1S7 on FHOs (Local file) 8SS NOS 267 160 9 9 DDN1S7 on Disk (System file) 3 overlays in CM+System file 760 NOS 8SS NOS/VE ass NOS " It " " " " The 100 second improvement for the 8SS NOS is caused by reducing disk accesses. In theory, if all the overlays that are called are put in memory, the script would run as well as the 8SS NOS/VE (18 seconds). Also, notice the CPU time for each of the above machines. The CPU time requirement for DONIS7 is less than DON1S3. The 830 and 810 is 4 and 6 times 1esl capable than the 760 or 8SS. If the site is CPU bound, the moving of the overlays into memory may not help response time during periodl of CPU saturation. The following table typical script: Overlay·' ------CL04 CLS2 CL02 CL72 CL270 CL7S CLSI CL14 CLS4 * Load Count --------- summarizes the overlay situation with a Field Length of Overlay* ----------------------- 276 247 136 Sl040 13S 23066 44031 60042 97 88 "62 S6 48 S2SS1 4321S S4S13 41300 30441 Field length and sum are in octal. Accumulated Sum* --------------S4K 126K 171K 21SK 261K 340K 41SK 4S7K S07K 3-4 800 Tuning .Guide for ICEK DON 6/88 --~----------------------------------------------------------------- 3.0 TUNING METHODS 3.3 DON OVERLAYS IN CENTRAL MEMORY These 9 overlays were loaded 1145 times. There were overlay loads in all with a total of 32 overlays used. 1442 After the 4th or 5th most frequently loaded overlay, the payoff from having the overlay in Central Memory (CM) goes down. The rest of the CM can be used for swap area. Both of these uses take away some CPU usage that would be normally available to user programs. But because most sites are disk bound, the swapping and overlay loading from memory to memory saves on disk access and speeds up the user response time. If CPO runs and RTlME and CTlME control cards are used around a script run before and after these tuning suggestions, the effect can be measured. With less disk access the product (ICEM DON) will speed up and will make more use of the CPU so that swapping and overlay loading will occur faster. This can have a secondary effect of causing more CPU utilization due to more jobs (through CPU swapping) having access to the CPU and less disk access due to overlay loading from memory to memory loading. This secondary effect may necessitate a reduction in the the job switch delay so that the CPU is shared better between competing jobs. In any case, the above tuning should have a positiv~ effect on response time for the average ICEK DON user. 3.4 CPU BOUND 800 If your site is CPU bound (95-99%) , the moving of the overlays to Central Memory may cause the individual ICEM user to run a lot faster but when a large terminal load is present the total throughput may decrease. You may take steps to decrease the CPU usage to optimize. Because the CPU is used to move ~verlays around in memory, the moving of overlays to disk may d.creas. CPU usage. This will slow down the terminal respon•• for the user at light loaded times but should make the u•• r at CPU bound times run better. This situation seems to be rath.r rare and i. found only on the 825. and lower machine.. In determining if your site is CPU bound don't be mislead by maintenance job. or batch jobs which loak up the CPU when the time-sharing jobs are not running. 3.5 CPO READING CPO or TRACER (NOS System Maintenance Reference Manual 60459300) and PROBE are uled for statistical analysis of your 3-5 800 Tuning Guide for leEM DON 6/88 -------------------------------------------------------------------3.0 TUNING METHODS 3.5 CPO READING system performance. The data is used to determine areas where problems occur, where improvements in design and system tuning can be .ade. These products work by periodically gathering data about the system and writing the data to a file. TRACER is . .de up of 4 programs: 1) ICPD - Starts up CPO PPU program 2) CPD - CPD is a dedicated PPU program which monitors system activity. Data i. written to.a direct access permanent file for future"analysis. 3) ACPD - A post-processor program which generates an output report from the direct access permanent file written by CPD. See the NOS'Maintenance manual (60459300) for details of calling parameters for TRACER. The following sequence will start and complete TRACER operation: 1) ICPD.pll.p2, ••• pn. (starts CPO up) 2) ENDCPD. (ends CPO data gathering) 3) ACPD.pll.p2 •••• pn. (processes the CPO data and generates a report) The ACPD report is in three sections 1. 2. 3. Systea para.eters and EST configuration. Systea Control Information. Interval Samples. 3.5.1 SYST55'PARAKETERS AND EST CONFIGURATION The Systea Parameters relate such things as the start date and ti•• ~- report interval, memory size, UEM, number of PPUs and varioua 1eDIths of software- tables. The EST table is dumped .~ the channel and disk connections. 3.5.2 SYSIEB CONTROL INFORMATION The System COntrol Information relates what the priority is for each ]0. elass. The BC, TS, and 01 classes are especially importaat to good system response. The Be and 01 should have a lover n (au priority) ,than the TS class. This will allow time-shar~ to always get the CPU before BC or DI can get it. ------------------- ---------..- , -------------,._, 3-6 800 Tuning Guide for ICEK DDN 6/88 -------------------------------------------------------------------3.0 TUNING METHODS 3.5.2 SYSTEM CONTROL INFORMATION -------------------------------------------------------------------The other important parameters are the UP (upper priority limit) and LP (lower priority limit). These parameters are set based on how often batch jobs are rolled in and out without ever getting executed. If there is usually a lot of CH available, the UP and LP can be lower for batch and detached jobs than for time-sharing jobs. These parameters control the rolling out of batch or detached jobs when a time-sharing job requests more memory than what is currently available. If the execution memory is small in comparison to the field length requests, the batch and detached jobs should have the same UP and LP so that jobs are not rolled in and out without doing any work. The NJ parameter can help this situation. By controlling the number of batch jobs that can execute at the same time, the" batch field length can be controlled •. The NJ parameter for time-sharing controls the number of users' allowed. The FL and AM parameters for each job class" can be designated to limit by job and/or job class how much Field Length (FL) m.y be used and when to schedule the job to CH. These parameters can be used to partition the memory by job class and run specific jobs at a selected time of the day. The CH parameter controls how long the UP priorities are in "effect. With fa.ter CPUs a sort duration 4-5 seconds is desired so that users that are running batch jobs in time-sharing mode are dropped down to the batch priority (assuming that batch priority is the same as the time-sharing lower bound priority). Thus, short duration time-sharing tasks will get the most attention. 3.5.3 INTERVAL SAMPLE The followinl table .hows .ome of the parameters and what action ai,ht be taken to improve performance when a high percenta,e of u.e i. shown: Parameter -(hiah percentage) PPUS ACTIVE NO PPU AVAILABLE CHANNEL ACTIVE CPU USAGE IDLE SYSTEM Cau.e/Information Not enough Di.k Channels or PPUs. Same as PPUS ACTIVE. 50-60+ up mean. that more di.k channel. will improve response time. High idle percent mean. the CPU is not being used could be cau.ed by the system being di.k bound. System Software u.ing exce •• ive CPU. 3-7 800 Tuning Guide for ICEM DON 6/88 -------------------------------------------------------------------3.0 TUNING METHODS 3.5.3 INTERVAL SAMPLE -------------------------------------------------------------------SUB-SYS SYS ORG USER FL AVAILABLE IAF USERS TRACKS AVAILABLE Same as SYSTEM. Same as SYSTEM. You are ·getting as much as you can out of the system. Application CPU usage may be excessive. Large percent is good - lots of room to run jobs. If coupled with secondary rollout filling up, FL needs to be moved to the secondary rollout area. Number of users. When a device has only 10% of it. tracks available the system automatically does not use this device for TEMP files. TOTAL ROLLOUTS SECONDARY ROLLOUTS TOTAL SECTORS ROLLED SECONDARY SECTORS ROLLED INSUFFICIENT CM NO CONTROL POINT The statistics on total and secondary rollouts will tell you if your secondary rollout threshold is large enough and how much your secondary rollout device is being used. Number of times no CM was available to bring in a job. This number will tell you if you have enough control points defined. 3.6 PROBE 1) 2) 3) 4) 5) The PROBE utility measures the following: The number of times a PP routine was loaded. The number of CIO RA+l requests by function number. The number of PP requests to CPUKTR by function number. The number of KTR requests to CPUKTR by function n~mber. The stati.tical data accuaulated in low central memory - includes such items as number of sectors rolled and number of rollouts. PROBE data gathering is enabled at deadstart time by an IPRDECK entry. SYSEDIT resets the PROBE data tables to zero. PROBE i. useful. in .ovin, PP routines to CM when they are called frequently enough, thus i.proving syste. performance. 3.7 CONSOLE WATCHING Many times all the various tools are not as useful as just watching the syste. console for signs of thrashing and/or particular user abuse. The following item. are worth watching for: 1) Users running batch jobs in time-sharing mode. 2) Batch job. that are beina rolled in but not getting the CPU before they are rolled out again. 3-8 800 Tuning Guide for ICEK DON 6/88 3.0 TUNING METHODS 3.7 CONSOLE WATCHING 3) Jobs that have excessive resource requests OVer extended peri s. 4) Maintenance jobs running at too high a priority and/or too many running. One job (CT7) is probably enough. Too many maintenance jobs cause a forced rollout every time a time-sharing job is brought in. 5) Permanent file dumping and loading during the prime shift will slow down or stop any PF requests by your users. 6) NOS/VE running in a dual 800 can have a default priority that allows NOS/VE to take the CPU away from NOS. . .. 4-1 800 Tuning Guide for ICEM DDN fli88 4.0 PERMANENT/TEMP FILE ALLOCATION 4.0 PERMANENT/TEMP FILE ALLOCATION It has been found that allowing temporary and permanent files to be allocated on every device seems to be the best strategy to spread the load onto as many units as possible. 5-1 800 Tuning Guide for IeEM DDN 6/88 -------~------------------------------------------------------------ 5. 0 EDL TUNING 5.0 EDL TUNING. In many sites the Engineering Data Library (EDL) runs with ICEK DDN and can contribute to excessive resource use. The following EDL file (IMF2STF/UN-IMF) should have the following values for best performance: 3 NUMBER OF USER PROCESSES TO CHECK FOR EACH MTR LOOP 2 SEMI-IDLE RECALL TIME (MILLISECONDS) 15 ACTIVE RECALL TIME (MILLISECONDS) 1 K-DISPLAY REFRESH CYCLE 50 MAX NUMBER OF TIMES IDLE BEFORE SCP SWAP-OUT 30 MAX NUMB"Ea OF CONNECTED USERS 10 MAX NUMBE~ OF OPEN DATA-BASES 170 MAX NUMBER OF ATTACHED FILES· 3 NUMBER OF ALLOCATED USER STACKS 5 NUMBER OF INPUT BUFFERS 1 NUMBER OF INPUT QUEUE ENTRIES 3 NUMBER OF I/O BUFFERS o NUMBER OF TRANSACTION FILES ON ECS 1 NUMBER OF LONG WAKE-UP WAITS ALLOWED AT STACK 2 NUMBER OF SHORT WAKE-UP WAITS ALLOWED AT STACK 6000 LONG WAKE-UP WAIT SWAP-OUT DELAY 4000 SHORT WAKE-UP WAIT SWAP-OUT DELAY 30 PARCEL STACK PREEMPTION DELAY 30 SINGLE READ STACK PREEMPTION DELAY 1 TRACE The file DEFSTF/UN-IMF (installation file for IMF) should be used as a model. The default values which have been cbanled above are: ACTIVE RECALL TIME - 30 TRACE - 1 Also, journal logging may be turned off for the EDL database. _ This will save considerable overhead. However, if the syat.. crashes witb the database open, the database file may have to be reloaded from the last permanent file backup, instead of being recovered to the point of failure. To turn off journal logging, log into the account where the EDL database file EI20DDB resides, and type the following commands: GET,CHL0G21/UN-IMF CHLOG21,OFF,E120DDB,E120LOG. 6-1 800 Tuning Guide for ICEM DON 6/a~ --------------------------------------~----------------------------- 6.0 CONCLUSION 6.0 CONCLUS·ION. Due to the many ways DON is used, and considering the many other applications that are run on 800s, the tuning recommendations mayor may not be applicable. If after you have tried to tune your system it still has bad response time, please send elM Field Support the following information and they will try to assist you: 1. Your name and phone number. 2. Describe response time with the general areas of DON that are used. 3. Computer model (810, 830, 860, etc.), memory size, . and length of time your system has been running DDN. 4. NOS level of the operating system and indicate if running dual state. s. Disk configuration - Channels, disk models, and hookup configuration. 6. DE entry - memory allocation - Job area, overlay, and swap area. 7. List the names of DDN overlays that are resident in memory. 8. If possible, include a Tracer listing which contains much of the above information. The Tracer listing should be from an average day. 7-1 800 Tuning Guide for ICEK DON 6/88 7 • 0 APPENDIX 7•0 APPENDIX· The following procedure and program will count the times each overlay is called and the total number of overlays called by processing the CT file which is output from a ICEK DON run with the T option on: .PROC,SORTCT. PACK,CT,TAPE2. FILE,TAPE2,BT-C,RT-U. FTNS,I-SORTC,B-LGO,L-L,OPT-2. LGO. NOTE./ RESULTS ON FILE LIST • • DATA,SORTC.·. '. PROGRAM SORTCT(INPUT,OUTPUT,TAPE2,LIST,TAPEI-LIST) INTEGER IBUF,INUM(S12) REWIND 1 REWIND 2 ITOTAL - 0 5 READ(2,END-1S)IBUF IF(IBUF .GT. S12)GO TO 5 IF(IBUF .LT. O)GO TO 5 lNUM(IBUF) - INUM(IBUF)+l ITOTAL - ITOTAL+1 GO TO 5 C 15 DONE READING CT. WRITE(I,3000) DO 30 J-l,512 K- 0 LASTBG - 0 00.20 1-1,512 IF (INUK(I) .GT. LASTBG) THEN LASTBG - lNUM(I) It - 1 20 30 9000 1000 2000 3000 ENDIF CONTINUE IF(LASTBG .EQ. O)GO TO 9000 WRlTE(1,1000) K,INUK(K) lNUM(K) - 0 CONTINUE WRITE(I,2000) ITOTAL FORMAT (' CL - ',03,3X,I10) FORMAT (' SUM - ',110) FORMAT ('1' ,'OVERLAY NUMBER',' END COUNT') , t .. 7-2 800 Tuning Guide for ICEM DON 6/88 end \. CON T R 0 L Y" D..·... 10/31/88 DA T A COR P 0 RAT ION ASSEMBLY NO CORPORATE FILE NUMBER SCMA Avb13" 2043520022 111367 PAGE SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) SHIP TO SOLD TO 1 OF 2 ***************** * PACKING COpy * ***************** COMPUTER PERIPHERALS INTL. 2621 VAN BUREN AVENUE NORRISTOWN, PA 19403 CUSTOMER P.O. TRANSMIT COMPUTER PERIPHERALS INTL. ATTN: C. MARTOCELLO 215/666-4578 2621 VAN BUREN AVENUE NORRISTOWN, PA 19403 NO - SALES REP DEPT ACCOUNT ' I I SUBMITTER SELLING OFFICE INSTALLING OFFICE SYSTEM TYPE SYSTEM SERIAL FXX FXX CY830 00618 PRODUCT NUMBER RELEASE LEVEL D830-207 708 DIVISION CODE FACILITY CODE PROJECT NUMBER 0150/ PRODUCT NAME VER PROD QTY ICEM ENGR DTA LIB 128 1 COMPONENT NUMBER COMPONENT NAME VER COMP TY COMP UNIT TYPE MN QTY PRICE REL76A SMD131461 SMD132189 SMD132190 77987785 EDL128 INSTALL BULL,ETIN INSTALL INSTR EDL URB INSTALL SURVEY 128 1200 MEMO 128 MEMO 128 MEMO MEMO 1 1 1 1 1 0.00 0.00 0.00 0.00 0.00 EXTND EXTND CP BACKPRICE QTY AV ORDER 1 1 1 1 1 0.00 0.00 0.00 0.00 0.00 ORDER PROCESSING CHARGE 0.00 PRODUCT CHARGE 0.00 S S S S S --------------------------------------------------------~--------------------- TOTAL ORDER PROCESSING CHARGE 0.00 TOTAL PRODUCT CHARGE 0.00 TOTAL ORDER CHARGE FREIGHT 0.00 1 U.S. DOLLARS SHIPPED FROM SMD 1227-7240 ROUTING- SURFACE AIR CONTROL DATA CORPORATION SOFTWARE MANUFACTURING AND DIST. 4201 N. LEXINGTON AVE. ARDEN HILLS, MINNESOTA 55126-6198 VIA NUMBER OF PIECES PACKED BY GROSS WEIGHT FREIGHT COST BILL OF LADING' • CON T R 0 L r ., DA T A COR P 0 RAT ION DA:... c; ASSEMBLY NO CORPORATE FILE NUMBER SCMA 10/31/88 AV013 2043520022 111367 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) MISCELLANEOUS CONTENTS: 001 - 1200 BUILD LEVEL A PAGE 2 OF 2 INSTALLATION BULLETIN INFORMATION JULY 9, 1988 *** IMPORTANT - PLEASE FOLLOW THE BELOW PROCEDURE BEFORE INSTALLING THIS PRODUCT *** *** Control Data Corporation provides its customers with an on-line method of obtaining current information about its products. One of the on-line information sources is called an INSTALLATION BULLETIN. An Installation Bulletin can contain information helpful in installing and executing Control Data products. Before installing this product, please contact your local Control Data office or follow the below procedure to determine if an Installation Bulletin exists. All sites should from time to time follow this procedure to review any recent Installation Bulletins that apply to them. 1. The on-line system resides in a Control Data Minnesota Facility. You will need a terminal and a 2400 or lower baud modem. Please dial: 2. (612) ~58-3400 The computer will answer your call (a high pitched sound) and respond with: PLEASE ENTER A COMMAND. 3. Enter: 4. The system will respond with: CREC CSS (carriage return key) FAMILY: . 5. Enter: 6. The system will respond with: CSS,SOLVER,SOLVER (carriage return key) Please enter your site code and password: Site Password- 7. Enter: CDCCIM,9P2PK (carriage return key) SMD131461 INSTALLATION BULLETIN INFORMATION JULY 9, 1988 PAGE 2 8. The system-will respond with the following menu: Your choices are: Search PSR Data Base 1 Retrieve Installation Bulletins 2 Report a new problem or change an existing PSR 3 to end this session BYE HELP if you want help Enter your main menu choice: (carriage return key) 9. Enter: 10. The system will respond with the menu below: 2 Installation Bulletins are available for: 1 ICEM 2 ICEM 2.0.0 3 ICEM MIGRATION CARRIAGE RETURN for main menu -, Enter your IB choice: 11. Enter: (carriage return key) 1 or (carriage return key) 2 or (carriage return key) 3 Entering the number "1" will provide access to all Installa;tion Bulletins for the IeEM 1 an~ associa~ed products. Entering the number "2" will provide access to all Installation Bulletins for ICEM 2.X.X products (2.0.0,2.0.1,2.0.2,etc) and associated products. I Entering the number "3" will provide access to all Installation Bulletins for the ICEM Data Migration Utility on all systems. 12. The system will respond with the menu below: Release:ICEM xxx 1 Display all Installation Bulletins 2 Display all Installation Bulletins entered or changed since a specified date 3 Display all new or changed IBs since your last IB retrieve (YY/MM/DD) 4 Display topic index for this release CARRIAGE RETURN for previous menu Enter your IB choice: 2 , INSTALLATION BULLETIN INFORMATION . JULY 9,' 1988 PAGE 3 (carriage return key) 13. Enter: 14. The system will respond by printing all Installation Bulletins for the IeEM products chosen. 15. Once the system has printed all Installation Bulletins, the menu in step 10 above will appear. Enter: 16. (carriage return key) The system will respond with the menu in step 8 above. Enter: 17. 1 BYE (carriage return key) The system will then log you off. telephone call. 3 You may now disconnect the end 1 October 1988 CONTROL DATA CORPORATION ICEM ENGINEERING DATA LIBRARY V1.2.8 Operating System Level: NOS 2 Level 708 Date: October 1988 INSTALLATION INSTRUCTIONS DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Control r~produce Data Corporation this document. gives the Please contact the appropriate hotline problems or have any questions. USA/Canada International user if permission to you encounter any 1-800-345-9903 (612) 851-4131 SMD132189 1-1 CONTROL DATA CORPORATION October 1988 IeEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 1.0 ICEM EDL VERSION 1.2.8 1.0 ICEM EDL VERSION 1.2.8 1.1 RELEASE DESCRIPTION IeEM Engineering Data Library (EDL) is an application designed to provide a user-friendly interface to Control Data's CAD/CAM products and to manage the engineering data produced by these products. The EDL system runs under the CDC Network Operating System (NOS) Version 2, and the CDC Network Access Method (NAM). and CDC Interactive Facility (IAF) communications packages . . Information Management Facility (IMF) interfaces to the EDL database. A ruh-time subset of IMF is included with EDL. 1.2 HARDWARE REQUIREMENTS EDL requires the minimum hardware configuration for NOS 2 and NAM/IAF. The user station can be a graphic or alphanumeric terminal. EDL requires a field length of 175000 octal words. 1.3 DEPENDENCIES EDL interfaces to the following application packages. IeEM DDN Version ICEM Solid Modeler Unistruc II IeEM Schematics PATRAN-G IGES V2 UNIPLOT XEDIT 1.65 1.13 15AUG84 1.15 2.0 2.23 1-2 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 1.0 ICEM EDL VERSION 1.2.8 1.3 DEPENDENCIES Full Screen Editor Reclaim 1.4 RELEASE MATERIALS EDL consists of two 9-track, 1600 cpi (D=PE) tapes. The format of the tapes is internal (F=I). The EDL Version 1.2.8 product resides on the tape VSN=REL76A and has a label of EDL128 (L=EDL128). The EDL Documentation resides on the tape VSN=REL76B and has a a label of E125DOC (L=E125DOC), same documentation as for EDL 1.2.5. The following files are found on the EDL product release tape. File File File File File File 1 2 3 4 5 6 INSTALL E128PRC E128ABS E128BIN E128LIB El28IBL File 7 File 8 File 9 E128NBL E120CNV EDLCOM File File File File File File File File 10 11 12 13 14 15 16 17 EDLFIX EDLTRAN MOUT El25MMB E125DMB E125MDB E125DDB EDLLIST EDL Installation Procedure EDL Version 1.2.8 Procedure file EDL Absolute Program EDL Main Overlay Relocatable Program EDL Relocatable Subroutine Library EDL Relocatable Information Base Subroutine Library EDL Networking Subroutine Library Conversion Program EDL 1.1.3 to EDL 1.2.0 -EDL Information Base Common Block Text File Unload and reload database procedures EDL Networking Data Type Text File Subroutine to generate EDLLIST Message and Task Metabase Engineering Data Metabase Message and Task Database Engineering Data Database Default Database Load List File File File File File File File File 18 19 20 21 22 23 24 25 SEND RCV RMUGET EDLMCNV EDLSCNV CONVLOG MDBRECS DDBRECS Communication Program used with Communication Program used with Communication Program used with Convers ion Program for' EDLMLOG Conversion Program for EDLSLOG Conversion Program of Log Files Menu and Tasks for EDL 1.2.8 Data Records for EDL 1.2.8 VT-CDCNET VT-CDCNET CONNECT for UNIX* *UNIX is a registered trademark of Bell Laboratories. - - - - - - - - - - .------- 1-3 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 1.0 ICEM EDL VERSION 1.2.8 1.4 RELEASE MATERIALS File File File File File 26 27 28 29 30 IMF2LIB IMF2QU MCSIMF2 IMF2STF IMF2SCP File 31 file 32 File 33 CLGABS OFFLINE IMF2REC File 34 WMTUN52 File 35 Fi l-eo 36 IMF2LDU MOTHERN 0 IMF Version 2.1 Enforcer Library Query Update with IMF 2.1 Interface Start-up Procedur~ for IMF2SCP IMF 2.1 System Tuning File IMF 2.1 System Control Point Absolute Program Program to Associate Log File to Database Recovery Utility Offline Recovery Utility Program to Change Metabase Username for a Database IMF 2.1 Load/Unload/Validate Utility Metabase for Metabases, needed by IMF2LDU The following files are found on the EDL Documentation release tape. File 1 File 2 File 3 INSTALL EDLDMAN EDLRMAN EDL Documentation Installation Procedure EDL Database Administrator's Manual EDL Version 1.2.5 Reference Manual NOTE: 1. The EDL 1.2.8 Database and Meta Database file names have not changed for EDL Version 1.2.8. They still maintain the E125 prefix. This provides an easier conversion process from EDL 1.2.5, EDL 1.2.6 or EDL 1.2.7 to EDL 1.2.8. I 2. SORT/MERGE is needed in order to execute the Migration Utilities to migrate data to EDL 2.0. SORT/MERGE is also needed to execute Query Update(QU) on NOS. 3. The Migration Utilities are needed in order to execute several data transfers ·t~ UNIX or NOS/VE hosts and to execute the EDL'migration tasks. 2-1 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.1 ESTABLISH NOS ACCOUNTS Establish a NOS account for the EDL programs, procedures, and data. base fi les. This account may have any username and password. Establish a NOS account with username IMF on which the Information Management Facility will reside and run. This username must have the name IMF, and must have special validations. It must be able to run a system control point job, communicate with user control points, create unlimited dayfile messages, unlimited CP time, unlimited MS, create direct and indirect files, etc. All usernames from which EDL will be run must have validation to communicate to system control point jobs. Otherwise, they will be automatically logged off when they try to execute EDL. 2.2 MINIMUM VALIDATIONS 2.2.1 UN=IMF AP=MCS AP=RBF Message Control System. Remote Batch Facility. AW=CLPF AW=CSPF AW=CCNR AW=CUCP Create direct access files. Create indirect access files. Enter system without charge number. Access system control point facility. 2-2 CONTROL DATA CORPORATION . October 19.88 ICEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.2.1 UN=IMF CC=77B CM=77B CS=7 DB=7 DF=77B DS=7 FC=7 FS=7 MS=77B PW=pw. Max number of batch commands. Max central memory space used. Cumulat.ive size of all indirect access files. Max number of executing jobs and queue files. Max number of MESSAGE requests to system and job dayfile. File size allowed for an . individual direct access permanent file. File count. File size allowed for an individual indirect access permanent file. Max number of additional mass storage PRU's the user is allowed to allocate to a job. Password for both batch and interactive 2.2.2 ALL OTHER USERS INCLUDING THE DATABASE ADMINISTRATOR AP=IAF AP=RBF Interactive Facility Remote Batch Facility AW=CLPF AW=CSPF AW=CCNR AW=CAND AW=CUCP Create direct access files. Create indirect accesi files. Enter system without charge number. (Note 1) Request nonallocatable devices (magnetic units). (Note 2) Access system control point facility. CC=77B CM=77B CS=7 Max number of batch commands. (Note 2) Max central memory space used. (Note 2) Cumulative size of all indirect access files. tape (Note 2) DB=7 Max number of executing jobs and queue files. (Note 2) DF=77B DS=7 FC=7 FS=7 MS=77B PW=pw Max number of MESSAGE requests to system and job dayfile. (Note 2) File size allowed for an individual direct access peimanent file. (Note ·2) File count. (Note 2) File size allowed for an individual indirect access permanent file. (Note 2) Max number of additional mass storage PRU's the user is allowed to allocate to a job. (Note 2) Password for both batch and interactive 2-3 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.2.2 ALL OTHER USERS INCLUDING THE DATABASE ADMINISTRATOR Note 1 - The EDL installation procedure does not enter a CHARGE statement after the secondary USER commands when the procedure moves to UN=IMF and back to the DBA's account. Note 2 - Required for Database other users. administrator, may vary for 2.3 RUN THE INSTALLATION PROCEDURE If you are installing EDL 1.2.8 on the same user number as EDL .. 1..2.5,EDL 1.2.7, or EDL 1.2.6 (not recommended), rename E125DDB and E125MDB with the following commands. CHANGE,E12BDDB=EI25DDB. CHANGE,EI2BMDB=EI25MDB. Run the product tape installation procedure following control cards. Before installing IMF, IMF from the system control point. H[ using the idle down LABEL,TAPE,VSN=REL76A,F=I,D=PE,R,L=EDLI28. COPYBF,TAPE,INSTALL. BEGIN,INSTALL,INSTALL. The installation procedure password of the EDL account, IMF. will prompt for the username and and the password of username If you already have the IMF2.1 files on username IMF and you do not wish to re-install it, answer .NONE when prompted for the password of username IMF. For sites currently using EDL 1.2.3 or EDL 1.2.5, it is recommended that the IMF files be reinstalled, since the IMF released with EDL 1.2.8 has been updated. IMF has not been updated since the EDL 1.2.6 Release, therefore if you have installed IMF from the 1.2.6 release tape there is no need to reinstall it. If you are running versions 1.2.3 or 1.2.5 it is recommended that you reinstall IMF even if you don't plan to upgrade to EDL 1.2.8, because the new IMF version contains a number of important fixes. After rein"s tall ing IMF, you mus t execute the LOADEDL procedure agains~ EDL 1.2.3 or EDL 1.2.5 to run EDL 1.2.3 or EDL 1.2.5 with the new IMF. For sites· currently using EDL 1.2.6 or EDL 1.2.7, no IMF update is necessary. 2-4 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING 'DATA LIBRARY Vl.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.3 RUN THE INSTALLATION PROCEDURES To install the IMF files without installing the EDL files, be sure that you are logged into the UN=IMF account and type the following commands. Remember to idle down IMF at the system control point. LABEL,TAPE,VSN=REL76A,F=I,D=PE,R,L=EDLI28. COPYBF,TAPE,INSTALL. BEGIN,INSTIMF,INSTALL. More information about starting and tuning IMF can be found in the following sections. After installing the EDL Version 1.2.8 product, you may wish to load the EDL· Documentation set onto your mass storage devices to modify according to your site's particular needs. To install the EDL Documentation set, mount the Documentation tape onto a 9-track tape drive and enter the 'following control cards. RETURN,TAPE,INSTALL. LABEL,TAPE,VSN=REL76B,F=I,D=PE,R,L=EI25DOC. COPYBF,TAPE,INSTALL. BEGIN,INSTALL,INSTALL. The installation procedure password of the account on Documentation files. This which you've installed EDL - - _....__ .__.. _- ..- _.._. __ .. _. will prompt for the user name and the which you wish to install the EDL will usually be the same account on Version 1.2.8. __.._... _--_._-------.-- ....... . / 2-5 CONTROL DATA CORPORATION October l~BB ICEM ENGINEERING DATA LIBRARY Vl.2.B INSTALLATION INSTRUCTIONS NOS 2 Level 70B 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.4 EDIT THE EDL PROCEDURE FILES. 2.4 EDIT THE EDL PROCEDURE FILES. WARNING - DO NOT EDIT E12BPRC IN ASCII MODE! The installation procedure creates the startup file EDL. It is a single CCL proc which gets procedure file E12BPRC from the NOS username where EDL is installed and passes that username as the value of the AUN parameter on the BEGIN statement for EDL. No changes to the file EDL should be necessary. The proc header of procedure EDL in E12BPRC should. be edited to change the default value of the alternate username parameter (AUN) to the username on which the EDL programs and databases were installed. This will ensure that EDL will run correctly even when started directly from E12BPRC instead of from file EDL. The procedures in E128PRC should be checked to ensure that the correct versions of the application programs are obtained from the correct usernames. The standard procedure file assumes that all application programs and procedures are on UN=APPLLIB. If this is not the case at your site, E12BPRC should be changed. If an application such as ICEM DDN is sysedited into your system so that it can be used as a system command, simply remove the attach statements and the statement that checks to see if the application program has been assigned. If you plan on using the Migration tasks with EDL or transfer data from NOS to NOS/VE or UNIX it is necessary to modify E128PRC to reflect the correct username where the migration utilities reside. The default user is set to UN=MGUN. 2.5 ACTIVATE ·THE IMF2.1 SYSTEM CONTROL POINT. Edit file MCSIMF2/UN=IMF to change the commented out USER statement to a valid USER statem~nt for the IMF account. Move this small procedure file'to username SYSTEMX (UI=377777B). Note that the user statement in MCSIMF2 is mandatory and cannot be replaced by a SUI statement. 2-6 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY Vl.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level' 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.5 ACTIVATE THE IMF2.1 SYSTEM CONTROL POINT. The IMF sys tem control point program, IMFSCP, is· started I ike all subsystems by a DSD entry, starting the execution of the procedure file saved under username SYSTEMX. That is, from the console, MCSIMF2. IMF2SCP can run at any control point. To force it to run at a specific control point, use the following CMR/DSD entry before the MCSIMF2 command. ENABLE ,MCS, cpll. To avoid changes to the operating system, the EDL version of IMF2SCP uses the same system identification as the Message Control System, and cannot run when the Message Control System is active. IMF2SCP is idled through the DSD entry IDLE,MCS. When idled-down, IMF2SCP will complete all processing needed to keep the databases in a consistent state. Idle-down can thus be done without damaging the databases, even if there are users active. 2.6 INSTALLING EDL IN NON-CONCURRENT MODE If you do not need to allow more than one ICEM user at the same time using the same EDL database , you can install EDL so that it will run in mono-user mode without the system control point job being active. To do this, follow the following steps. 1. Define an empty direct access file named EDLLOCK on the username where the EDL Engineering Database is installed. This file should be Public in Write mode. EDL will use this file to ensure that only one person tries to use EDL at a time. Otherwise, EDL may abort when the database is busy. DEFINE,EDLLOCK/CT=PU,M=W. 2. Edit Procedure EDL in E128PRC to change the statement $IF,$MONO$=$TRUE$,Ll. to $IF,$MONO$=$MONO$,Ll. and put the AC=l parameter on the E128ABS statement. 2-7 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY Vl.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION 2.7' INSTALLATION VERIFICATION To verify the installation of EDL, do the following steps: Log in to the NOS system using the username established for the database administrator. Initiate EDL by entering: -,EDL The terminal session below shows how to update the DBA's user profile. User responses are indicated by lower case letters. 88/09/15. ICEM ENGINEERING DATA LIBRARY VERSION 1.2.8 COPYRIGHT CONTROL DATA CORP., .1984,1985,1986,1987,1988 ALL RIGHTS RESERVED ENTER EDL USER IDENTIFICATION ? edlid ENTER EDL PASSWORD ? dba CURRENT TERMINAL CONFIGURATION GRAPHICS TERMINAL CDC VIKING 721 DIALOG AREA ON GRAPHICS TERMINAL COMMUNICATIONS RATE . 9600 BAUD COMMUNICATIONS TYPE ASYNCHRONOUS TABLET NO LOCAL ASSIST DEFAULT LOCAL DISPLAY DEFAULT EGM NO BIT PLANES 4 EDLU0037 YOU ARE NOT RUNNING UNDER YOUR OWN NOS USERNAME 1. 2. 3. 4. ADMINISTRATOR TASKS EXIT USER MANAGEMENT GROUP ADMINISTRATION RELEASE ADMINISTRATION E,EXIT USERMGMT GROUPADMIN RELADMIN 2-8 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY Vl.2.8 INSTALL~TION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION 5. PART, FAMILY, AND VENDOR MANAGEMENT ENTER TASK ? usermgmt PARTM USER MANAGEMENT 1. EXIT E,EXIT 2. LIST USERS L,LIST 3. ADD USERS A,ADD 4. DELETE USERS D,DELETE 5. CHANGE A USER'S PROFILE C,CHANGE 6. REACTIVATE A USER R,REACTIVATE SELECT OPTION ? c ENTER THE EDL ID OF THE USER, LIST, OR CR TO EXIT ? ed1id CHANGE USER DATA 1. EXIT E,EXIT 2. PROMPT FOR ALL P,PROMPT 3. EDL PASSWORD PSW,PW U, UN . 4. NOS USER NAME 5. LAST NAME .L,LNM 6. FIRST NAME F,FNM 7. MIDDLE NAME HI,MNH 8. DEPARTMENT D,DEPT 9. TITLE T,TITLE 10. STREET ADDRESS A,ADOR 11. CITY, STAT&, ZIP C,CITY 12. PHONE PH,PHONE 13. FIRST COMMAND CMD,COMMAND 14. DIALOG DELIMITER DIALOG 15. STRING DELIMITER STRING 16. EDITOR EDITOR 17. HOST HOST SELECT OPTION ? p ENTER A NEW EDL PASSWORD OR CR FOR SAME ? dbapw *-Jd, -Jdd, WARNING - THE USER MAY NOT BE ABLE TO ACCESS THEIR OWN FILES IF THEIR NOS USER NAME IS CHANGED THE USER'S NOS USER NAME IS EDLDBA ENTER A NEW NOS USER NAME OR CR FOR SAME ? ed1dba *-Jd, -Jdo', 2-9 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION THE USER'S LAST NAME IS ENTER A NEW LAST NAME OR CR FOR SAME ? smith THE USER'S FIRST NAME IS ENTER A NEW FIRST NAME OR CR FOR SAME ? john THE USER'S MIDDLE NAME IS ENTER A NEW MIDDLE NAME OR CR FOR SAME ? a THE USER'S DEPARTMENT IS ENTER A NEW DEPARTMENT OR CR FOR SAME ? 2210 THE USER'S TITLE IS DATABASE ADMINISTRATOR ENTER A NEW TITLE OR CR FOR SAME ? THE USER'S STREET ADDRESS IS ENTER A NEW STREET ADDRESS OR CR FOR SAME ? 123 main street THE USER'S CITY, STATE, AND ZIP ARE ENTER A NEW CITY; STATE, AND ZIP OR CR FOR SAME ? minneapolis, mn 55000 THE USER'S PHONE NUMBER IS , 2-10 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION ENTER A NEW PHONE NUMBER OR CR FOR SAME ? (612) 555-2345 THE USER'S FIRST COMMAND IS ADMIN ENTER A NEW FIRST COMMAND OR CR FOR SAME ? . THE USER'S DIALOG DELIMITER IS ENTER THE NEW DIALOG DELIMITER OR CR FOR SAME ? THE USER'S STRING DELIMITER IS " ENTER THE NEW STRING DELIMITER OR CR FOR SAME ? THE USER'S DEFAULT EDITOR IS FSE ENTER THE NEW EDITOR OR CR FOR SAME ? CHANGE USER DATA 1. EXIT 2. PROMPT FOR ALL 3. EDL PASSWORD 4. NOS USER NAME 5. LAST NAME 6. FIRST NAME 7 • MIDDLE NAME 8. DEPARTMENT 9. TITLE 10. STREET ADDRESS 11. CITY, STATE, ZIP 12. PHONE 13. FIRST COMMAND 14. DIALOG DELIMITER 15. STRING DELIMITER 16. EDITOR 17. HOST SELECT OPTION E,EXIT P,PROMPT PSW,PW U,UN L,LNM F,FNM MI,MNM D,DEPT T,TITLE A,ADDR C,CITY PH,PHONE CMD,COMMAND DIALOG STRING EDITOR HOST 2-11 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY Vl.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION ? e *'1d, THE USER'S PROFILE HAS BEEN CHANGED ~'dd: ENTER THE EDL ID OF THE USER, LIST, OR CR TO EXIT ? USER MANAGEMENT 1. EXIT 2. LIST USERS 3. ADD USERS 4. DELETE USERS 5. CHANGE A USER'S PROFILE -- ·6. REACTIVATE A USER SELECT OPTION ? list E,EXIT L,LIST A,ADD D,DELETE C,CHANGE R,REACTIVATE ENTER THE EDL ID OF THE USER, LIST, OR CR TO EXIT ? list 2 SELECTIONS EDL ID NAME- 1. EDLCOM 2. EDLID SMITH, JOHN A. '/dd, END OF L-IST '/dd: ENTER A NUMBER, E OR EXIT, OR CR FOR MORE ? 2 EDL USER ID NAME NOS USER NAME DEPARTMENT TITLE STREET ADDRESS CITY, STATE, ZIP PHONE FIRST COMMAND STATUS DIALOG DELIMITER STRING DELIMITER EDITOR EDLID SMITH, JOHN A. 2210 DATABASE ADMINISTRATOR 123 MAIN STREET MINNEAPOLIS, MN 55000 (612) 555-2345 ADMIN ACTIVE / " FSE ENTER CR TO CONTINUE ? .' ------_.'. -....•.. _. -". -- ,,_.. _---- - - -- .__.- -.._-,--_.'---_._-_._..... -_._,.•... .. ' - .•",---- ...--_.,. __ _-------,---_._-_.._._---_._--_ _--_ .. .. 2-12 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA·LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION 2 SELECTIONS EDL ID NAME 1. EDLCOM 2. EDLID SMITH, JOHN A. *** *** END OF LIST ENTER A NUMBER, E OR EXIT, OR CR FOR MORE ? e ENTER THE EDL ID OF THE USER, LIST, OR CR TO EXIT ? USER MANAGEMENT 1. EXIT 2. LIST USERS 3. ADD USERS 4. DELETE USERS 5. CHANGE A USER'S PROFILE 6. REACTIVATE A USER SELECT OPTION ? e E,EXIT L,LIST A,ADD D,DELETE C,CHANGE R,REACTIVATE ADMINISTRATOR TASKS 1. EXIT 2. USER MANAGEMENT 3. GROUP ADMINISTRATION 4. RELEASE ADMINISTRATION 5. PART, FAMILY, AND VENDOR MANAGEMENT ENTER TASK ? quit E,EXIT USERMGMT GROUP ADMIN RELADMIN PARTM 2.8 UPGRADING EDL DATABASES If your sit~ is currently running a previous version of EDL, (pre-1.2.5) you must move 'the information to the new databases. If you have customized EDL for your site, also read the section in the customization manual about upgrading site customizations • . ...•....•.. _._ .. _.__. _ - _...•.•... __ ...•. - - - ---_. __. _ . _ - _..•..... __._._._._..••..•.__.. - - .. - .- - .•...•.... _----_ ... 2-13 CONTROL DATA CORPORATION ICEM ENGINEERING DATA LIBRARY Vl.2.B INSTALLATION INSTRUCTIONS NOS 2 Level 70B 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.B.l CONVERSION FROM EDL 1.1.3 2.B.l CONVERSION FROM EDL 1.1.3 Conversion from EDL 1.1.3 to EDL 1.2.B must be accomplished in three steps: EDL 1.1.3 to EDL 1.2.0, EDL i.2.0 to EDL 1.2.3, and, finally, EDL 1.2.3 to EDL 1.2.B. This section of the document describes the conversion from EDL 1.1.3 to EDL 1.2.0. Conversion from EDL 1.2.0 to EDL 1.2.3 is discussed in section 2~B.2 of this document and conversion from EDL 1.2.3 to EDL 1.2.B in section 2.B.3. To move from EDL 1.1.3 the data must first be moved to an EDL 1.2.0 database. All conversion programs and procedures are available on the "EDL 1.2.B release tape. However, you will need to install a default EDL 1.2.0 database from an EDL 1.2.0 reI eas e ta,pe. In order to convert the information on an EDL 1.1.3 database to your EDL 1.2.0 database, you need to run a procedure called CONVll3. This procedure must be run from the NOS account where the EDL 1.2.0 database will reside. The EDL 1.1.3 database need not be on the same NOS account. Begin the conversion procedure by typing: BEGIN,CONVI13,E12BPRC,UN113=username. Where username is .replaced EDL 1.13 database resides. with the NOS account where the This procedure will submit a job to convert the data from the EDL 1.13 database to the EDL 1.2.0 database. There should be no one else using the EDL 1.2.0 database during this time. After CONV113 has run, the output from the job, and the dayfile, will be on file CONVOUT. CONVOUT will contain details of any records which the program was unable to translate. 2-14 CONTROL DATA CORPORATION . October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.1 CONVERSION FROM EDL 1.1.3 If the conversion program is unable to complete, the output and dayfile from the job will be on a file called CONVERR. Possible causes and solutions are: Problem Solution Misspecified UNl13 Ti:me Limit Re-run the CONVl13 procedure Edit E128PRC, changing the time limit from 1200 on the ~ONVERT procedure. Reinstall an empty.default 1.2.0 database before attempting to rerun the procedure. 2-15 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY Vl.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.2 CONVERSION FROM EDL 1.2.0 TO EDL 1.2.3 2.8.2 CONVERSION FROM EDL 1.2.0 TO EDL 1.2.3 Before moving engineering data into the EDL 1.2.3 database, you must reapply any Query Update Transactions which you used to customize the EDL 1.2.0 database. Otherwise, site defined file types, data types, engineering categories, etc., will not be in the new database, and any engineering data information that uses them will be rejected with constraint violations. You should also delete the user EDLID and the group DBA from the default EDL 1.2.3 database before attempting to convert the old database. This will avoid uniqueness constraint violations as that user and group are moved from the EDL 1.2.0 database. Use the user and group management functions of EDL 1.2.3 or Query Update to accomplish the deletion. To .move engineering data from an EDL 1.2.0 database to an EDL 1.2.3 database, type the following command. BEGIN,CONVI20,EI28PRC,UNI20=username. where username is replaced with the NOS account where the 1.2.0 database resides. EDL This procedure runs the IMF unload-reload utility and a special program to - convert data that cannot be handled properly by the unload-reload utility. If you have a·very large database, you may wish to begin the procedure in a batch job. In some cases, the reload utility may find constraint violations which will cause the new database to be marked invalid. You should look at the error report and lists to determine which records caused the problem. Then use Query Update in repair mode to correct the errors an~ rerun the validate utility. ATTACH,IMF2QU/UN=IMF. IMF2QU. INVOKE EDLDATAW OF EDLDATA KEY EDLORDBA + USING E123DDB REPAIR EDLPW (enter QU directives to·DISPLAY and correct the database) END ATTACH,IMF2LDU/UN=IMF. 2-16 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY VI.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.2 CONVERSION FROM EDL 1.2.0 TO EDL 1.2.3 IMF2LDU. ? VALIDATE THROUGH EDLDATAW OF EDLDATA ? ? ? ? ? KEY EDLORDBA USING EI23DDB REPAIR EDLPW TERM If you have customized EDL 1.2.0 please read the new customization guide. before attempting to convert the database. It is necessary to adapt and reapply your QU -and MDB directives before converting the engineering data . _...... -_ ..- _..._.._.... _. __. _.._....._.._... _ - - - - _ . . _.. __ _._-_.. _ - .. - - _.._-----_ .._ _ _. __ ... _.. .. ... 2-17 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.3 CONVERSION FROM EDL 1.2.3 TO EDL 1.2.8 2.8.3 CONVERSION FROM EDL 1.2.3 TO EDL 1.2.8 Before moving engineering data into the EDL 1.2.8 database, you must reapply any Query Update Transactions which you used to customize the EDL 1.2.3 database. Otherwise, site defined file types, data types, engineering categories, etc., will not" be in the new database, and any engineering data information that uses them will be rejected with constraint violations. You should also delete the user EDLID and the group DBA from the default EDL 1.2.8 database before attempting to convert the old database. This will avoid uniqueness constraint violations as that user and group are moved from the EDL 1.2.3 database. Use the user and group management functions of EDL 1.2.3 or Query Update to accomplish the deletion. To move engineering data from an EDL 1.2.3 1.2.8 database, type the following command. datab~se to an EDL BEGIN,CONV123,E128PRC,UN123=username1,UN128=username2. where username1 is replaced with the NOS account where the EDL 1.2.3 database resides and username2 is replaced with the NOS account where the EDL 1.2.8 database resides. This procedure runs "the IMF unload-:-~eload utility. If you have a large database, you may w1sh to begin the procedure as a batch job. In some cases, the reload utility may find constraint violations which will cause the new database to be marked invalid. You should look at the error report and lists to determine which records caused the problem. Then use Query Update in" repair mode to correct the errors and rerun the validate utility. ATTACH,IMF2QU/UN=IMF. IMF2QU. INVOKE EDLDATAW OF EDLDATA KEY EDLORDBA + USING E125DDB REPAIR EDLPW ON username2 (enter QU directives to DISPLAY and correct the database) END ATTACH,IMF2LDU/UN=IMF. 2-18 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 . INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.4 CONVERSION FROM EDL 1.2.3 TO EDL 1.2.8 IMF2LDU. ? VALIDATE THROUGH EDLDATAW OF EDLDATA ? KEY EDLORDBA ? USING E125DDB ? REPAIR EDLPW ? TERM ? .If you have customized EDL 1.2.3 please read the guide before attempting to convert database. It is necessary to adapt and reapply your QU MOB directives before converting the engineering data. c~stomization 2.9.3. CONVERSION FROM EDL 1.2.5/6/7 new the and TO EDL 1.2.8 If you installed EDL 1.2.8 on the same user number as EDL 1.2.5, 1.2.6 or 1.2.7 then you should have renamed your database files before installing EDL 1.2.8 per instructions. Execute the following commands to maintain your 1.2.5, 1.2.6, or 1.2.7 databases for EDL 1.2.8. CHANGE,E12RDDB=E125DDB. (version 1.2.8, R=release five) CHANGE,E12RMDB=E125MDB. (version 1.2.8, R=release five) CHANGE,E125DDB=E12BDDB. CHANGE,E125MDB=E12BMOB. If you installed EDL 1.2.8 on a different user number from your previous version, execute the following commands to use your old database files for EDL 1.2.8. Under the EDL 1.2.5, 1.2.6 or 1.2.7 user number (olduser): PERMIT,E125DDB,user128=R. 2-19 CONTROL DATA CORPORATION ·October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.9.3 CONVERSION FROM EDL 1.2.5, 1.2.6, 1.2.7· TO EDL 1.2.8 Under the EDL 1.2.8 user number (user128). CHANGE,E12RDDB=E125DDB. (version 1.2.8, R=release) CHANGE,E12RMDB=E125MDB. (version 1.2.8, R=release) DEFINE,E125DDB. DEFINE,E125MDB. CHANGE,E125DDB/CT=S,M=RM . . CHANGE, E125MDB/CT=PU ,M=W. ATTACH,DDB=EI25DDB/UN=olduser. ATTACH,MDB=EI25MDB/UN=olduser. COPY,DDB,E125DDB. COPY,MDB,E125MDB. RETURN,MDB,DDB. PERMIT,EI25DDB,IMF=W. Execute LOADEDL to add your customized ovcaps and routines. Run EDL, all your data, customized menus and messages, and routines should be present. You· need to add the EDL 1.2.8 menu and data records to the menu and data databases. Run EDL and execute the ADDINFO task twice to add the files MDBRECS and DDBRECS to EDL, the application data types are EDL MOB TRANSACTIONS and EDL DDB TRANSACTIONS, respectively. When adding these files you must specify a data name. Execute the task MENUMGMT and retrieve the file MOBRECS, check local file MDBLIST for errors. Execute the tas~ QUBAT~H and retrieve the file DDBRECS, check the local file QULIST for errors. If you have not upgraded EDL to version 1.2.6 then implement the following commands to correct the MSTRING character code. ATTACH,IMF2QU/UN=IMF. IMF2QU. INVOKE EDLDATAW OF EDLDATA KEY $EDLORDBA$ USING E125DDB IF FTFTC=$DDN MENU STRING FILE$ MODIFY SETTING FTCHR » $A$ END 2-20 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING OATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.10 IMF DATABASE MAINTENACE 2.10 IMF DATABASE MAINTENANCE 2.10.1 BACKUP AND RECOVERY IMF 2.1 provides utilities for database journal logging and offline database recovery. There are two procedures in EDL that make these utilities easy to use to backup and recover the EDL database. Thes~· procedures must be run from the NOS account on which the EDL database resides. They should be run only when there are no EDL users on the system. 2.10.1.1 Backup Procedure BEGIN,BACKUP,E125PRC This procedure copies the EDL database file E125DDB to a backup file named E128BAK. It also creates a journal log file named E128LOG which will automatically capture a record of all changes to the EDL Engineering'Data Database. You should run this procedure periodically depending on the amount of EDL activity at your site. Be careful that the database is good before you run the BACKUP procedure since it will overwrite any previous backup and log files. Before running BACKUP, you may wish to copy E125DDB, E128BAK and E128LOG to magnetic tape. ,I 'I 2-21 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.10.1.2 Recovery Procedure 2.10.1.2 Recovery Procedure BEGIN,RECOVER,E128PRC,DBN=username. This procedure is to be used only in the unlikely event that a system crash occurs when the database is open and the EDL database is destroyed. RECOVER copies the backup file E128BAK over the current database file E125DDB and runs the offline recovery utility to update the database with the journal entries from file E128LOG. This restores the database to a consistent state as it appeared just b~fore the database was destroyed. Then this procedure causes the BACKUP procedure described above to be run, ensuring that any subsequent changes are logged. 2.10.1.3 Unload and Reload Database Procedure EDLFIX is a procedure file containing procedures to be used to unload and then reload an EDL database. EDLFIX consists of four procedures, UNLOAD, RELOAD, VALID, and CLEARDB. UNLOAD is a procedure to unload the contents of the E125DDB to files. RELOAD is a procedure to load the information obtained from the UNLOAD utility back into an empty database. (E125DDB) VALID is a procedure to validate a database if the RELOAD utility has problems. CLEARDB is a procedure that takes an "empty" database supplied on the EDL125 release tape and makes it totally empty. This should help the RELOAD procedure run smoothly( use to obtain an empty database for the RELOAD). 2-22 CONTROL DATA CORPORATION Octobero,'1988 ICEM ENGINEERING DATA LIBRARY Vl.2.8 INSTALLATION INSTRUCTIONS NOS""2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.10.1.3 Unload and Reload Database Procedure TO RELOAD YOUR DATABASE: 1. Run the UNLOAD procedure against your current database. BEGIN,UNLOAD,EDLFIX. 2. Swap databases so that the default database from the EDL125 release tape is called Ei25DDB. Do not delete the old database yet. Remember to CHANGE (EI25DDB/CT=S ,M=RM) and PERMIT(EI25DDB,IMF=W). If you have run through the process before you can use the true empty database created by step 5 rather than the one on the EDL release tape. 3. Run the CHMUN procedure to ensure that the metaun is correct. BEGIN,CHMUN,EI28PRC,FN=E125DDB,METAUN=username. 4. If your site does not run with journal logging, then you must turn it off again because logging is turned on in the default database on the EDL release tape. To turn journal logging off enter: BEGIN,CHLOG,E128PRC,FUNC=OFF,FN=El25DDB,AFN=El28LOG. You do not need to run this step if you have done it previously and saved the true empty database from the next step. 5. Run the CLEARDB procedure. The procedure may complain about the AI records which is ok, if the procedure complains about any other records you should call the Hotline. To run the procedure enter: BEGIN,CLEARDB,EDLFIX. 6. After executing the CLEARDB utility, make a copy of the resulting El25DDB. Then, the next time you need to RELOAD data, you can use that database instead of the default DB on the release tape. Then you can skip steps 4 and 5. 7. Run the RELOAD procedure. empty database. BEGIN,RELOAD,EDLFIX. This will reload the data into the 2-23 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY Vl.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.10.1.3 Unload and Reload Database Procdure 8. Run the CHMUN procedure to ensure that the metaun is correct. BEGIN,CHMUN,EI28PRC,FN=El25DDB,METAUN=username. 9. Test everything. NOTE: To run these procedures against EDL123 modify EDLFIX to reflect the El23DDB, i.e. change all occurrances of E125DDB to EI23DDB. 2.10.2 RUNNING WITHOUT JOURNAL LOGGING To -turn journal logging off for the EDL database, execute the following procedure. BEGIN,CHLOG,EI28PRC,FUNC=OFF,FN=EI25DDB,AFN=E128LOG. Substantial improvements in resource' utilization can be achieved by turning journal logging off. However, without journal logging, it is impossible to use the RECOVER procedure to reestablish the database to the point of failure in case the system crashes while a user has the EDL database open. Instead, the file E125DDB must, be restored from the last system file backup. It is unlikely that the database will be corrupted by anything other than a operating system or hardware failure, since IMF performs reprieve processing to close the database gracefully if a program fails or a user uses control T to abort the program. The risk of losing a day or half day of EDL information may be acceptable at your site. The application 2-24 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.10.2 RUNNING WITHOUT JOURNAL LOGGING data such as drawings and journal logging. models are not affected by IMF 2.11 IMF TUNING CONSIDERATIONS The IMF System Tuning File, IMF2STF/UN=IMF, determines. certain parameters that IMF 2.1 uses to control its operation at the system control point. These parameters can affect resource utilization of EDL, response time, and overall system throughput. The tuning parameters are read from the file every· time the IMF (MCS) subsystem is started. To some extent, the optimal settings depend on the type of load on your system. The parameters on the tuning file provided on the EDL release tape are set to reasonable values for an ICEM environment. They are set to minimize the impact of IMF and EDL on system throughput at the possible expense of EDL response time. 2.12 EDL AUTOSTART FOR USERS If a user wishes to log in to EDL without typing his EDL user id and password, create an indirect file called EDLUSER on the user's NOS username. This file should have a single line with the user id in columns 1-10 and the EDL password in columns 11-20. EDL will attempt to read this file and will prompt the user only if the file does not exist or if the information on the file is invalid. 2.13 PASSWORD MASKING If all terminals at your site are communicating in full duplex mode, you may cause EDL to temporarily disable echoplex mode while the users are entering passwords so that the password characters do not appear on the terminal screen. This is accomplished by changing the title of the message 2-25 CONTROL DATA CORPORATION October 1988 IeEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.13 PASSWORD MASKING named "DUPLEX" to "FULL", using a MDB transaction file or query update. See the customization guide. section "CUSTOMIZING THE MESSAGE AND TASK DATABASE" for an explanation of how to change EDL messages. 2 .. 14 USING QUERY UPDATE For the most part, IMF2QU functions as described in the Update Version 3 Reference Manual 60498300. Query The-· Invoke clause used to open an IMF 2.1 database schema, different from the one documented for IMF Version 1. INVOKE external-scheMa-name OF conceptual-scheMa-name [ KEY use-literal] USING database-file-name [ nos-username ] [ REPAIR repair-literal] [ CONCURRENT ] To query the EDL Engineering Database, INVOKE EDL OF EDLDATA USING E125DDB nos-u~ername CONCURRENT To query the EDL Message and Task Database, INVOKE EDLMENUR OF EDLMENU USING E125MDB nos-un To query or update the Engineering Database, INVOKE EDLDATAW OF EDLDATA KEY $EDLORDBA$ + USING E125DDB nos-un CONCURRENT To query or update the Message and Task Database, INVOKE EDLMENUW OF EDLMENU KEY $EDLORDBA$ + USING E125MDB nos-un Sometimes Query Update will not display data for all records of a record type unless FOLLOW directive is entered to specify the access path or coset to be used to retrieve the records. See the Query ~pdate manual and the EDL record layout section of the cus~omization guide. a 1S 3-1 CONTROL DATA CORPORATION I : I ' I" " I ,:, ~ • \ \ 'I October 1988 ICEM ENGINEERING DAT~ LIBRARY Vl.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 ' 3.0 CREATING A NETWORK IN EDL 3.0 CREATING A NETWORK IN EDL This section explains how to set up a network of EDL databases, one on each mainframe. Hosts in an EDL network are configured in a "star", with many subordinates clustered around a single master host. Administrative functions (user validation, part definition) are carried out on the master host. The DBA in the network is responsible for running a job (started with the command INITNET) which polls other hosts in the-· network (a subordinate polls the master, while the master polls each subordinate), then rolls out for a site defined period before repeating the polling cycle. This information is repeated in section 16 of the EDL Customization Guide. It is recommended that the System Administrator become familiar with that document before attempting these changes. For sites maintaining a network configuration including NOS/VE, NOS, and UNIX the following conditions hold true. 1. The NOS/VE host must be the Master host with NOS and UNIX as the Subordinate hosts. 2. The networking capability between NOS/VE and NOS is a scoped down ver-sion of networking. All data records will be maintained except part records and release records (i.e. PI,PR,PD,PS,PV,RA,RP,RS,RT,RU). For sites maintaining a network configuration including and UNIX hosts the following-conditions hold true. NOS 1. The NOS host must ~e the Master host with UNIX as a Subordinate host. 2. The only networking capability between NOS and UNIX are file transfers, no other records will be maintained. NOS will not know about files that reside on UNIX. 3-2 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 3.1 DEFINE HOSTS 3.1 DEFINE HOSTS The default EDL database host name is blank. In order to identify multiple hosts in a network, each host must be given a unique name within EDL. This name should be the three character LID (Logical IDentifier) by which the host is known to RHF. For the NOS/VE host the EDL database host name does not necessarily need to represent the LID. The database host operating system name for a NOS/VE host must be set to NOSVE. This is represented this way only on a NOS host; for the 2.0.2 database it is set to NOS/VE. For a UNIX host the database host· identifier name can at most be 4 characters in length. One host should be designated as the MASTER host for the network. This host must communicate directly to all subordinate hosts which run EDL. Ail administrative functions, such as validating users, and defining parts, and vendors, will be done on this host, and the information will be passed to the subordinates, except for the conditions stated in section 3.0. All transactions dealing with data are done on the subordinate hosts, and then passed up to the master. Therefore, tne master host will contain information about the data on all subordinate hosts, ex~ept for UNIX hosts. 3-3 ., CONTROL DATA CORPORATION 'II \ 1',1 '\ October 1988 I "','H!:EM', ENGINEERING DATA LIBRARY 1.2.8 :: \:,INSTALLATION INSTRUCTIONS NOS '2 Level 708 3.0 CREATING A NETWORK IN EDL 3.2 DEFINE COMMUNICATION LINKS 3',.2 DEFINE COMMUNICATION LINKS CL records must be created for each host in the database, telling EDL which other hosts a specific host can communicate with. Note that each link must be defined twice, saying that HOST A can communicate with HOST B, and that HOST B can communicate with HOST A. 3.3 QU DIRECTIVES TO DEFINE A NETWORK A sample network could consist of two Cyber mainframes, a Cyber 120 which does not run EDL, but whose data is managed by MA4 (whose data is passed up to MB1), and a Cyber 910 Workstation. Following are the QU directives to update the MASTER host (in this. case MB1) for this network configuration. INVOKE EDLDATAW OF EDLDATA KEY $EDLORDBA$ USING E125DDB STORE SETTING HIHOS,HIOFF,HIOS,HIEDL,HIHOSS $MB1$ 1 $NOS$ $T$ $MB1$ $MA4$ 100000 $NOS$ $T$ $MB1$ $SD2$ 200000 $AOS/VS$ $F$ $MA4$ $CDC3$ 300000 $UNIXS $T$ $MB1$ "'END STORE SETTING UVUSR UVHOS UVOUN $EDLID$ $MA4$ $EDLDBA $ $EDLID$ $MB1$ $EDLDBA $ $EDLID$. $SD2$ $DJH $ $EDLID$ $CDC3$ $DBA $ $EDLCOM$ $MA4$ $EDLDBA $ $EDLCOM$ $SD2$ $DJH $ $EDLCOM$ $MB1$ $EDLDBA $ $EDLCOM$ $CDC3$ $DBA $ *END -_..-._._ ..... _---_._--_. __ __.. . -_. __.__ ..:.--_._._-------_._-----------_.:..•. _. ----- -" -------_._-_ ..._---_._-_._----_...__... - -,- ._- ----,... 3-4 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY 1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 3.0 CREATING A NETWORK IN EDL 3.3 QU DIRECTIVES TO DEFINE A NETWORK STORE SETTING CLHOSS CLHOSR $MA4$ $MB 1$. $.MB 1$ $MA4$ $MA4$ $SD2$ $MB1$ $SD2$ $CDC3$ $MA4$ $MA4$ $CDC3$ *END REMOVE USING UVHOS $ $ *END REMOVE USING HIHOS $ $ *END· MODIFY USING HIHOS SETTING HIOFF $MB1$ 0 *END END 3-5 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY 1.2.8 INSTALLATION INSTRUCTIONS NOS 2 Level 708 3.0 CREATING A NETWORK IN EDL 3.3 QU DIRECTIVES TO DEFINE A NETWORK Once the network has been defined on what will be the master host, this configuration should be copied to subordinates. EDL should be installed, then this same QU file should be run on each subordinate host. EDL must run on the same NOS account on each host. For a UNIX subordinate create a transaction file containing records with similar settings. For more information see the User Release Bulletin for EDL 2.0.2. Below are QU directives for a sample network consisting of a NOS/VE (CIMA) master with a NOS (MA4) and a UNIX (CDC3) subordinate hosts. These directives are performed on the NOS host only. Check the User Release Bulletin for EDL 2.0.2 to set up the network for NOS/VE and UNIX, making sure that all networks have the same host identifiers, offsets, and user numbers. INVOKE EDLDATAW OF EDLDATA KEY $EDLORDBA$ USING E125DDB STORE SETTING HIHOS HIOFF HIOS HIEDL HIHOSS $CIMA$ 1 $NOSVE$ $T$ $CIMA$ $MA4$ 100000 $NOS$ $T$ $CIMA$ $CDC3$ 200000 $UNIX$ $T$ $CIMA$ *END STORE SETTING UVUSR UVHOS UVOUN $EDLID$ $CIMA$ $EDLDBA$ $EDLCOM$ $CIMA$ $EDLDBA$ $EDLID$ $MA4$ $EDLDBA$ $EDLCOM$ $MA4$ $EDLDBA$ $EDLID$ $CDC3$ $DBA$ $EDLCOM$ $CDC3$ $DBA$ "t'END STORE SETTING CLHOSS CLHOSR $CIMA$ $MA4$ $MA4$ $CIMA$ $CDC3$ $MA4$ $MA4$ $CDC3$ *END REMOVE USING UVHOS $ $ *END REMOVE USING HIHOS $ $ 7t'END END NOTE: The HIOS setting for a NOS/VE system is NOSVE, this is different from the networking setups for EDL 2.0.1, that setting is NOS/VE. The HIHOS setting for a UNIX system can at most be 4 characters lo~g. -, 3-6 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY 1.2.8 CUSTOMIZATION GUID~ NOS 2 Level 708 3.0 CREATING A NETWORK IN EDL 3.4 E128PRC MODIFICATIONS 3.4 E128PRC MODIFICATIONS 3.4.1 GENERAL MODIFICATIONS WARNING - DO NOT EDIT E128PRC IN ASCII MODE! If your site has a networked environment including a NOS/VE host, E128PRC must be modified to reflect the correct LID, Logical Identifier (RHF) , because the HIHOS field does not necessarily represent the NOS/VE identifier. Modify all occurrances of ST=NVEID to the correct ide Due to this limitation NOS subordinatesca~not transfer to NOS/VE subordinates. If the HIHOS field represents the RHF identifier for the NOS/VE system, then replace ST=NVEID to ST=HOS or HOS2 depending upon the procedure.' 3.4.2 PROCEDURES GETMAS AND GETSUB Procedure GETMAS and GETSUB contain .DATA files with MFLINK directives. These directives are used to poll alternate hosts 1n the network for information which should be sent from. the master to the subordinates, or vice versa. The first line in the .DATA files are USER,EDLDBA,EDLDBA for a NOS system and LOGIN EDLDBA EDLDBA for a NOS/VE system. These statements should be replaced with the batch user statement for the username where EDL will be running in the network. Since the master host will be using these MFLINK directives to poll each subordinate, this means that the username and batch password where EDL runs on each subordinate must be the same. If your site is running with a master NOS/VE host then GETMAS must be modified to reflect the full path name of where EDL is installed on the NOS/VE system. Modify the statement SETWC :CIM.EDL100A.APPLICATIONS.ICEMEDL.VER#_2#_00 to the correct path name. A recommended modification to the GETMAS and GETSUB procedures is to remove the .DATA files from E128PRC (which is available to all users running EDL) , put this information into a private file on the username on which EDL resides, and modify the procedures to read these files rather then the .DATA files. 3-7 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY 1.2.8 CUSTOMIZATION GUIDE NOS 2 Level 708 3.0 CREATING A NETWORK IN EDL 3.4.3 PROCEDURE EDL 3.4.3 PROCEDURE EDL Procedure EDL on file E128PRC must be changed on each host, telling EDL the name of the host. The updated procedure header will look like: .PROC,EDL,I=INPUT,IT=O/IT,OT=O/OT,HOST=hos,AUN=EDLDBA. where' hos is replaced by the name of the host on which this file resides. 3.4~4 EDL LOG FILES Each subordinate should have, on the username on which EDL is installed, a file called EDLSLOG. The master should have a file called EDLMLOG, and one file for each subordinate which runs EDL. These files will be called EDLMhos, where hos is replaced with the host identifier for the subordinate, for a UNIX host these files are called EDLhos. These files should be made public, or permitted to all, usernames which can run EDL, in WRITE mode. These files contain log entries of each transaction which needs to be shipped either from the subordinates to the master, or vice versa. These log files polled are periodically by their destination hosts. 3.5 NETWORK INITIALIZATION The DBA should log into each host on the account where EDL resides, and enter the command INITNET. This will start up a .j ob whi ch wi 11: 1. 2. 3. 4. Poll the subordinates (or master) for transactions which should be sent to this host. Run EDL in batch mode to process these transactions. Rollout for the interval defined in the procedure NETROLL in E128PRC. Repeat. 3-8 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY 1.2.8 CUSTOMIZATION GUIDE NOS 2 Level 708 3.0 CREATING A NETWORK IN EDL 3.5 NETWORK INITIALIZATION This job will have the UJN of NETJOB. It should continue to cycle until the system is deadstarted, at which time the INITNET task should be run again. If the job is dropped, the transaction data is not lost. Network transactions will accumulate in the log files, and will be sent to other hosts whenever the INITNET job is run on the receiving host. 1 October 1988 CONTROL DATA CORPORATION ICEM ENGINEERING DATA LIBRARY V1.2.8 Operating System Level: NOS 2 Level 708 Date: October 1988 USER RELEASE BULLETIN DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features and parameters. Control Data Corporation reproduce this document. -10'0': gives NOTE the user permission -Idd: Please contact the appropriate Hotline if you encounter any problems or have any questions. USA/Canada International 1-800-345-9903 (612) 851-4131 SMD132190 LO 1 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 SOFTWARE RELEASE BULLETIN NOS 2 Level 708 Table of Contents 1.0 INTRODUCTION 1-1 2.0 USER'S SECTION 2-1 2.1 NOTES AND CAUTIONS 2.2 MIGRATION TASKS 3.0 DATABASE ADMINISTRATOR'S SECTION 3.1 NOTES AND CAUTIONS . . • • . 3.2 NETWORK NOTES AND CAUTIONS . . • . 4.0 PSR CORRECTIVE CODE . . . . • • 2-1 2-4 3-1 3-1 3-3 4-1 1-1 \ CONTROL DATA CORPORATION I October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 SOFTWARE RELEASE BULLETIN NOS 2 Level 708 1.0 INTRODUCTION 1.0 INTRODUCTION Version 1.2.8 of the Engineering Data Library is a System Software Update Release (SSU) containing NOS support for the TCP/IP network protocol between NOS and UNIX* workstations as well as PSR corrective code. *UNIX is a registered trademark of Bell Laboratories 2-1 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 SOFTWARE RELEASE BULLETIN NOS 2 Level 708 2.0 USER'S SECTION 2.0 USER'S SECTION 2.1 NOTES AND CAUTIONS 1. On entering EDL, if the user's logged in NOS user name is different from the NOS username in the EDL database, a warning message is displayed. Files created under this condition will not be accessible when the user is logged into the correct username unless the files are specifically permitted to the user. 2. Updating EDL for new files requires you to be running on the NOS username where the file resides. EDL assumes that all new files are private files. If the file is actually a NOS public file, use the EDL PERMIT task to change the file category to PUBLIC. 3. An indirect access permanent file name.d USER must exist on the user's NOS username if the user wishes to use TRANSFER tasks on Solid Modeler data. The file USER contains the job card, user card, and accounting charge card image if needed. 4. In a multi-host network, it is not possible to transfer data to a remote host when using the ACCEPT or RELEASE tasks. Data ~ay be submitted to a release proc~dure from any host on the network, but to ACCEPT or RELEASE the data, the releaser must run on the host where the pending or released destination data is desired to reside. 5. Using the EDIT command on non-permanent files or creation files will prompt the user for the character code to be used to edit the file, UPPER CASE DISPLAY CODE or UPPER LOWER CASE ASCII. 6. The correct file type for PATRAN PATDAT, is RANDOM ACCESS DATA. DATA, local file 7. In using the transfer tasks involving an IGES DATA FILE, the user must use the correct data name of the origination file or the destination file. The IGES data name spe~ified must match the origination data name. The transfer data name specified must match the data name in the IGES file, or if the name in the IGES file is blank, the default data name IGES .. 2-2 " CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY V1.2.8 SOFTWARE RELEASE BULLETIN , NOS 2 Level 708 2.0 USER'S SECTION 8. In a network con~iguration consisting of two or more hosts where a host is not available, the IMPORT and EXPORT commands will require a control-t to exit the wait status. This will not exit the user from EDL. 9. The reference manual states that a part number cannot be deleted if any released data is associated to the part. In fact, the part cannot be deleted if any data is associated to the part, regardless of the status of the data. 10. Data transfers to a remote Virtual complete correctly if the destination exist on the remote system. 11. An EDL 1.2.8 subordinate. NOS Master will System catalog will does not not not track files for a UNIX 12. When transferring data to a remote NOS/vE or UNIX host yo~ must enter the full path name of the catalog in which the file is to reside. 13. When transferring data from a NOS host to a UNIX host all path and file names will be interpreted by EDL to be lower case, therefore all your UNIX catalogs should be created in lower case. ,, , 14. The default dialog delimiter has changed from once you reach the first TASK prompt in EDL. 'I' 15. Two file and application types EDL Vl.2.7. File Type 1. IND ASCII DRAWING were added to to Application Data Type IND ASCII DRAWING This type indicates down dated IPARTA files from NOS/vE or NOS IPARTDs that have been converted to IPARTAs. 2. IND ASCII 2.0 DWG IND ASCII 2.0 DWG This type indicates a 2.0 IPARTA file that has been transferred from EDL 2.0 without being down dated. 2-3 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY Vl.2.B SOFTWARE RELEASE BULLETIN NOS 2 Level 708 2.0 USER'S SECTION 16. During some transfers from UNIX to NOS, you may see an INCORRECT COMMAND message on your screen. Please ignore this; this is a known problem on NOS which has been PSR'ed. 17. The default sleep intervals in the icemlog_server script on a subordinate UNIX workstation may not be long enough for your site. If you encounter problems because VT is not giving NOS sufficient time to process login and logout commands, you may set an environment variable for UNIX EDL users to change the sleep interval: setenv nos_login_sleep #ofsecs . where #ofsecs is the number of seconds VT should wait before doing any further processing. 2-4 I. CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY Vl.2.8 SOFTWARE RELEASE BULLETIN NOS 2 Level 708 2.0 USER'S SECTION 2.2 MIGRATION TASKS Tasks incorporated into EDL at version 1.2.7 allow the migration of engineering data to EDL 2.0 on NOS/VE. The MIGRATE task in the USER task menu is a task menu listing the migration tasks, SELECT, GETTF, POSTF, and TDATA. The MIGRATE task menu can be executed by entering MIGRATE at .any task prompt or entering the appropriate selection from the USER menu. When the MIGRATE task is executed the following menu is displayed. MIGRATE TASKS 1. EXIT 2....SELECT DATA TO MIGRATE 3. GET TRANSACTION FILES 4. POST TRANSACTION FILES 5. TRANSFER DATA AND FILE INFORMATION ENTER TASK E,EXIT SELECT GETTF POSTF TDATA The SELECT task allows you the select dat~ to migrate. The GETTF task obtains the migration files created by the Data Migration Utility to inform EDL of the data that migrated successfully. The POSTF task updates the migration files, and the TDATA task extracts all the EDL information about the data that was migrated, places it on a transaction file, and sends it to NOS/VE. After data has successfully been migrated, the utility ADD_DATA_200 must be executed on NOS/VE. For more information on migration MIGRATION UTILITY USER'S MANUAL. refer to the ICEM DATA 3-1 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY Vl.2.8 SOFTWARE RELEASE BULLETIN NOS 2 Level 708 3.0 DATABASE ADMINISTRATOR'S SECTION 3.0 DATABASE ADMINISTRATOR'S SECTION 3.1 NOTES AND CAUTIONS 1. The EDL 1.2.8 databases have the same file names as EDL 1.2.5/6/7 databases. There are no schema changes between databases, but there are new data records added to the 1.2.8 databases. Maintaining the same database file names provides an easier conversion process. 2. To install data files on a system username such as APPLLIB or LIBRARY, when a SUI statement is used to access the account, use UPDATE EDL FOR ENGINEERING DATA to add the information to EDL, then use CORRECT FILE INFORMATION to change the NOS username of the file to the right username. 3. If two users attempt to update the same EDL record at nearly the same time, a concurrency conflict may occur for the second user. ·Ari error message will be displayed and EDL will return to the previous task menu. The user should reobtain the data to determine what change was made by the other user and try the update again if appropriate. 4. If the user uses a Control T to abort Query Update using IMF, occasionally the user job hangs and cannot be dropped. It may be necessary to do an override from the console to drop the job. 5. The default core memory field length to run EDL Vl.2.8 is 175,000 octal. If EDL aborts due to maximum field length (MFL) exceeded, then edit the procedure file E128PRC, procedure EDL, to change the command MFL,175000 to increase the amount of memory allowed for EDL and IMF. 6. The EDL re1ocatab1e libraries are compiled at NOS 2 level 708. If your site is using an earlier version of NOS and the product sets, there may be incompatibilities between the EDL libraries and the system libraries. This may cause proolems if the EDL absolute is reloaded using the LOADEDL procedure to include site-written Fortran code. If this situation occurs at your site, upgrade the product sets of your site to level 708. I 3-2 CONTROL" DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY Vl.2.8 SOFTWARE RELEASE BULLETIN NOS 2 Level 708 3.0 DATABASE ADMINISTRATOR'S SECTION 7. When a permanent file (PF) utility is running, EDL may abort if IMF tries to create a file. User catalogs that have a user index ending in the same number as the user index of the IMF user name will be locked until the" PF utility has completed and IMF will not be able to create or extend the files it uses for its operations. To prevent a possible loss of data, it is recommended that the system administrator be notified when PFLOAD or PFDUMPs are executing so that they can monitor and coordinate the use of EDL while these utilities are in uSe. 8. The procedure IGTCEI on EI28PRC, which transfers IGES DATA to EXTERNAL IGES DATA, has been modified to write the EXTERNAL IGES DATA to tape. The procedure EITCIG on E125PRC has been modified to read from tape. The tape's VSN is SCRATC (VSN=SCRATC) and the user executing the transfer must be validated to use UNLABELED tapes. The format of the tape request is as follows: REQUEST, TAPE, NT ,LB=KU,"D=PE,CV=AS,F=S, VSN=SCRATC, (PO=W if writing to tape). You may wish to modify this tape request based on your site's needs. Please refer to the IGES Reference Manual for more detail. 9. To execute any-of the data transfers from NOS to NOS/VE or UNIX or execute any of the EDL migration tasks you must have the Data Migration Utility installed. Also you must modify procedure file E128PRC to reflect the user number where the Data Migration Utility is installed. Modify all occurrences of MGUN to the correct user number. J 3-3 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY Vl.2.8 SOFTWARE RELEASE BULLETIN NOS 2 Level 708 3.2 NETWORK NOTES AND CAUTIONS 1. When defining a network th~t includes a NOS/VE an~ a NOS host, NOS/VE must be the master host with the NOS host as the subordinate host. NOS cannot be the master of NOS/VE. This also holds true for a UNIX host; NOS/VE is the master. 2. When defining a network that only includes UNIX hosts, a NOS host must be the master . NOS hosts and . 3. The networking capabilities between a master EDL 2.0.2 NOS/VE host and a subordinate EDL 1.2.8 NOS host include all database records except those dealing with part structure and release. 4. The networking capabilities between a master EDL 1.2.8 NOS host and a subordinate EDL 2.0.2 UNIX host include only those database records involved with a data transfer. The EDL 1.2.8 master host will not track files for the UNIX subordinate. Because UNIX is a subordinate, you must ~hange the USERMGMT task security status from.MASTER to blank in the UNIX menu database if you wish to do user m~nagement on the UNIX workstation. Use TASKMOD to accomplish this. 5. When defining a network on EDL 1.2.8 to include a NOS/VE host, the HIOS field (operating system name) must be set to NOSVE. This is only represented this way on NOS hosts. 6. A NOS subordinate cannot transfer to a NOS/VE subordinate, a NOS subordinate can only transfer to a NOS/VE master, another NOS subordinate, or a UNIX subordinate. 7. If NOS is the master of a UNIX subordinate there may exist conditions which cause the icemlog_server job on UNIX to create several suspended jobs on the NOS EDLCOM operating system user number. This condition causes network logging problems. To clean up this problem, kill the icemlog_server process on UNIX, log into the NOS EDLCOM operating system user number and drop all suspended jobs, then execute the task INITNET on UNIX. 8. When defining a network that includes a UNIX host the HIHOS field in the HI record can be at most 4 characters in length. 4-1 CONTROL DATA CORPORATION October 1988 ICEM ENGINEERING DATA LIBRARY Vl.2.8 SOFTWARE RELEASE BULLETIN NOS 2 Level 708 4.0 PSR CORRECTIVE CODE 4.0 PSR/RSE CORRECTIVE CODE The release of EDL Vl.2.8 corrects the following PSR's. PSR DESCRIPTION EDIA037 EDIA042 EDIA044 EDIA047 ED1A048 EDI0287 EDI0354 EDI0355 EDI0357 EDI0358 MULTI-HOST DATABASE UPDATING FAILS ON DD RECORDS CANNOT DELETE FILES CONTAINING DATA WITH FAMILY CAN'T DELETE DATA INFO WHEN PART-DATA RELATIONSHI MIGRATED GLOBAL PATTERN FILES NOT COMPATIBLE WITH MISSING MIGRATION MESSAGE MULTI-HOST DATABASE UPDATING FAILS ON DD RECORDS EDL 1.2.7 ERRONEOUSLY TRACKS TEMPORARY RETRIEVAL CANNOT DELETE DATA THAT HAS PART OR FAMILY EDL 1.2.7 HANGS AT 'ENTER CR TO CONTINUE' AFTER VIEWING A RELEASED DWG, INDEX INFO IS CREAT 'j CON T R 0 L DA T A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 10/31/88 AV013 2043520022 111367 PAGE SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) SHIP TO SOLD TO 1 ***************** * PACKING COPY * ***************** COMPUTER PERIPHERALS INTL. 2621 VAN BUREN AVENUE NORRISTOWN, PA 19403 CUSTOMER P.O. TRANSMIT COMPUTER PERIPHERALS INTL. ATTN: C. MARTOCELLO 215/666-4578 2621 VAN BUREN AVENUE NORRISTOWN, PA 19403 NO DEPT SALES REP ACCOUNT SUBMITTER SELLING OFFICE INSTALLING OFFICE SYSTEM TYPE SYSTEM SERIAL FXX FXX CY830 00618 PRODUCT NUMBER RELEASE LEVEL D830-207 708 DIVISION CODE 0150/ PRODUCT NAME VER PROD QTY ICEM ENGR DTA LIB 128 l' COMPONENT NUMBER COMPONENT NAME VER COMP TY COMP UNIT TYPE MN QTY PRICE REL76A SMD131461 SMD132189 SMD132190 77987785 EDL128 INSTALL BULLETIN INSTALL INSTR EDL URB INSTALL SURVEY 128 1200 MEMO 128 MEMO 128 MEMO MEMO 1 1 1 1 1 0.00 0.00 0.00 0.00 0.00 EXTND EXTND CP BACKPRICE QTY AV ORDER 0.00 0.00 0.00 0.00 0.00 ORDER PROCESSING CHARGE 0.00 PRODUCT CHARGE 0.00 TOTAL ORDER PROCESSING CHARGE 0.00 TOTAL PRODUCT CHARGE 0.00 0.00 TOTAL ORDER CHARGE 1 1 1 1 1 S S S S S 1 U.S. DOLLARS SHIPPED FROM FREIGHT SMD 1227-7240 ROUTI~G- PROJECT NUMBER FACILITY CODE SURFACE AIR CONTROL DATA CORPORATION SOFTWARE MANUFACTURING AND DIST. 4201 N. LEXINGTON AVE. ARDEN HILLS, MINNESOTA 55126-6198 VIA NUMBER OF PIECES PACKED BY GROSS WEIGHT FREIGHT COST BILL OF LADING \ - .-~''''( ....,~~ --, CON T R 0 L \ ................. > DAT A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 10/31/88 AV013 2043520022 111367 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) MISCELLANEOUS CONTENTS: 001 - 1200 BUILD LEVEL A --------,---- PAGE 2 ..... .........-- ~ INSTALLATION BULLETIN INFORMATION (10/21/87) **** *)x X< * IMPORTANT - PLEASE FOLLOW THE BELOW PROCEDURE BEFOI~E I NST {-iLL I NG TH I S PRODUCT **** **:« * Control Data Corporation provides its customers with an on-line method of obtaining current information about its products. One of the on-line information sources is called an INSTALLATION BULLETIN. An Installation Bulletin can contain information helpful in installing and ex~cuting Control Data products. Before installing this product, please contact your local Control Data office or follow the below procedure to determine if an Installation Bulletin exists. 1. The on-line system resides in the Control Data Sunnyvale California facility. You will need a terminal and 300 or 1200 baud modem. Please dial: (408) 7::-:::4-6100 2. When the computer system answers your call (a high pitched sound) , enter: (carriage return key) enter: (carriage return key) 3. The system will respond with: F('~lvJ I L Y: SMD131461 ""."'. INSTALLATION BULLETIN INFORMATION Page 2 SOL VEl::;: !' SOLVER 4 .. Entf?r: 5.. The system will respond with: !' (carriage return key) OVER ••• 6.. Enter: 7. The system will respond with: Please enter your site code and password: Site Password Bn Ent.er: 9. The system will respond with the following menu: Your choices are: 1 Search PSR Data Base Retrieve Installation Bulletins 2 ~5 Report a new problem or change an existing PSR to end this session BYE HELP if you t"Jant help (carriage return key) CDCCIM,9P2PK (carriage return key) Enter your main menu choice: (carriage return key) 11. The system will respond with the below menu: Installation Bulletins are available for: 1 ICEl"l ~~ ICE 11 2. (:) . (:) CARRIAGE RETURN for main menu En~er your IB choice: - INSTALLATION BULLETIN INFORMATION Page 3 12. Enter: 1 (carriage return key) or 2 (carriage return key) 13. The system will respond with the below menu: Release: ICEI"1 1 Display all Installation Bulletins 2 Display all Installation Bulletins entered or changed since a specified date 3 Display all new or changed IBs since your last IB retrieve (YY/MM/DD) 4 Display topic index for this release CARRIAGE RETURN for previous menu Enter your IB choice: 14. Enter: 1 (carriage return key) 15. The system will respond by printing all Installation Bulletins for the ICEM products. The system will occasionally pause to allow the reading of a page of text. To continue, enter the carriage return key. 16. Once the system has printed all Installation menu in step 11 above will appear. . Enter' : Bulletins~ the (carriage return key) 17. The system will respond with the menu in step 9 above. lB. Enter: BYE (carriage return key) 19. The system will then log you off. te I E~phone ca 11 • end You may now disconnect the ;. / CONTROL DATA CORPORATION - leEM IGES Translators Version 2.22 Operating System Level: NOS 2.5.3 Level 688 December 9, 1987 INSTALLATION INSTRUCTIONS DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Control Data Corporation gives the user permission to reproduce this document. NOTE Please contact the appropriate hotline if you encounter any problems or have any questions concerning installation. USA 800 800 612 Cancrll International 345-9903 527-0564 851-4131 Additional information pertinent to this update may be found in Solver Installation Bulletins for the ICEM products. SMD131744 ------- _.- . -- ... _... -------- I, / . CONTROLDATACORPORATION ICEM IGES TRANSLATORS VERSION 222 INSTALLATION INSTRUCTIONS NOS 2.5.3 LEVEL 688 1.0 2 December 9,1987 DESCRIPTION ICEM IGES Translators allows the user to receive and/or transfer geometry-based information between non-CDC CAD/CAM systems and the ICEM system. ICEM IGES runs under NOS 2. 2.0 HARDWARE REQUIREMENTS ICEM IGES Translators requires the minimum hardware configuration for NOS. 3.0 RELEASE MATERIALS The IGES Translators are released on 9-track tape (VSN=REL38A). The following files are included: File File File File File File 1: 2: 3: 4: 5: 6: INSTALL IGPROC IGESICT IGESCIT IGESVER IGESLST the IGES installation procedure the IGES execution procedure file the IGES Postprocessor - IGES to IPARTD translator the IGES Preprocessor - IPARTD to IGES translator an IGES file - used for verification testing a translator list file - used for verification testing The installation procedure creates the following files and makes them permanent on the installation catalog: Indirect-access file IGPROC Direct-access files IGESICT IGESCIT *** NOTES AND CAUTIONS *** 1. The installer must be sure that permanent files do not exist with the same names as the files generated in the installation procedure. 2. The Tape-to-DiskiDisk-to-Tape facilities now use the NOS FCOPY command. FCOPY is limited to a tape blocking factor of 48 or less. Sites may want to save the following files before upgrading to version 2.22: IGPROC IGESDTT IGESTDT IGES user may wish to use the above procedures and programs when reading or writing tapes have a blocking factor greater than 48. \' / CONTROL DATA CORPORATION ICEM IGES TRANSLATORS VERSION 2.22 INSTALlATION INSTRUCTIONS NOS 2.5.3 LEVEL 688 4.0 3 December 9,1987 INSTALLATION PROCEDURE To the IGES product is installed by executing the install procedure which is the first file on the IGES tape; the installation must be run interactively. It is recommended that ICEM IGES be installed on user number APPLLlB with a user index of 377774. • To installlGES on APPLLlB, enter the following commands from the System Console: X.DIS. SUI,377774. LABEL,TAPE,R,L=IGESV222,VSN=REL38A,F=I,D=PE. COPYBF,TAPE,INSTALL INSTALL DROP. • To installlGES on a user number other than APPLLlB, log onto that user number using any terminal and enter the following commands: LABEL,TAPE,R,L=IGESV222,VSN=REL38A,F=I,D=PE. COPYBF,TAPE,INSTALL INSTALL,usernumber. Edit the file, IGPROC, to modify the default for the AUN parameter. Change the user number from APPLLlB to the NOS user number that the files actually reside in. 5.0 • A successful installation is indicated with the following message: "INSTALLATION COMPLETE; VERIFY GOOD". • An unsuccessful installation is indicated with the following message: "INSTALlJ\TION ABORTED." VERIFICATION PROCEDURE The installation procedure performs a verification test to assure a correct installation of the IGES product. The "INSTALlJ\TION COMPLETE; VERIFY GOOD" message indicates that the verification test was successful. No further verification testing is necessary. end· \ I, \,! CON T R 0 L DAT A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 02/11/88 2B029 2043520020 96415 PAGE SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) SHIP TO SOLD TO 1 ***************** * PACKING COPY * ***************** COMPUTER PERIPHERALS INTL. ATTN: C. MARTOCELLO,215/666-5000 2621 VAN BUREN AVE. NORRISTOWN, PA 19403 CUSTOMER P.O. TRANSMIT COMPUTER PERIPHERALS INTL. ATTN: C. MARTOCELLO,215/666-5000 2621 VAN BUREN AVE. NORRISTOWN, PA 19403 NO SALES REP EM7001 SELLING OFFICE INSTALLING OFFICE EXX EXX PRODUCT NUMBER RELEASE LEVEL .D830-122 688 ACCOUNT MCSWEENEY SYSTEM TYPE SYSTEM SERIAL CY830 00618 DIVISION CODE IGES TRNSLTR FACILITY CODE PROJECT NUMBER ROCOLA 0150/ PRODUCT NAME ICE~ DEPT VER PROD QTY 222 1 COMPONENT NUMBER COMPONENT NAME VER COMP TY COMP UNIT TYPE MN QTY PRICE REL38A 60463050A 60463050B SMD131461 SMD131744 SMD131745 IGESV222 IGES REF MAN IGES REF MAN INSTALL BULLETIN INSTALL INSTR IGES SRB 222 600 RF M RF P MEMO 222 MEMO 222 MEMO 1 1 1 1 1 1 0.00 0.00 0.00 0.00 0.00 0.00 EXTND EXTND CP BACKPRICE QTY AV ORDER 0.00 0.00 0.00 0.00 0.00 0.00 1 1 1 1 1 1 ORDER PROCESSING CHARGE 0.00 6 PRODUCT CHARGE 0.00 TOTAL ORDER PROCESSING CHARGE 0.00 6 TOTAL PRODUCT CHARGE 0.00 1 FREIGHT S L L S S S SHIPPED FROM SMD 1227-7240 ROUTING- SURFACE AIR CONTROL DATA CORPORATION SOFTWARE MANUFACTURING AND DIST. 4201 N. LEXINGTON AVE. ARDEN HILLS, MINNESOTA 55126-6198 VIA NUMBER OF PIECES PACKED BY GROSS WEIGHT FREIGHT COST BILL OF LADING CON T R 0 L DAT A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 02/11/88 2B029 2043520020 96415 PAGE 2 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) TOTAL ORDER CHARGE MISCELLANEOUS CONTENTS: 001 . __ .._ .. - 600 _._ ......._ - - - - - - - - - - - - 0.00 U.S. DOLLARS .' '''':''''( CON T R 0 L DAT A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 02/11/88 2B029 2043520020 96415 PAGE SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) SHIP TO SOLD TO 1 OF 2 ***************** * PACKING COPY * ***************** COMPUTER PERIPHERALS INTL. ATTN: C. MARTOCELLO,215/666-5000 2621 VAN BUREN AVE. NORRISTOWN, PA 19403 CUSTOMER P.O. TRANSMIT COMPUTER PERIPHERALS INTL. ATTN: C. MARTOCELLO,215/666-5000 2621 VAN BUREN AVE. NORRISTOWN, PA 19403 NO SALES REP INSTALLING OFFICE EXX EXX PRODUCT NUMBER RELEASE LEVEL D830-122 688 ACCOUNT MCSWEENEY EM7001 SELLING OFFICE DEPT SYSTEM TYPE SYSTEM SERIAL CY830 00618 DIVISION CODE FACILITY CODE PROJECT NUMBER ROCOLA 0150/ PRODUCT NAME VER PROD QTY ICEM IGES TRNSLTR 222 1 COMPONENT NUMBER COMPONENT NAME VER COMP TY COMP UNIT TYPE MN QTY PRICE REL38A 60463050A 60463050B SMD131461 SMD131744 SMD131745 IGESV222 IGES REF MAN IGES REF MAN INSTALL BULLETIN INSTALL INSTR IGES SRB 222 600 RF M RF P MEMO 222 MEMO 222 MEMO EXTND EXTND CP BACKPRICE QTY AV ORDER 0.00 0.00 0.00 0.00 0.00 0.00 1 1 1 1 1 1 ORDER PROCESSING CHARGE 0.00 6 PRODUCT CHARGE 0.00 1 1 1 1 1 1 0.00 0.00 0.00 0.00 0.00 0.00 TOTAL ORDER PROCESSING CHARGE 0.00 6 TOTAL PRODUCT CHARGE 0.00 1 FREIGHT SHIPPED FROM SMD 1227-7240 ROUTING- SURFACE AIR CONTROL DATA CORPORATION SOFTWARE MANUFACTURING AND DIST. 4201 N. LEXINGTON AVE. ARDEN HILLS, MINNESOTA 55126-6198 VIA NUMBER OF PIECES PACKED BY GROSS WEIGHT FREIGHT COST BILL OF LADING .. _._...... _ - - - - _ . _ •.. _...••. S L L S S S _-- CON T R 0 L D A T A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 02/11/88 2B029 2043520020 96415 PAGE 2 OF 2 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) TOTAL ORDER CHARGE MISCELLANEOUS CONTENTS: 001 - 600 0.00 U.S. DOLLARS , , ,,~ CONTROL DATA CORPORATION ICEM IGES Translators Version 2.22 Operating System level: NOS 2.5.3 Level 688 December 9, 1987 SOFTWARE RELEASE BULLETIN DISCLAIMER ICEM IGES and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Control Data Corporation gives the user permission to reproduce this document. Please make this document available to all IGES users. NOTE Please contact the appropriate hotline if you encounter any problems or have any questions concerning installation. USA Canem International 800 345-9903 800 527-0564 612851-4131 SMD131745 crnTROL DATA CORPORATION ICEM IGES TRANSLATORS VERSION 2:22 SYSTEM RELEASE BULLETIN NOS 2.5.3 LEVEL 688 1.0 2 December 9,1987 Introduction ICEM IGES Version 2.22 incorporates PSR corrective code for the following problems: IIC0062 IIC0063 IIC0064 IIC0068 IIC0069 IICA037 IGES TYPE 106 DAMAGED GEOMETRY TRANSFERRED WAS UNSELECTABLE AND MISPLACED CROSSHATCH SEEMS TO CAUSE IGES TRANSLATION TO FAIL ALLOW ZERO VIEW POINTERS IN DRAWING ENTITY SUBFIGURE SUBORDINATE TO OTHER IGES ENTITIES SHOULDERED UNIGRAPHICS DIAMETER DIMENSION MAY NOT MAP PROPERLY The IGES Postprocessor will now read IGES 3.0 files. The IGES Preprocessor continues to write IGES 2.0 files. 2.0 NOTES AND CAUTIONS 1. IGES V2.22 should be used in conjunction with ICEM DDN V1.64. It may be used in conjunction with ICEM DDN V1.60 ,V1.62 or V1.63. 2. Not all drafting symbols supported by ICEM DDN are supported by the IGES V2.0 standard. Control Data's IGES V2.22 substitutes a blank in place of the symbols not translated. Drafting symbols unique to other vendors may not be translated to ICEM DDN. 3. IGES Drawings are translated into ICEM View Layouts. It may be necessary to adjust the view borders and view scales using DDN when restoring the resulting IPARTD files. 4. The IGES Preprocessor may fail if the IPARTD file does not have DDN type 16 entities as its first two entities. When encountering such a file, the IGES Preprocessor issues warning message 202: EXPECTING ENTITY TYPE 16, TRANSLATION MAY FAIL. If such an IPARTD file causes the IGES Preprocessor to fail, restore the IPARTD file into DON and write it back out again. Use the new IPARTD file. 5. The Tape-to-Disk (TADI) and Disk-to-Tape (DITA) utilities now use the NOS FCOPY command. In the past, some special symbols and lower case characters were changed if blocking factors of 3, 6 or 9 were not used - this is no longer the case. Note: FCOPY is limited to a blocking factor of 48 (The Recommended Practices Manual for IGES suggests a blocking factor of 10 .) 6. When restoring IPARTD files generated by the IGES Postprocessor into DDN, it is important that the DON part be in the same units as the IPARTD file. end - - - - , ----"'--","","-,,-"---- I 'j ,I ' CONTROL DATA CORPORATION SYSTEMS DIVISION INSTALLATION & USAGE NOTES NOS 2 19.2/38.4 KB ASYNCHRONOUS SUPPORT FOR CDC 2550 NPU IC220-A June 4, 1985 Doc:0836i-0840i SMD130882 - - - ,--"--,--".,, , 19.2 KB ASYNCHRONOUS SUPPORT Installation & Usage Notes 1.0 GENERAL The IC220-A Special Product package contains the changes needed to upgrade the standard NAM/NOL and CCP V3 under NOS Version 2 to provide support for 19.2 KB and 38.4 KB Asynchronous communications lines. These changes may be installed in ariy NOS 2 with product level 580 and above. Since the changes effect both NOL and cCP V3. a full NAM/CCP Installation must be run. After installation is complete and a new deadstart tape has been produced. a new NOL file must be generated to define the 19.2 KB and 38.4 KB lines. NOT~: The 19.2 KB and 38.4 lines are fixed speed - i.e. you may not use AUTOREC. 1-1 ._------ ---"-"-.-,-,, .._,.,.,. ".- -.,,-,- - - - - _ . _ - - , -"-_ .. .. " '""'''. ,---_.,-"''',... ' ' - , ' ' , . , - - - - - - - 19.2 KB ASYNCHRONOUS SUPPORT Installation & Usage Notes 2.0 MATERIALS SUPPLIED The materials are supplied on one magnetic tape, labeled, containing 3 files as follows: file 1 file 2 file 3 9TRACK, 1600 BPI, Changes to NDL in Update format. Changes to CCP V3 in Update format. A PRODUCT file containing the modified binaries for NAM/NDL and CCP, at NOS 2.2 level 605. 2-1 .... _-"._._.-... _._._." .. _ - - - - . _ - - - - - - - - - _ . _ - - - - _ . "... , , - - __. ............................. .. __._- - - - - - 19.2 KB ASYNCHRONOUS SUPPORT Installation & Usage Notes 3.0 SPECIAL PRODUCT INSTALLATION To install the 19.2/38.4 KB modifications you must run a full NAM/CCP Installation procedure, and you must have the t\tfo UPDATE modification files available under the installation user-number used at your site. (This is normally user-number INSTALL, pw=INSTALL). Using the tape supplied with this special product proceed as follows: 1) Access the tape under your installation job. LABEL,HODTAPE,NT,D=PE,VSN=IC220A 2) load the first file onto an indirect access file named NAMMOD under user name INSTALL; COPYBF,HODTAPE,NAMMOD SAVE,NAMMOD 3) load the second file onto an indirect access file named UCCP under user name INSTALL; COPYBF,HODTAPE,UCCP SAVE,UCCP 4) you may load the third file onLo a direct access file named PRODUCT under user name INSTALL if your system is at level 605. DEFINE,PRODUCT/H=W. COPYEI,HODTAPE,PRODUCT RETURN,* 3.1 REFERENCES Documents needed for installation and us.e of this special product are as follows: NOS V2 INSTALLATION HANDBOOK, pUblication number 60459320 SRB NOS 2 Level 605/587 or the appropriate SRB for your system NOS 2.2 L605/587 Installation Feature Notes publication number SMD130633B NETWORK DEFINITION LANGUAGE RM publication number 60480000 3-1 19.2 KB ASYNCHRONOUS SUPPORT Installation & Usage Notes 3.2 NAM INSTALLATION Follow the procedures for NAM installation as defined in the NOS V2 Installation Handbook, Chapter 3. You may also have to use the SRB for NOS V2 at the level being used at your site. The "USERF" parameter must be used as indicated on the NAMS Build Procedure. BEGIN,NAMS,INSTALL,USERF=NAMMOD. 3.3 CCP INSTALLATION Follow the procedures for CCP installation as defined in the NOS V2 Installation Handbook, Chapter 3, the appropriate SRB and lhe Installation Feature Notes for NOS. 3.3.1 CCPPHI,CCPBLB The "USERF" parameter must be used as indicated both CCPPHl and CCPBLB build precedure calls. BEG1N,CCPPHl ,INSTALL ,USERF=UCCP. BEGIN,CCPBLB,INSTALL,USERF=UCCP. 3.3.2 CCPVAR Run the Load Variant build procedure, CCPVAR as required for your site. Follow the procedures as described in the NOS V2 Installation Handbook. 3.3.3 CCPLOAD Run the CCPLOAD build procedure as required for your site. procedures as defined in the NOS V2 Installation Handbook. 3-2 Follow the 19.2 KB ASYNCHRONOUS SUPPORT Installation & Usage Notes 4.0 NDL Reference: CDC pUblication number 60480000 NETWORK PRODUCTS NETWORK ACCESS METHOD VERSION 1 NETWORK DEFINITION LANGUAGE REFERENCE MANUAL (herein referred to as the NDL manual) 4.1 CHANGES As a result of this specal product, the LSPEED parameter for Asynchronous communication lines now has a maximum value of 38400. Reference the NDL manual. 1) Table 4-1 page 4-1, for LTYPE=A2. Maximum Speed = 38400. 2) Figure 4-1 Asynchronous LINE statement. add the values 19200 and 38400 to the lspeed value list. 4.2 NDL FILES Change your site NDL file for the .appropriate NPU(S) to define the new high speed lines. These lines should be configured in the lower number CLAs as discussed in the NDL manual. Using the standard CDC NPU configuration, the maximum configuration that is recommended is six lines at 19.2 KB or four lines at 38.4 KB. (See the Feature Notes document for the 19.2/38.4 KB Asynchronous Support). 4-1 . ._.. __ ._.......... _..- - - - •................ _----_.- .... - ... _-_.__._._.-._ ....- . - - .._ 19.2 KB ASYNCHRONOUS SUPPORT Installation & Usage Notes 5.0 HARDWARE The special product clock for the high speed capability must be installed on the 2550 as per instructions provided with the clock board. 5-1 end - ." --_ .. _._ ... _-_ .._.-._---- - - - - - --,----- CONTROL DATA CORPORATION SYSTEMS DIVISION Feature Notes NOS 2 19.2/38.4KB Asynchronous Support For CDC 2550 NPU. IC220-A June 4, 1985 . Doc: 0909i-0911i SMD130883 CONTENTS 1.0 DESCRIPTION 1.1 1.2 1.3 SOFTWARE HARDWARE RESTRICTIONS 2.0 TESTING 2.1 SYSTEM LEVEL 2.2 INITIAL TEST 2.3 GRAPHICS TEST 2.4 EXTENDED TESTING 3.0 CURRENT INSTALLATION NOS 2.2 19.2 KB Asynchronous Support 1.0 DESCRIPTION In response to a special request for support of 19.2 KB and 38.4 KB Asynchronous lines, software changes and a special hardware clock for the CDC 2550 have ~een developed by the Systems Division. This support is now offered as Special Product lC2.20-A from ClM. 1.1 SOFTWARE The software changes were supplied by personnel from Sunnyvale Central Software Support. The changes effect both NDL and CCP5 and have been installed in a NOS 2.2 level 605 system, and a NOS 2.3 level 617 system. NAM and CCP must be rebuilt to include these software changes. 1.1.1 NDL CHANGES Three programs are changed namely - NDLPSS1, NDLNFCM and NDLLIST. The NDL changes consist of 59 lines including the IDENT, update control statements and code changes. history, The changes are either table entry changes or constants which define table lengths. There are no actual code changes. 1.1.2 CCP CHANGES Three programs are changed namely CONST, ASYNCTIP and ZEXBDL. The CCP changes consist of 35 lines including IDENTs, history, update control statements and code changes. The CCP changes are table· changes. only. 1.2 HARDWARE A special hardware board, -Special Product Number 65370-1, was developed to provide 19.2 KB and 38.4 KB clocking to the· loop-mux in the 2550. One board is needed for each loop-mux that must support high speed asynchronous lines. This board must be mounted in the back of the 2550 on the left edge of the backplane. Three wires with special backplane connectors are used for power, gro~nd and clock signal. The clock signal is provided on the fourth clocking port of the loop-mux referred to as "Reference Frequency 0". Installation time is 10-15 minutes pet' board. 1-1 NOS 2.2 19.2 KB Asynchronous Support 1.3 RESTRICTIONS 1.3.1 LINE CONFIGURATION Using the Communications assumptions are used: Subsystem Configurator the following Processor utilization at 19.2 KB is assumed to be double that of a 9600 BPS line or 12%. NPU will be configured for a maximum of 80% utilization. Line Utilization is classed as high volume interactive 1536 cis. @ 80'0 or Thus the development group recommends that the maximum number of 19.2 KB lines that should be configured'on a 2550 is six, and the maximum number of 38.4 lines should .be four. 1.3.2 TERMINALS When using Viking 721 terminals at 19.2 KB, the data flow control XON/XOFF must be enabled on the terminal and at the host. 1-2 NOS 2.2· 19.2 KB Asynchronous Support 2.0 2.1 . TESTING SYSTEM LEVEL The changes have been installed in two NOS systems, NOS 2.2 level 605 and NOS 2.3, level 611. Initial testing was .done under level 605. Testing under level 611 has been completed and some extended testing is being done by the CIM Development Group in Arden Hills. 2.2 INITIAL TESTS Initial tests were run using a CDC Viking 121 running at 19.2 KB and a CDC 151 terminal running at 9600 baud. Various line speeds were tested to insure that they had not been affected by the changes. 2.3 GRAPHICS TESTS Graphics tests were performed using the CIM development CYBER system, two TEKTRONIX 4115B graphics terminals, one TEKTRONIX 4014 graphics terminal and one CDC 122 terminal all running at 19.2 KB. Several text files and demonstration graphics drawings were used in the tests in various combinations. Testing at 38.4 KB utilized one Tektronix 4128 plus the 19.2 KB conf iguration listed above. The Tektronix 4128 and 4115B terminals were run at 38.4 KB while the others were at 19.2 KB 2.4 EXTENDED TESTING BY CIK DEVELOPMENT GROUP The .CIM Development Group is currently running with 18 line~ and 12 CLA's installed both of which exceed the recommended numbers. "The 2550 line configuration includes one 56 KB trunk line. They have not experienced any problems up to this time. 2-1 • NOS 2.2 19.2 KB Asynchronous Support 3.0 CURRENT INSTALLATION The 19.2 KB Asynchronous support is currently installed in one customer site on a NOS 2.2 Level 605 system, ~nd one CDC development gro~p system in Arden Hills using NOS 2.3 Level 617. The customer is running four TEKTRONIX 4115B graphics terminals. The elM configuration was noted in paragraph 2.5 and as indicated, the elM group is running both 38.4 an 19.2 KB lines. 3-1 end CON T R 0 L DATE 10/03/86 D A T A COR P 0 RAT ION PAGE COMPONENT LIST SCMA SOLD TO: 84466 REFERENCE: COMPUTER PERIPHERALS INC. ATTN: C.W. MARTOCELLA,215/666-4578 PO M2-948216-00/PT 0009482161 2621 VAN BUREN AVENUE NORRISTOWN, PA 19403 ASSEMBLY NUMBER: A3021 SMD SHIPMENT NUMBER: 84466 CORPORATE FILE NUMBER: 2043520018 THE FOLLOWING IS A COMPLETE LISTING OF THE COMPONENTS FOR THE PRODUCTS ORDERED. BASED UPON THE INFORMATION IN YOUR ORDER WE ASSUME YOU ALREADY HAVE THOSE MATERIALS LISTED HERE THAT ARE NOT SHOWN ON THE ENCLOSED PACKING LIST. SMD WILL BE HAPPY TO SUPPLY ANY ADDITIONAL COMPONENTS YOU REQUIRE. PRODUCT NUMBER PRODUCT NAME AND VERSION RELEASE LEVEL IC220-A NAM/CCP PRF ENHCE 001 605 COMPONENT NUMBER COMPONENT NAME AND VERSION TYPE MANUAL IC220ATI SMD130882 SMD130883 NAM/CCP PRF ENHNC INSTALL & USAGE FEATURE NOTES TAPE NO. 0655B . - - - -.. COMPONENT LEVEL TYPE 605 605 605 ---- MAGNETIC TAPE MEMO MEMO 1 CON T R 0 L COR P 0 RAT ION DAT A DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 10/03/86 A3021 2043520018 84466 PAGE SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) SHIP TO SOLD TO 1 ***************** * PACKING COPY * ***************** COMPUTER PERIPHERALS INC. ATTN: C.W. MARTOCELLA,215/666-4578 PO M2-948216-00/PT 0009482161 2621 VAN BUREN AVENUE NORRISTOWN, PA 19403 CUSTOMER P.O. TRANSMIT M2-948216-00 EC6185 SELLING OFFICE INSTALLING OFFICE FXX FXX PRODUCT NUMBER RELEASE LEVEL IC220-A 605 COMPUTER PERIPHERALS INC. ATTN: C.W. MARTOCELLA,215/666-4578 PO M2-948216-00/PT 0009482161 2621 VAN BUREN AVENUE NORRISTOWN, PA 19403 DEPT SALES REP NO S. B. LEVY SYSTEM TYPE SYSTEM SERIAL DIVISION CODE CY830 00618 0595 PRODUCT NAME VER PROD QTY NAM/CCP PRF ENHCE 001 1 COMPONENT NUMBER COMPONENT NAME IC220AT1 SMD130882 SMD130883 NAM/CCP PRF ENHNC INSTALL & USAGE FEATURE NOTES ACCOUNT VER COMP TY COMP UNIT TYPE MN QTY PRICE PROJECT NUMBER FACILITY CODE EXTND EXTND CP BACKPRICE QTY AV ORDER 0.00 0.00 0.00 1 1 1 ORDER PROCESSING CHARGE 0.00 3 PRODUCT CHARGE 0.00 600 MEMO MEMO 1 1 1 0.00 0.00 0.00 TOTAL ORDER PROCESSING CHARGE 0.00 3 TOTAL PRODUCT CHARGE 0.00 1 0.00 TOTAL ORDER CHARGE S S S U.S. DOLLARS MISCELLANEOUS CONTENTS: FREIGHT SHIPPED FROM SMD 1270-1979-SMD380 ROUTING- SURFACE AIR CONTROL DATA CORPORATION SOFTWARE MANUFACTURING AND DIST. 4201 N. LEXINGTON AVE. ARDEN HILLS, MINNESOTA 55126-6198 VIA NUMBER OF PIECES PACKED BY GROSS WEIGHT FREIGHT COST BILL OF LADING .- _._._----_.- ._-----_._--------- ------ .. ---------- CON T R 0 L DATE ASSEMBLY NO 10/03/86 A3021 DA T A COR P 0 RAT ION CORPORATE FILE NUMBER SCMA 2043520018 84466 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) 001 . - 600 "._._-_.._._._.---_._... - . - - - . - - - - - - - ._ .. __ _._..- - •.... PAGE 2 CON T R 0 L DAT A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 09/22/88 ... 9M079 2043520024 105781 PAGE 1 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) SHIP TO SOLD TO ***************** * PACKING COPY * ***************** COMPUTER PERIPHERALS INTL. ATTN: C. MARTOCELLO 215/666-4578 2621 VAN BUREN AVENUE NORRISTOWN, PA 19403 COMPUTER PERIPHERALS INTL. 2621 VAN BUREN AVENUE NORRISTOWN, PA 19403 CUSTOMER P.O. TRANSMIT 987558A BS8117 SELLING OFFICE INSTALLING OFFICE FXX FXX PRODUCT NUMBER RELEASE LEVEL D830P-010 678 NO DEPT SALES REP ACCOUNT MCSWEENEY SYSTEM TYPE SYSTEM SERIAL CY830 00618 DIVISION CODE 0090/ PRODUCT NAME VER PROD QTY TIELINE/NP NOS 2 252 1 COMPONENT NUMBER COMPONENT NAME P16004 15190762AE 15190132AD 15190018AB 20266700 TIELINE/NP*N2-678 252 600 TIELINE/NP IHB IH OP TIELINE OP GUIDE TIELINE GIM IN TIELINE/NP D S IN PROJECT NUMBER FACILITY CODE VER COMP TY COMP UNIT TYPE MN QTY PRICE EXTND EXTND CP BACKPRICE QTY AV ORDER 0.00 0.00 0.00 0.00 0.00 1 1 1 1 1 ORDER PROCESSING CHARGE 0.00 5 PRODUCT CHARGE 0.00 M M M M 1 1 1 1 1 0.00 0000 0.00 0.00 0.00 TOTAL ORDER PROCESSING CHARGE 0.00 5 TOTAL PRODUCT CHARGE 0.00 1 TOTAL ORDER CHARGE 0.00 U.S. DOLLARS SHIPPED FROM FREIGHT SMD 1227-7240 ROUTING- SURFACE CONTROL DATA CORPORATION SOFTWARE MANUFACTURING AND DIST. 4201 N. LEXINGTON AVE. ARDEN HILLS, MINNESOTA 55126-6198 AIR VIA NUMBER OF PIECES PACKED BY GROSS WEIGHT FREIGHT COST BILL OF LADING _ ..- .. _ ...... -.. _------ S L L L L .... _------_.. - - - CON T R 0 L DATE ASSEMBLY NO DAT A COR P 0 RAT ION CORPORATE FILE NUMBER SCMA ... 09/22/88 9M079 -II 2043520024 105781 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) MISCELLANEOUS CONTENTS: 001 - 600 - - - , ._,,-_.,...., , - - - - - - - - PAGE 2 , CON T R 0 L .... DA T A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER 09/22/88 9M079 2043520024 SCMA . PAGE 1 OF 2 105781 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) SHIP TO SOLD TO ***************** * PACKING COPY * ***************** COMPUTER PERIPHERALS INTL. ATTN: C. MARTOCELLO 215/666-4578 2621 VAN BUREN AVENUE NORRISTOWN, PA 19403 COMPUTER PERIPHERALS INTL. 2621 VAN BUREN AVENUE NORRISTOWN, PA 19403 CUSTOMER P.O. TRANSMIT 987558A BS8117 NO INSTALLING OFFICE SYSTEM TYPE SYSTEM SERIAL FXX FXX CY830 00618 RELEASE LEVEL D830P-010 678 ACCOUNT MCSWEENEY SELLING OFFICE PRODUCT NUMBER DEPT SALES REP DIVISION CODE 0090/ PRODUCT NAME VER PROD QTY TIELINE/NP NOS 2 252 1 VER COMP TY COMP UNIT TYPE MN QTY PRICE COMPONENT NUMBER COMPONENT NAME P16004 15190762AE 15190132AD 15190018AB 20266700 TIELINE/NP*N2-678 252 600 TIELINE/NP IHB IH OP TIELINE OP GUIDE TIELINE GIM IN TIELINE/NP D S IN PROJECT NUMBER FACILITY CODE EXTND EXTND CP BACKPRICE QTY AV ORDER 0.00 0.00 0.00 0.00 0.00 1 1 1 1 1 ORDER PROCESSING CHARGE 0.00 5 PRODUCT CHARGE 0.00 1 1 1 1 1 M M M M 0.00 0.00 0.00 0.00 0.00 TOTAL ORDER PROCESSING CHARGE 0.00 5 TOTAL PRODUCT CHARGE 0.00 1 TOTAL ORDER CHARGE 0.00 FREIGHT S L L L L U.S. DOLLARS SHIPPED FROM CONTROL DATA CORPORATION SOFTWARE MANUFACTURING AND DIST. 4201 N. LEXINGTON AVE. ARDEN HILLS, MINNESOTA 55126-6198 SMD 1227-7240 ROUTING- SURFACE AIR VIA NUMBER OF PIECES PACKED BY GROSS WEIGHT FREIGHT COST BILL OF LADING -------------_ ..... _---_ ..._. __ ._._._ .. _._ ... CON T R 0 L DAT A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 09/22/88 9M079 2043520024 105781 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) MISCELLANEOUS CONTENTS: 001 - 600 PAGE 2 OF 2 9' r,:J &::\ CONTf\OL DATA \::I r:!J COR]lOR(\T10N SOFTWARE AVAILABILITY BULLETIN , Distribution List For CDC CYBER 1BO/170/70L/6000 SAB No. 692 November 17, 19BB ICEM ENGINEERING DATA LIBRARY UNDER NOS 2 (Level 70B Release) A. ABSTRACT ICEM Engineering Data Library Version 1.2.B under NOS 2 is updated to release level 70B. This release includes support for the 6000, CDC CYBER 70, 170, lBO, A and E series systems. Depending upon the hardware mainframe, different product numbers will apply. (Refer to tables 2 and 3 of the Request for Software Product Update Materials form for appropriate product number.) B. DESCRIPTION OF RELEASE The ICEM Engineering Data Library V1.2.B provides the user with: Simplified operating features Data Management features Customization features A user interface to several other ICEM applications Version 1.2.B provides data management and operational interface functions for the following ICEM applications: ICEM DDN IeEM Solid Modeler ICEM Solid Analysis PATRAN II IGES UNISTRUC 1. 65 1.13 1.13 2.0 2.23 15AUGB4 The following new feature is available with V1.2.B: TCP/IP Support TCP/IP, available with NOS 2.6.1 level 708, is required to use ICEM EDL 1.2.8. be separately licensed. c. TCP/IP must PUBLICATIONS There are no new or updated publications pertaining to this release. D. ORDERING INFORMATION These update materials are now available. These update materials will be sent existing licensed domestic customers with Support Service. International reference the separately enclosed ordering instructions for details on how updates. Licensed software products and update materials are available only have entered into a contractual agreement with Control Data for the use of these automatically to customers should to order these to cus tomers who products. Customers not currently licensed for these update products, who place new orders through their sales representative at this time, and who wish to receive level 70B as their initial delivery, should specify the desired level in their order. New software orders must be covered by a license agreement which lists each product explicitly. Distribution List For CDC CYBER 180/170/70L/6000 SAB No. 692 Page 2 TABLE 1. SUMMARY LEVEL 708 Product Namet Nominal Release Level Identifiertt Level of Latest Available Media PSRs at New Level :Features :---------------------------------------------------------------------------------------------------: : ICEM Engineering Data Library 708 708 : 708 Yes :---------------------------------------------------------------------------------------------------: tRefer to tables 2 and 3 of the Request for Software Product Update Materials form for applicable product numbers. Contact your Control Data sales representative to ensure correct product number for appropriate mainframe. The product listed in this table is BINARY only. ttThis column indicates the latest release at which code and/or documentation changes have been made for each product shown. CONTROL DATA CORPORATION ARDEN HILLS PROGR. DIV SW MANUFACTURING & DIST. FIELD AVAILABILITY SUMMARY NO. REV. DATE PAGE FOR APPLICATIONS UNDER NOS 2 19-CONFIGURATION MANAGEMENT-88 PRODUCT DESCRIPTION THE USER'S STREET ADDRESS IS ENTER A NEW STREET ADDRESS OR CR FOR SAME ? 123 main street THE USER'S CITY, STATE, AND ZIP ARE ENTER A NEW CITY, STATE, AND ZIP OR CR FOR SAME ? minneapolis, mn 55000 THE USER'S PHONE NUMBER IS 2-10 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 664 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION. ENTER A NEW PHONE NUMBER OR CR FOR SAME ? (612) 555-2345 THE USER'S FIRST COMMAND IS ADMIN ENTER A NEW FIRST COMMAND OR CR FOR SAME ? THE USER'S DIALOG DELIMITER IS / ENTER THE NEW DIALOG DELIMITER OR CR FOR SAME ? THE USER'S STRING DELIMITER IS " ENTER THE NEW STRING DELIMITER OR CR FOR SAME ? THE USER'S DEFAULT EDITOR IS FSE ENTER THE NEW EDITOR OR CR FOR SAME ? CHANGE'USER DATA 1. EXIT 2. PROMPT FOR ALL 3. EDL PASSWORD 4. NOS USER NAME 5. LAST NAME 6. FIRST NAME 7. MIDDLE NAME 8. DEPARTMENT 9. TITLE 10. STREET ADDRESS 11. CITY, STATE, ZIP 12. PHONE 13. FIRST COMMAND 14. DIALOG DELIMITER 15. STRING DELIMITER 16. EDITOR 17. HOST SELECT OPTION E,EXIT P,PROMPT PSW,PW U,UN L,LNM F,FNM MI,MNM D,DEPT T,TITLE A,ADDR C,CITY PH,PHONE CMD,COMMAND DIALOG STRING EDITOR HOST 2-11 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 664 .2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION .1 e ,'dd: THE USER'S PROFILE HAS BEEN CHANGED ,'dd: ENTER THE EDL ID OF THE USER, LIST, OR CR TO EXIT 1 USER MANAGEMENT 1. EXIT 2. LIST USERS 3. ADD USERS 4. DELETE USERS 5. CHANGE A USER'S PROFILE 6. REACTIVATE A USER SELECT OPTION 1 list E,EXIT L,LIST A,ADD D,DELETE C,CHANGE R,REACTIVATE ENTER THE EDL ID OF THE USER, LIST, OR CR TO EXIT 1 list 2 SELECTIONS EDL ID NAME 1. EDLCOM 2. EDLID SMITH, JOHN A. *** *** END OF LIST ENTER A NUMBER, E OR EXIT, OR CR FOR MORE 1 2 EDL USER ID NAME NOS USER NAME DEPARTMENT TITLE STREET ADDRESS CITY, STATE, ZIP PHONE FIRST COMMAND STATUS DIALOG DELIMITER STRING DELIMITER EDITOR ENTER CR TO CONTINUE 1 EDLID SMITH, JOHN A. 2210 DATABASE ADMINISTRATOR 123 MAIN STREET MINNEAPOLIS, MN 55000 (612) 555-2345 . ADMIN ACTIVE / " FSE 2-12 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 664 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION -------------------------------------------------------------------2 SELECTIONS EDL ID NAME 1. EDLCOM 2. EDLID SMITH, JOHN A. *** *** END OF LIST ENTER A NUMBER, E OR EXIT, OR CR FOR MORE' ? e ENTER THE EDL ID OF THE USER, LIST, OR CR TO EXIT ? 1. 2G 3. USER MANAGEMENT EXIT LIST USERS ADD USERS E,EXIT L,LIST A,ADD ------------------~4r..~~D~EtLE~T~E~Uffi5ffiERR£5------------------------~D~,.DD~------------------------- 5. CHANGE A USER'S PROFILE '6. REACTIVATE A USER SELECT OPTION ? e ADMINISTRATOR TASKS EXIT USER MANAGEMENT GROUP ADMINISTRATION RELEASE ADMINISTRATION 5 • PART, FAMI LY, AND VENDOR MANAGEMENT ENTER TASK ? quit 1. 2. 3. 4. C,CHANGE R,REACTIVATE E,EXI't USERMGMT GROUP ADMIN RELADMIN PARTM 2.8 UPGRADING EDL DATABASES If your site is currently running a previous version of EDL, you must move the information to the new databases. If you have customized EDL for your site, also read the section in the customization manual about upgrading site customizations. 2-13 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 664 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.1 CONVERSION FROM EDL 1.1.3 2.8.1' CONVERSION FROM EDL 1.1.3 Conversion from EDL 1.1.3 to EDL 1.2.5 must be accomplished in three steps: EDL 1.1.3 to EDL 1.2.0, EDL 1.2.0 to EDL 1.2.3, and, finally, EDL 1.2.3 to EDL 1.2.5. This section of the document describes the conversion from EDL 1.1.3 to EDL 1.2.0. Conversion from EDL 1.2.3 to EDL 1.2.5 is discussed in section 2.8.2 of this document and conversion from EDL 1.2.3 to EDL 1.2.5 in section 2.8.3. To move from EDL 1.1.3 the data must first be moved to an EDL 1.2.0 database. All conversion programs and procedures are available on the EDL 1.2.5 release tape. However, you will need to install a default EDL 1.2.0 database from an EDL 1.2.0 release tape. In order to convert the information on an EDL 1.13 database to your EDL 1.2.0 database, you need to run a procedure called CONV113~ This procedure must -be run from the NOS.account where the EDL 1.2.0 database will reside. The EDL 1.13 database need not be on the same NOS account. Begin the conversion procedure by typing: BEGIN,CONVI13,EI25PRC,UN113=username. Where username is replaced EDL 1.13 database resides. with the NOS account where the This procedure will submit a job to convert the data from the EDL 1.13 database to the EDL 1.2.0 database. There should be no one else using the EDL 1.2.0 database during this time. After CONV113 has run, the output from the job, and the dayfile, will be on file CONVOUT. CONVOUT will contain details of any records which the program was unable to translate. --_.-. __ ...._--------.__._--_._._._-_. _ .. ------- 2-14 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 664 -------------------------------------------------------------------2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.1 CONVERSION FROM EDL 1.1.3 -------------------------------------------------------------------If the conversion program is unable to complete, the output "and dayfile from the job will be on a file called CONVERR. Possible causes and solutions are: Problem Solution Misspecified UN1l3 Time Limit Re-run the CONVl13 procedure Edit El25PRC, changing the time limit from 1200 on the CONVERT procedure. Reinstall an empty default 1.2.0 database before attempting to rerun the procedure. 2-15 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 664 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.2 CONVERSION FROM EDL 1.2.0 TO EDL 1.2.3 ---------------~-------------------------------------- -------------- 2.8.2 CONVERSION FROM EDL 1.2.0 TO EDL 1.2.3 Before moving engineering data into the EDL 1.2.3 database, you must reapply any Query Update Transactions which you used to customize the EDL 1.2.0 database. Otherwise, site defined file types, data types, engineering categories, etc., will not be in the new database, and any engineering data information that uses them witl be rejected with constraint violations. You should also delete the user EDLID and the group DBA from the default EDL 1.2.3 database before attempting to convert the old database. This will avoid uniqueness constraint violations as that user and group are moved from the EDL 1.2.0 database. Use the user and group management functions of EDL 1.2.3 or Query Update to accomplish the deletion. To move engineering data from an EDL 1.2.0 database to an EDL 1.2.3 database, type the following command. BEGIN,CONV120,E125PRC,UN120=username. where username is replaced with the NOS account where the 1.2.0 database resides. EDL This procedure runs the IMF unload-reload utility and a special program to convert data that cannot be handled properly by the unload-reload utility. If you have a very large database, you may wish to begin the procedure in a batch job. In some cases, the reload utility may find constraint violations which will cause the new database to be marked invalid. You should look at the error report and lists to determine which records caused the problem. Then use Query Update in repair mode to correct the errors and rerun the validate utility. ATTACH,IMF2QU/UN=IMF. IMF2QU. INVOKE EDLDATAW OF EDLDATA KEY EDLORDBA + USING E123DDB REPAIR EDLPW (enter QU directives to DISPLAY and correct the database) END ATTACH,IMF2LDU/UN=IMF. 2-16 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 664 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.2 CONVERSION FROM EDL 1.2.0 TO EDL 1.2.3 IMF2LDU. ? VALIDArE THROUGH EDLDATAW 'OF EDLDATA ? KEY EDLORDBA ? USING El23DDB ? REPAIR EDLPW ? TERM ? If you have customized EDL 1.2.0 please read the customization guide before attempting to convert database. It is necessary to adapt and reapply your QU MDB directives before converting the engineering data. new the and 2-17 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 664 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.9~2 CONVERSION FROM EDL 1.2.3 TO EDL 1.2.5 2.9.2 CONVERSION FROM EDL 1.2.3 TO EDL 1.2.5 Before moving engineering data into the EDL 1.2.5 database, you must reapply any Query Update Transactions which you used to customize the EDL 1.2.3 database. Otherwise, site defined file types, data types, engin"eering categories, etc., will not be in the new database, and any engineering data information that uses them will be rejected with constraint violations. You should also delete the user EDLID and the group DBA from the default EDL 1.2.5 databas;-b;fore attempting to convert the old database. Th~s will avoid uniqueness constraint violations as that user and group are moved from the EDL 1.2.3 database. Use the user and group management functions of EDL 1.2.3 or Query Update to accomplish the deletion. To move engineering data from an EDL 1.2.3 database to an EDL 1.2.5 database, type the following command. BEGIN,CONVI23,E125PRC,UN123=usernamel,UNI25=username2. where usernamel is replaced with the NOS account where the EDL 1.2.3 database resides and username2 is replaced with the NOS account where the EDL 1.2.5 database resides. This procedure runs the IMF unload-reload utility. If you have a large database, you may wish to begin the procedure as a batch job. In some cases, the reload utility may find constraint violations which will cause the new database to be marked invalid. You should look at the error report and lists to determine which records caused the. problem. Then use Query Update in repair mode to correct the errors and rerun the validate utility. ATTACH,IMF2QU/UN=IMF. IMF2QU. INVOKE EDLDATAW OF EDLDATA KEY EDLORDBA + USING E125DDB REPAIR EDLPW ON username2 (enter QU directives to DISPLAY and correct the database) END ATTACH,IMF2LDU/UN=IMF. ) ) 7- c;.,\) \) ._--- ----_.. _-",_._.,.__ .... "._•..._. ._--------.-_._-"'-_.. .... " " . - - - - - - - - - - - - - " " 2-18 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS . NOS 2 Level 664 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.9.2 CONVERSION FROM EDL 1.2.3 TO EDL 1.2.5 IMF2LDU. ? VALIDATE THRO~GH EDLDATAW OF EDLDATA . ? KEY EDLORDBA ? USING E125DDB ? REPAIR EDLPW ? TERM ? If you have customized EDL 1.2.3 please read the customization guide before attempting to convert database. It is necessary to adapt and reapply your QU MDB directives before converting the engineering data. new the and 2.10 IMF DATABASE MAINTENANCE 2.10.1 BACKUP AND RECOVERY IMF 2.1 provides utilities for database journal logging and offline database recovery. There are two procedures in EDL that make these utilities easy to use to backup and recover the EDL database. These procedures must be run from the NOS account on which the EDL database resides. They should be run only when there are no EDL users on the system. 2.10.1.1 Backup Procedure BEGIN,BACKUP,EI25PRC This procedure copies the EDL database file E123DDB to a backup file named EI23BAK. It also creates a journal log file named E123LOG which will automatically capture a record of all changes to the EDL Engineering Data Database .. You should run this procedure periodically depending on the amount of EDL activity at your site. Be careful that the database is good before you run the BACKUP procedure since it 2-19 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 664 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.10.1.1 Backup Procedure will overwrite any previous backup and log files. Before running· BACKUP, you may wish to .copy 'E125DDB,. E125BAK and E125LOG to magnetic tape. 2.10.1.2 Recovery Procedure BEGIN,RECOVER,E125PRC,DBN=username. This procedure is to be used only in the unlikely event that a system crash occurs when the database is open and the EDL database is destroyed. RECOVER copies the backup file E125BAK over the current database file E125DDB and runs the offline recovery utility to update the database with the journal entries from file E125LOG. This restores tha database to a consistent state as it appeared just before the database was destroyed. Then this procedure causes the BACKUP procedure described above to be run, ensuring that any subsequent· c~anges are logged. 2.10.2 RUNNING WITHOUT JOURNAL LOGGING To turn journal ,logging off for the EDL database, execute the following procedure. BEGIN,CHLOG,E125PRC,FUNC=OFF,FN=E125DDB,AFN=E125LOG. Substantial improvements in resource utilization can be achieved by turning journal logging off. However, without journal logging, it is impossible to use the RECOVER procedure to reestablish the database to the point of failure in case the system crashes while a us~r has the EDL database ope~. Instead, the file E125DDB must be restored from the last system file backup. It is unlikely that the database will be corrupted by anything other than a operating system or hardware failure, since IMF performs reprieve processing to close the database gracefully if an program fails or a.user uses control T to abort the program. The risk of losing a day or half day of EDL information may be acceptable at your site. The application ... _- ....... _.. _..__ .. .....- . - - , . __.. " ........... - .'_. __ ..• ---- 2-20 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 664 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.10.2 RUNNING WITHOUT JOURNAL LOGGING -data such as drawings and journal logging. models are not affected by IMF 2.11 IMF TUNING CONSIDERATIONS The IMF System Tuning File, IMF2STF/UN=IMF, determines certain parameters that IMF 2.1 uses to control it's operation at the system control point. These parameters can affect resource utilization of EDL, response time, and overall system throughput. The tuning parameters are read from the file every time the IMF (MCS) subsystem is started. To some extent, the optimal settings depend on the type of load on your system. The parameters on the tuning file provided on the EDL release tape are set to reasonable values for an ICEM environment. They are set to m1n1m1ze the 1mpact of IMF and EDL on system throughput at the possible expense of EDL response time. 2.12 EDL AUTOSTART FOR USERS If a user wishes to log in to EDt without typing his EDL user id and' password, create an indirect file called EDLUSER on the user's NOS username.This file should have a single line with, the user id in columns 1-10 and the EDL password in columns 11-20. EDL will attempt to read this file and will prompt the user only if the file does not exist or if the information on the file is invalid. 2.13 PASSWORD MASKING If all terminals at your site are communicating in full duplex mode, you may cause EDL to temporarily disable echoplex mode while the users are entering passwords so that the password characters do not appear on the terminal screen. This is accomplished by changing the title of the message 2-21 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 664 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.13 PASSWORD MASKING named "DUPLEX" to "FULL", using a MOB transaction file or query. upd.ate. See· the cus·tomization° guide sectiqn "CUSTOMIZING THE MESSAGE AND TASK DATABASE" for an explanation of how to change EDL messages. 2.14 USING QUERY UPDATE For the most part, IMF2QU functions as described in the Update Version 3 Reference Manual 60498300. Query' The Invoke clause used to open an IMF 2.1 database schema, different than the one documented for IMF Version 1. INVOKE external-schema-name OF conceptual-schema-name [ KEY use-literal] USING database-file-name [ nos-username [ REPAIR repair-literal] [ CONCURRENT ] To query the EDL Engineering Database, INVOKE EDL OF EDLDATA USING E125DDB nos-username CONCURRENT To query the EDL Message and Task Database, INVOKE EDLMENUR OR EDLMENU USING E125MOB nos-un To query or update the Engineering Database, INVOKE EDLDATAW OF EDLDATA KEY $EDLORDBA$ + USING E125DDB nos-un CONCURRENT To query or update the Message and Task Database, INVOKE EDLMENUW OF EDLMENU KEY $EDLORDBA$ + USING E125MOB nos-un Sometimes Query Update will not display data for all records of a record type unless a FOLLOW directive is entered to specify the access path or coset to be used to retrieve the records. See the Query Update manual and the EDL record layout section of the customization guide. ---" "."'-' .•.._-_.... _---._.._.... 1S 3-1 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY 1.2.5 INSTALLATION·INSTRUCTIONS NOS 2 Level 664 3.0 CREATING A NETWORK IN EDL 3.0 CREATING A NETWORK IN EDL This section explains how to set up a network of EDL databases, one on each mainframe. Hosts in an EDL network are configured in a "star", with many subordinates clustered around a single master host. Administrative functions (user validation, part definition) are carried out on the master host. The DBA in the network is responsible for running a job (started with the command INITNET) which polls other hosts in the network (a subordinate polls the master, while the master polls each subordinate), then rolls out for a site defined period before repeating the polling cycle. This information is repeated in section 16 of the EDL Customization Guide. It is recommended that the System Administrator become familiar with that document before attempting these changes. 3.1 DEFINE HOSTS The default EDL database host name is blank. In order to identify multiple hosts in a network, each host must be given a unique name within EDL. This name should be the three character LID (Logical IDentifier) by which the host is known to RHF. One host should be designated as the MASTER host for the network. This host must communicate directly to all subordinate hosts which run EDL. All administrative functions, such as validating users, and defining parts, and vendors, will be done on this host, and the information will be passed to the subordinates. All transactions dealing with data are done on the subordinate hosts, and then passed up to the master. Therefore, the master host will contain information about-the data on all subordinate hosts. ... __._-_.- - - - - 3-2 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY 1.2.5 INSTALLATION INSTRUCTIONS NOS 2 Level 664 3.0 CREATING A NETWORK IN EDL 3.2 DEFINE COMMUNICATION LINKS 3.2 DEFINE COMMUNICATION LINKS CL records must be created for each host in the database, telling EDL which other hosts a specific host can communicate with. Note that each link must be defined twice, saying that HOST A can communicate with HOST B, and that HOST B can communicate with HOST A. 3.3 QU DIRECTIVES TO DEFINE A NETWORK A sample network could consist of two Cyber mainframes, and a Cyber 120 which does not run EDL, but whose data is managed by MA4 (whose data is passed up to MB1). Following are the QU directives to update the MASTER host (in this case MBl) for this network configuration. INVOKE EDLDATAW OF EDLDATA KEY $EDLORDBA$ USING E125DDB STORE SETTING HIHOS,HIOFF,HIOS,HIEDL,HIHOSS $MB1$ 1 $NOS$ $T$ $MB1$ $MA4$ 100000 $NOS$ $T$ $MBl$ $SD2$ 200000 $AOS/VS$ $F$ $MA4$ "'~END STORE SETTING UVUSR $EDLID$ $MA4$ $EDLID$ $MBl$ $EDLID$ $SD2$ $EDLCOM$ $MA4$ $EDLCOM$ $SD2$ $EDLCOM$ $MBl$ UVHOS UVOUN $EDLDBA $ $EDLDBA $ $DJH $ $EDLDBA $ $DJH $ $EDLDBA $ ,I~END STORE $MA4$ $MBl$ $MA4$ $MB1$ SETTING CLHOSS CLHOSR $MBl$ $MA4$ $SD2$ $SD2$ "'~END REMOVE USING UVHOS $ $ "'~END REMOVE USING HIHOS $ $ "'~END 3-3 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY 1.2.5 CUSTOMIZATION GUIDE NOS 2 Level 664 3.0 CREATING A NETWORK IN EDL 3.3 QU DIRECTIVES TO DEFINE A NETWORK MODIFY USING HIHOS SETTING HIOFF "SMB1S 0 "'END END Once the network has been defined on what will be the master host, this configuration should be copied to subordinates. EDL should be installed, then this same QU file should be run on each subordinate· host. EDL must run on the same NOS account on each host. 3.4 E125PRC MODIFICATIONS 3.4.1 PROCEDURES GETMAS AND GETSUB Procedure GETMAS and GETSUB contain .DATA files with MFLINK directives. These directives are used to poll alternate hosts in the network for information which should be sent from the master to the subordinates, or vice versa. The first line in the .DATA files are USER,EDLDBA,EDLDBA. This user statement should be replaced with the batch user statement for the username where EDL will be running in the network. Since the master host will be using these MFLINK directives to poll each subordinate, this means that the username and batch password where EDL runs on each subordinate must be the same. A recommended modification to the GETMAS and GETSUB procedures is to remove the .DATA files from E125PRC (which is available to all users running EDL) , put this information into a private file on the username on which EDL resides, and modify the procedures to read these files rather then the .DATA files. 3.4.2 PROCEDURE EDL Procedure EDL on file E125PRC must be changed on each host, telling EDL the name of the host. The updated procedure header will look like: -_.... __ •....._ - - - - - - _ .._... _......•._-_. 3-4 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY 1.2.5 CUSTOMIZATION GUIDE NOS 2 Level 664 3.0 CREATING A NETWORK IN EDL 3.4.2 PROCEDURE EDL . PROC, EDL, I=INPUT, IT=O/IT, OT=O/OT, HOST=hos ,AUN=.EDLDBA .. where. hos is . replaced by the name of the .host on which this file resides. This is the only change to E125PRC given host. which is specific to a· 3.4.3 EDL LOG FILES Each subordinate should have, on the username on which EDL is installed, a file called EDLSLOG. The master should have a file called EDLMLOG, and one file for each subordinate which runs EDL. These files will be called EDLMhos, where hos is replaced with the host identifier for the subordinate. These files should be public, or permitted to all usernames which can run EDL, in 'WRITE mode. These files contain log entries of each transaction which needs to be shipped either from the subordinates to the master, or vice versa. These log files are polled periodically by their destination hosts. 3.5 NETWORK INITIALIZATION The DBA should log into each host on the account where EDL resides, and' enter the command INITNET. This will start up a job which will: 1. 2. 3. 4. Poll the subordinates (or master) for transactions which should be sent to this host. Run EDL in batch mode to process these transactions. Rollout for the interval defined in the procedure NETROLL in E125PRC. Repeat. This job will have the UJN of" NETJOB. It should continue to cycle until the system is deadstarted, at which time the INITNET task should be run again. If the job is dropped, the transaction data is not lost. Network transactions will 3-5 CONTROL DATA CORPORATION 1987/01/30 ICEM ENGINEERING DATA LIBRARY 1.2.5 CUSTOMIZATION.GUIDE NOS 2 Level 664 3.0 CREATING A NETWORK IN EDL 3.5 NETWORK INITIALIZATION accumulate in the log fil~s, and. will be sent to other whenever the INITNET job is run on the receiving host. . _ - - _ . -.•_.-.......... -._... . hosts - - - _ ....... _"-,,....... _---,-_.,-" ...... ,.". - - - - 1 01/22/87 CONTROL DATA CORPORATION ICEM DDN Version 1.62 Operating System Level: Date: NOS 2.5.1 Level 664 1/21/87 SOFTWARE RELEASE BULLETIN DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Control Data Corporation gives the user permission to reproduce this document. Please call the following HOTLINE numbers if you have any problems or questions: 1-800-328-3980 1-800-527-0564 1-612-851-4131 U.S. Canada Minnesota and other international countries Please make this document available to all ICEM DDN users. SMD131371 1 21 JAN 87 Table of Contents 1.0 INTRODUCTION . • • • . . . . . . . • . . . . . . . . . . 1.1 ICEM DON V1.6 PUBLICATIONS STATUS • . •. . ..•. 1-1 . 1-2 2.0 VERSION 1.~2 FEATURE REVIEW . . • .. . •••• 2.1 ·DESIGN/DRAFTING FEATURES. . .•.. 2. 1. 1 HIGHLIGHTING . . • . . . . . .. .... 2.1.2 PLOTTING ENHANCEMENTS. . . .•. 2.1.3 ALTERNATE SCREEN POSITION INPUT. . ...•. 2.1.4 LOCAL ZOOM • . • • . • • •. . .•. 2. 1. 5 PATTERN MANAGEMENT . . . . . . . • . •. ...• 2.1.6 IPARTD ENHANCEMENTS . . . • . . • . • . . . . . . • 2.2 N/C FEATURES .• • • • . . . • . . . . 2.2.1 LATHE ROUGHING REWRITE . . . • • . .. . 2.2.2 N/C TOOLPATH MACRO: PTVAL STATEMENT ... . 2.3 GPL FEATURES . . • . . . . . 2.3.1 MSTRNG/MSFILE . • •. . .. . 2.3.2 LATHE ROUGHING . . .. ••.. ... . 2.4 PART SHARING UTILITIES. . . . . . ..• 2.4.1 IWOS UTILITIES. • • . . . • . ..... 2.4.1.1 ICEM Design/Drafting Part File Formatter (FORMIP AR TD) • . . • • . . . . . . .. .... 2.4.1.2 File Transfer Utility .......•. 2.4.2 NOS UTILITIES • • • . . . . ..... 2.4.2.1 ICEM Design/Drafting Part File Translators 2.4.2.2 File-to-File Transfer (XTRX170, XRECI70) . . . • 2-1 2-1 2-1 2-1 2-1 2-2 2-2 2-2 2-3 2-3 2-3 2-3 2-3 2-4 2-4 2-4 3. 0 COMPATIBILITIES • . • • . • . . . . . . . . . . . . . . 3.1 VERSION NUMBERS OF RELATED ICEM APPLICATIONS . . . . . . 3.2 ICEM DON UNDER IWOS . . • • • •. . .... . 3-1 3-1 3-1 4.0 INCOMPATIBILITIES, NOTES, AND CAUTIONS • 4.1 GENERAL ICEM DDN SYSTEM NOTES AND CAUTIONS . . . • • • • . 4.1.1 DDN PART NAMES ON IWOS AND NOS . . . • . 4.1.1.1 Using IWOS Host Part Sharing (ICEM MENUS) 4.1.1.2 Manual use of utilities . . . . . . . . . . . • 4.1.2 UNDOCUMENTED PATTERN UPDATE FEATURES . . . • . 4.1.3 MSTRNG COMMAND IN GPL • . • • • • . • . . • . 4.1.4 MSTRING WITH ALTERNATE SCREEN POSITION INPUT. 4-1 4-1 4-1 4-1 4-2 4-3 4-4 4-5 5.0 MANUAL CORRECTIONS • • • . • • • • • • 5.1 DESIGN DRAFTING DATA MANAGEMENT MANUAL 5.2 N/C MANUAL. . .•• 5-1 5-1 5-1 6.0 6.1 6.2 6.3 6-1 6-1 6-5 6-6 PSR/RSE • . •. . .••.••• PSRS CORRECTED IN THIS RELEASE • • • • • RSES INCLUDED IN THIS RELEASE . • • • NEW PSRS OPENED WITH THIS RELEASE 2-4 2-5 2-5 2-5 2-5 1-1 ICEM DDN V1.62 SRB 21 JAN 87 1.0 INTRODUCTION 1:0 INTRODUCTION This SOFTWARE RELEASE BULLETIN (SRB) site analysts and ICEM DDN users of: * is designed to inform New features in ICEM DDN ICEM products which must use V1.62 System notes and cautions PSRs/RSEs resolved/included with this release In addition, this SRB contains a set of replacement pages to correct and supplement the ICEM DDN V1.62 Reference Manuals. It is important that the V1.62 manuals be updated with these pages so that they are current and accurate. 1-2 ICEM DON V1.62 SRB 21 JAN 87 1.0 INTRODUCTION 1.1 ICEM DON Vl.6 PUBLICATIONS STATUS 1.1 ICEM DON V1.6 PUBLICATIONS STATUS The IC~ DON Reference Manuals hav~ been updated for the V1.62 release and can be ordered through Control Data's Literature Distribution Service (LOS). The following table summarizes the V1.62 manual update plans: MANUAL NUMBER NEW MANUAL or OVERLAY MANUAL CHANGE PACKET ICEM Design Drafting: Introduction and System Controls 60457130 rev L ICEM Design Drafting: Data Management 60461410 rev E ICEM Design Drafting: Basic Construction 60461420 rev 0 ICEM Advanced Design 60461430 rev 0 ICEM Design Drafting: Drafting Functions 60461440 rev 0 ICEM Numerical Control 60461450 ICEM Design Drafting GRAPL Programming Language Reference Manual 60461460 -ICEM GPL 60462520 NO MANUAL CHANGE rev 0 X rev C ICEM DDN Instant 60457140 X ICEM Tablet Overlays 60458080 X ICEM DON User's Guide 60456940 X 2-1 ICEM DDN Vl.62 SRB 21 JAN 87 2.0 VERSION 1.62 FEATURE REVIEW 2.0 VERSION 1.62 FEATUR£ REVIEW 2.1 DESIGN/DRAFTING FEATURES 2.1.1 HIGHLIGHTING In pre-VI.62 ICEM DDN, a selected entity is highlighted by placing an attention indicator ('0') somewhere on the entity. If that entity's attention point is zoomed or panned off screen, it is not possible to tell that it was selected. A new modal has been added to correct this problem. F.I.II.II HIGHLIGHTING METHOD offers two choice.s for highl ighting methods: ATTENTION INDICATORS and BLINKING. Attention indicators will continue to put the ('0') on the attention point of a selected entity. Blinking will cause a selected entity to blink on and off slowly. This feature only works for terminals with local display files which are turned on. 2.1.2 PLOTTING ENHANCEMENTS These changes allow us~ng a different paper type than that associated with the part and displaying a more descriptive main menu. The default paper type is based on the units of measure and drafting standard of the part. The alternate paper type will be requested with the Other Options key (CTRL-V or V). This causes a menu listing ·the various paper types to be displayed so that the desired type may be selected. 2.1.3 ALTERNATE SCREEN POSITION INPUT Alternate Screen Position Input is an advanced feature for ICEM DDN designed to remove some of the differences between running ICEM DDN interactively via a keyboard and running ICEM DDN by other methods, i.e., interactive MSTRINGs and MSTRINGs in GPL. Alternate Screen Position Input adds a new function key to --_.... _._-_._._--_._-----------------------_.. _.... _--.- ..--.-.- •....•.. _...... _._....•..........._.......... _..__.__ ......_.. _----- 2-2 ICEM DDN V1.62 SRB 21 JAN 87 2.0 VERSION 1.62 FEATURE REVIEW 2.1.3 ALTERNATE SCREEN POSITION INPUT ICEM DDN. With this key, screen locations may be specified without the use of the graphics cursor. Specifying screen locations using Alternate Screen Position Input is done by prompting the user for the location in transform or model coordinates. The function key for Alternate Screen Position Input is the 'I' key and may be included in MSTRING's just as other function key letters may be. The "I" key may also be selected when the graphics cursor is displayed in conjunction with prompts such as 'INDICATE ENTITY' and 'INDICATE POSITION'. 2.1.4 LOCAL ZOOM As in Diagonal Screen Positions, Local' Zoom permits the user to select the region to be zoomed by indicating the diagonal corners. Unlike Diagonal Screen Positions, Local Zoom displays the zoomed view with the terminal zooming capabilities, i.e., without a host repaint. Local Zoom is turned on and off through the Zoom menu (F.8.6.l8). This feature only works on terminals which have the local display file enabled (Tektronix 4107, 4109, 4115, 4125 and the CDC 790 Workstation). A local zoom done through the ICEM DDN menus provides for correct mapping of the tablet to the screen. Zooming done only wi th . the terminal function keys and not through ICEM DDN will not allow for this during selection. Local Zoom will automatically turn highlighting to blinking so' that selected entities can be clearly distinguished whether or not the attention indicator location is within the zoomed region. 2.1.5 PATTERN MANAGEMENT Pattern libraries will now contain no more than one drafting standard per pattern library. With 1.62, Pattern Update splits pre-1.62 patterns into separate libraries based on their drafting standards. Changes in pattern modals, pattern create, retrieve, list, and copy reflect and enforce this enhancement. 201.6 IPARTD ENHANCEMENTS The enhancements in 1.62 preserve the user's environment when the part is saved on an IPARTD file. When the part is restored from IPARTD, the user environment is the same as it was when the part was saved in IPARTD. 2-3 ICEM DDN V1.62 SRB 21 JAN 87 2.0 VERSION 1.62 FEATURE REVIEW 2.1.6 IPARTD ENHANCEMENTS The user" environment includes: *oJ, Viewing information General modals and fonts )" . Advanced des ign modals * Drafting modals * Entity selection modals * Viewing modals )" N/C modals With this enhancement, the IPARTD save/restore is as as the Global Parts save/restore. 2.2 2.2.1 complete N/C FEATURES LATHE ROUGHING REWRITE Lathe Roughing is the machining operation for removing large amounts of material from a material blank or a rough casting. The cuts in the operation are straight parallel lace cuts (they do not follow the finish part contour). The user must specify the original material boundary as well as the final contour shape. The two. new features in Lathe Roughing are variable offset and Generation Parameter Groups (GPG). Variable offset allows the contour geometry to be offset by different amounts in the X and Y directions. GPG allows the user to preset prompts in ~he user interface. 2.2.2 N/C TOOLPATH MACRO: PTVAL STATEMENT This feature adds to the macro writer the ability to associate the x,y,z,i,j,k values of the current point or of a named point to local variables. 2.3 GPL FEATURES 2.3.1 MSTRNG/MSFILE The MSTRNG statement enables the user to string through ICEM DDN menus beginning at the special functions menu,· enter data if necessary and optionally return to the next statement following it in the executing GPL program. All mstrings - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - _.._,._._.. ...... _.,_._... , , .. ,',...,.,...,.,.,.,... ,_..'_..... , .... _'. , - - - - 2-4 IeEM DDN V1.62 SRB 21 JAN 87 2.0 VERSION 1.62 FEATURE REVIEW 2.3.1 MSTRNG/MSFILE should begin with an 'F' to begin at the main menu, with the exception of mstrings intended for the special functions menu. Two definition forms give the user the options of specifying the menu string explicitly with. the GPL program, or of specifying the name of· an" existing menu string which resides on a local file. The MSFILE statement permits the user to change the name of the local, external file to be searched by all subsequent MSTRNG statements for the specified menu strings. An option for loading the original mstring filename into a GPL text variable is provided. This option allows the GPL program to reset the mstring file name before termination. 2.3.2 LATHE ROUGHING GPL provides the capability to create Lathe Roughing too1paths. This feature has been implemented by adding additional forms of the SETGPG and TLPATH statements. Inclusion of this feature within GPL, in combination with existing lathe commands, gives GPL a complete lathe machining functionality. 2.4 PART SHARING UTILITIES The IPARTD translators and related utilities are required to exchange parts between NOS- and IWOS-based IeEM systems. The translators reformat the independent part file IPARTD from 16 to 60 bit representation and from 60 to 16 bit representation. These utilities enable IeEM DDN users to transfer part files to and from NOS via a communication link to the host mainframe. 2.4.1 IWOS UTILITIES 2.4.1.1 IeEM Design/Drafting Part File Formatter (FORMIPARTD) This utility on the IWOS is accessible through the IeEM Host Part Sharing menu. It merges several single-part IPARTD part files into a multi-part file and formats that file for the IeEM DDN part file translator on NOSe The resulting output file may be sent to NOS via the fi1e-to-fi1e transfer or via magnetic tape medium. Reversing the process, the part file formatter takes from NOS 2-5 ICEM DDN V1.62 SRB 21 JAN 87 2.0 VERSION 1.62 FEATURE REVIEW 2.4.1.1 ICEM Design/Drafting Part File Formatter (FORMIPARTD) a transmitted file containing multiple parts and separates it into individual IPARTD part files. Each separated part file ~s formatted and placed in IPARTD . directory for ICEM DDN pr~cessing under IWOS. 2.4.1.2 File Transfer Utility This utility is accessible through the ICEM Host Part Sharing menu. It allows the user to transfer a part file to and from NOS and allows the completion status of the file transfer process to be checked. 2.4.2 NOS UTILITIES 2.4.2.1 ICEM Design/Drafting Part File Translators These utilities on NOS translate a part file from 16-bit IWOS machine representation to 60-bit NOS machine representation using the PFX1660 utility, and vice versa using the PFX6016 utility. These utilities may be controlled using ICEM Menus under IWOS. The current version accepts Vl.60 or Vl.62 parts from NOS and translates them to V1.6~ on the IWOS. Going the opposite direction it accepts V1.62 from IWOS and produces V1.62 parts on NOS. 2.4.2.2 File-to-File Transfer (XTRX170, XREC170) This utility is used only if the NOS-IWOS connection is through the HASP protocol. It is supplied with IWOS 2.X, and is controlled through ICEM Menus. Both IPARTD files and text files may be transferred through these utilities. 3-1 -ICEM DDN Vl.62 SRB 21 JAN 87 3.0 COMPATIBILITIES 3.0 COMPATIBILITIES 3.1 VERSION NUMBERS OF RELATED ICEM APPLICATIONS In addition to ICEM DDN, the following Application Products under NOS 2 have been updated to release level 664. All products are compatible with ICEM DDN Vl.62. Refer to the Software Availiblilty Bulletin for a brief description of new features/modifications included in each of the these products. DRAM Vl.l HASCO Vl.l ICEM BEND Vl.2 ICEM Engineering Data Library (EDL) Vl.2.S ICEM Facilities Vl.4 ICEM Hydraulics Vl.3 ICEM Kinematics Vl.0 ICEM Plastimould VI.I ICEM Solid Modeler VI~l3 IGES Translators V2.2 LINCAGES Vl.2 MOLDFLOW V4.0 MOLDSTAR VI.O 3.2 ICEM DDN UNDER IWOS ICEM DDN under IWOS executes as an application software package on the Application Processor (AP) under the control of the ICEM Workstation Operating System (IWOS). IWOS 2.X is a menu-driven operating system that includes the latest AOS/VS and associated software as well as ICEM menus and communications software. The IWOS version of ICEM DDN is based on the NOS version. The IWOS and NOS· implementations of ICEM DDN, while they are not identical, are compatible to the extent that they perform identi~al functions. In some cases, the user controls these functions in slightly different ways. 3-2 ICEM DDN V1.62 SRB 21 JAN 87 3.0 COMPATIBILITIES 302 ICEM DDN UNDER IWOS For details on the differences between ICEM DDN on IWOS and ICEM DDN on NOS, refer to the ICEM DDN under IWOS 20X SRB for Ve r sian 1. 62 • . 4-1 ICEM DDN V1.62 SRB 21 JAN 87 4.0 INCOMPATIBILITIES, NOTES, AND CAUTIONS 4.0 INCOMPATIBILITIES, NOTES, AND CAUTIONS There are no known incompatibilities between the version of any ICEM product and ICEM DDN under NOS. latest 4.1 GENERAL ICEM DDN SYSTEM NOTES AND CAUTIONS 4.1.1 DDN PART NAMES ON IWOS AND NOS 4.1.1.1 Using IWOS Host Part Sharing (ICEM MENUS) (a) From NOS to IWOS The IWOS part name is formed by the NOS part name characters 1-13 followed by a period, followed by the sheet number. The IWOS description field is formed by followed by NOS part name characters 14-60. name characters 61-70 are not retained. 13 blanks NOS part If in the NOS IPARTD file there are any parts where part name characters 1-13 and sheet numbers match, the last such part in the IPARTD file will be the ONLY part of among these duplicates that will be in the IPARTD directory on the IWOS. Duplicates are not translated. The user must look in the part sharing job log to check for possible problems. (b) From IWOS to NOS The NOS part name is formed by the IWOS part name characters 1-13 (not the IWOS IPARTD directory name), followed by the entire description field. The NOS sheet number is same as the IWOS sheet number. DDN on the IWOS allows the user to specify a 31-character IPARTD file name for the part. These file names can be used on the IWOS to differentiate IPARTD parts, but these file names are ignored when the IPARTD parts are translated. The part will be translated using the IWOS -_._.,,_ ...._.......... - ..... _... _. __ ._._._.. ._------------ 4-2 ICEM DDN V1.62 SRB 21 JAN 87 -------------------------------------------------------------------4.0 INCOMPATIBILITIES, NOTES, AND CAUTIONS 4.1.1.1 Using IWOS Host Part Sharing (ICEM MENUS) TAPE3 part name. This can lead to duplicate in the resulting NOS IPARTD file. part names Duplicate part· names are not overwritten. Once over to NOS, DDN will list all the IPARTD parts, but will .restore only ONE of the duplicates for the user. 4.1.1.2 Manual use of utilities These utilities are available on NOS and may be executed directly: PFX6016 PFX1660 (a) From NOS to IWOS The default IWOS part ~ame construction is the same as when these utilitites are executed on the IWOS. The user may ~upply an alternative to the default IWOS part name for each NOS part. The user-supplied IWOS part name may be up to 31 characters long. This allows users to avoid the IWOS problem of losing duplicate parts. (b) From the IWOS to NOS The default is the same as when these utilitites are executed on the IWOS. Duplicate part names are not overwritten. Once over to NOS, DDN will list all the IPARTD parts, but will only restore one of the duplicates for the user. The user may supply an alternative to the default IWOS part name for each IWOS part that is recognized by the translator. The user-supplied NOS part name may be up to 70 characters long. This allows users to avoid the IWOS problem of creating duplicate parts in the resulting NOS IPARTD file. 4-3 ICEM DDN V1.62 SRB 21 JAN 87 4.0 INCOMPATIBILITIES, NOTES, AND CAUTIONS 4.1.2 UNDOCUMENTED PATTERN UPDATE FEATURES 4.1.2 UNDOCUMENTED PATTERN UPDATE FEATURES When updating 1.60 pattern libraries, DDN separates patterns by drafting standard and creates a new pattern library for each available drafting standard. 'DDN will allow you to replace the old library with the new library. If you choose to update the patterns, the system displays the following prompt: ENTER NAME FOR NEW type LIBRARY where 'type' is the desired drafting standard (omitted if no drafting standard) If you enter the same name as the original library, the system displays: REPLACE OLD LIBRARY WITH NEW LIBRARY? Enter: Y To replace the old library with the updated library. N To avoid replacing -the old library with the new library The system again prompts with: ENTER NAME FOR NEW type LIBRARY (Note: Y can be entered for only one drafting standard. If it is entered a second time the following will be displayed: YOU CAN NOT HAVE TWO LIBRARIES WITH THE SAME NAME If some patterns cannot display a message: be updated, the system will UPDATE FINISHED nn PATTERNS UNABLE TO UPDATE If an error occurs and update replaces the old library with the new library the system will" display the following: ERRORS OCCURED DURING UPDATE - - - - - - - _.. __ __ .---_... .. .. _._--_ .. __._.._---_._--_ _............. . .. _._.... __..._.. _._._--_.._.... _ . _ . _ - - - - - - - - - - - - 4-4 ICEM DDN Vl.62 SRB 21 JAN 87 4.0 INCOMPATIBILITIES, NOTES, AND CAUTIONS4.1.2 UNDOCUMENTED PATTERN UPDATE FEATURES SAVE THE OLD LIBRARY? Enter : Y To copy the old lib~ary to a new file N To avoid saving any old patterns If you enterd Y to displays: save the old library the system ENTER NEW NAME FOR OLD LIBRARY If a file displays: with this name already exists, the system A FILE WITH THIS NAME ALREADY EXISTS The system then prompts you for library name: an alternative pattern ENTER NEW NAME POR OLD LIBRARY The old library will be saved under the new name. 4.1.3 MSTRNG COMMAND IN GPL 1. Upon entering DDN under the NOS operating system, the menu string file (default name MSTRING) will not be local unless the tablet is turned on. Therefore, an MSFILE command should proceed the first occurrence of HSTRNG/NAME, 'msname' in your GPL program. This will insure that the menu string file is made local before any attempt to read a menu string. 2. A GPL program should not be entered thru an MSTRNG menu string. 'If a menu string does execute a GPL program, control cannot be returned to the original GPL program. 3. Each lower case character in the HSTRNG menu string counts as 2 characters toward the 127 character limit for menu strings "defined explicitly within GPL. 4-5 ICEM DDN Vl.62 SRB 21 JAN 87 4.0 INCOMPATIBILITIES, NOTES, AND CAUTIONS 4.1.4 MSTRING WITH ALTERNATE SCREEN POSITION INPUT 4.1.4 MSTRING WITH ALTERNATE SCREEN POSITION INPUT 1. When using Alternate Screen Position Input with an MSTRING, you must not begin any line of a multiple~line' MSTRING with th~ 'I' character. 'Sample MSTRING: F.16.10.I.let5t.t5]t.tTHIS IS A NOTE]t Incorrect multi-line representation: F.16.10 I.1.t5t.t5]t.tTHIS IS A NOTE]t Correct multi-line representation: F.16.10.I.l t5t.t5]t.tTHIS IS A NOTE]t 2. ICEM DDN ignores the default entity selection method (see F.1.11.10) when executing MSTRINGs. The desired selection ~ethod must be specified each time selection is invoked. For example, the drafting note created above can be deleted by screen select .through Alternate Screen Position Input with the following MSTRING: F.3.1.1.I.l.t5.0t.t5.0]t 3. The Definition Space modal (1.15.2) does not affect Alternate Screen Position Input. You must ALWAYS choose model or transform space for each MSTRING. 5-1 ICEM DDN Vl.62 SRB 21 JAN 87 5.0 MANUAL CORRECTIONS 5.0 MANUAL CORRECTIONS 5.1 DESIGN DRAFTING DATA MANAGEMENT MANUAL 1. PATTERN UPDATE: Refer to the General ICEM DDN Notes and Cautions section for details on this manual change. 2. The attached sheets at the end of this section should be added to the ICEM DDN Data Management Manual as Appendix D. 5.2 N/C MANUAL 1. Page 6-16, Final Depth Calculation, PT to PT Explanation of ~rror messages is missing. lathe drilling for explanation. Refer to 2. Page 6-18, GPG Statement Append the following text to the end of this page. If the desired countersink diameter is larger than the diameter of the tool being used, you receive the following message: TOOL DIAMETER IS TOO SMALL The system then returns to the Tool Motion menu. Control If the pilot hole is too large to allow the defined countersink operation to occur, the following prompt is displayed: PILOT HOLE TOO LARGE The system then returns to the Tool Motion Control menu. 5-2 ICEM DDN V1.62 SRB 21 JAN 87 - 5.0 MANUAL CORRECTIONS 5.2 N/C MANUAL 3. Page 9-3, Editor Modals Change '2oCOOLANT' to '2.COOLANT MODE.' ~. Page 9-15, Editor Modals Menu items 2 and 3 should read: 2.TEXT LOCATION AREA 3.TOOL DISPLAY INCREMENT GRAPHICS N POINTS 5. Page 14-2, Sur£ace Milling Menu heading should read 'TOOL AXIS CONTROL.' 6. Page 15-2, 5-Axis Swarf Cutting Change '2.KEY-IN' to '2oENTER COORDINATES' Entry/Retract. Add '3.EXISTING POINT'. under 7. Page 15-4, 5-Axis Swarf Cutting After text for ~ption 4, add 'You will then proceed to the INDICATE TOOL TIP prompt.' 8. Page 17-1, Lathe Paragraph 4, last s~ntence should read: 'The available operations are roughing, contouring, drilling ,and threading.' 9. Page 17-9, Modify Generation Parameters First sentence: Change 'lathe drilling' roughing. ' 10. Page 17-14, Modify Generation Parameters Menu item 7 should read 'FROM AND RAPTO.' 11. Page 17-21, Modify Generation Parameters Change 'RAPTO ••• ' to 'RAPTO SETPOINT.' 12. Page 17-24, Threading to 'lathe 5-3 ICEM DDN V1.62 SRB 21 JAN 87 5.0 MANUAL CORRECTIONS 5.2 N/C MANUAL Change 'TOOL APPROACH, FINISH, AND to 'THREAD ANGLES AND CENTERLINE.' RETRACT MODES' In the second column, replace the first sentence with 'Specify the approach, finish,. retract, . and clearance angles. 13. Page 17-24, Threading Change 'TOOL ANG' to 'ANGLES.' 'PRE-GEN INSERTS' prompt missing.at the end • . '- - - - - _.. _---_. __ ._,_._ .... .. , ,._- ...... _ - - - - - - - - - - _ ...- .... '_._._---- 5-4 APPE~Q!~~~ATA MG~MANUALl PART SHARING VIA MAGNETIC TAPE BETWEEN CYBER 120 AND 170 Parts created on the CYBER 120 may be used on the CYBER 170, and parts created on the CYBER 170 may be used on the CYBER 120. Because of differences in (1) naming conventions, (2) file structure and (3) data format between the CYBER 120 and the CYBER 170, a part file from one type of system must be processed to translate each of these differing characteristics before it can be used by the other. When a CYBER 120 and a CYBER 170 are connected by data communication, you can use RHF/X.25 or HAMLET to move parts between systems. By selecting Part Sharing under ICEM menus on the CYBER 120, you can specify the source and destination file names, and all of the translation and file transfer operations are performed automatically. When there ls no wire connection between systems, the most convenient way to share parts is by magnetic tape. This appendix describes the operations a CYBER 170 user must perform to (1) prepare a parts tape on the 170 for use on a CYBER 120; and (2) process parts data from a 120 parts tape and move it to the 170 parts data base. A summary of the operations performed by the 120- user is included as an aid to understanding the process. - PREPARING A PARTS TAPE-ON THE CYBER 170 FOR USE ON THE CYBER 120 To prepare a series of parts for use on a different model CYBER system, you first save each of them from within ICEM DON, using 6.1.9.IPARTO MANAGEMENT, to create a system-independent version of the part file. Next, you convert the CYBER 170 data format of the flle to CYBER 120 £ormat using a program called PFx5016. 'PFX6016's output .1s a disk flle. The final step is to create a magnetic tape that contains the data from the PFX6016 output file. MakIng an IPARTD File Start DDN 1n the normal manner. Specify the name of the £irst part you want to put on the tape. When it has-10aded 7 select 6.1.9.IPARTD MANAGEMENT, and save the part. Repeat the process for each of the parts you want to put on the tape. Converting to CYBER 120 Data Format --._._--_.. _--_.. ------- 5-5 .. To run PFX6016, use the following commands at the NOS prompt (/ or READY): ATTACH,PFX6016 PFX6016,fn1,fn2,fn3,T,O,maxerr £n1 1s the name of the CYBER 170 IPARTD file to be translated. If you do not specify a name, the p~ogram looks for IPARTD. fn2 1s the name of the translator CYBER 120 format output file. If you don't specify a name, it will be named IPD120. £n3 1s the name of the file where diagnostic messages will.be written. If you do not specify a name, it will be named OUTPUT. maxerr is the maximum number of diagnostic messages to be written in fn3. If you do not specify a number, the maximum is 100. The program displays the following messages: ICEM DON PART FILE TRANSLATOR (CYBER-170 TO CYBER-120) PROCESSING: part name NO: sheet number SHEET NON-FATAL ERRORS • number FATAL ERRORS • number ~able E-1 shows the error messages for PFX6016 and PFX1660e WrIting a Tape write the information in the PFX6016 output file to tape, use the following commands at the NOS prompt (/ or READY) : ~o RESOURC,PE.1. LABEL, r1TAPE ,1)=1600, F.S ,LB-KU, VSN.vsnlist, PO.W. COpy,I.fn'O~T~~E,TC.EOF,BS.256,PO.R. vsnl1st 1s the volume serial numbe~ or numbers you assign to identify the tape. If you are preparing a multi-volume tape, separate the volume serial numbers with 'I'. ~D 1s the name of the output disk file from PFX6016, IPD120 or the name you specified above.· You have created a tape that can be used on the CYBER 120. ~be £ollow1ng information on how the data is further 5-6 .. processed at the CYBER 120 site is intended to help you understand the whole process. FURTHER PROCESSING AT THE CYBER 120 SITE Two char~cterlstics of the parts file must be changed at the CYBER 120 site before the parts on the tape can be used by ICEM DON. (1) The IPARTO file format must be changed from one part per record (multiple parts per file) to one par:t per file as required by the CYBER 120 version of ICEM DON. (2) The file names and/or part names must be changed to accommodate the differences 1n name lengths allowed on the two systems. One program called FORMIPARTO, running on the CYBER 120, does both jobs. Converting the IPARTD File To convert an IPARTD file from CYBER 170 to CYBER 120 ~ormat, you use FORI~IPARTO to split the IPARTO file into multiple, single-part files. At the same time, FORMIPARTO converts CYBER 170 70-character part names to CYBER 120 31-character part names, which become the individual IPARTO 1'ile names. You will find detailed instructions for converting CYBER 170 IPARTO files to CYBER 120 format in the ICEM DON DATA MANAGEMENT FOR AOS/VS Refer~nce Manual. - PROCESSING AN INCOMING CYBER 120 IPARTD TAPE An IPARTD tape received from a 120 site has already been converted 80 that there are multiple parts per file, one part per record. There are three steps ~ema1n1ng. First,. you read the tape into the system. Next, you convert the CYBER 120 data format of the file to CYBER 170 data format using a program called PFX1660. Finally, you restore the part from a CYBER 170 IPARTD file into your workspace using 6.1.9.IPARTD MANAGEMENT. From there, you can save the part on TAPE3. or perform any other ICEM DON operation on it. Reading 8n IncomIng IPARTD Tape To read a CYBER 120 IPARTD tape. use the following commands at the NOS prompt (lor READY): RESOURC,PE~1. LABEL, MTAPE, 0=1600 t F.S, LB.KU t po=!{ •. COPY,I-MTAPE,O=fn,TC.EOF,BS-256. REWIND,!n. PACK,fn. " . _.'.__ .n....________... _m._ .. _.. ___ .. n. ", ... "_.""_.,. __ ... ,..". ",,,,. '__"'''-'_''--_'_- -. -", . __.- ... _, .............- .-.-.. ----...-,,-----,-.-.--- ". ,.........,. .. .-,... "...... ",,_ ..... ,'-' .... ..."._,_ ..._-"".".,--"'---_."-'-'----'-,.. ,, ,,,._ ...--' ., .. _-,. __ ...._, .. -_."... _.........,-_.... ,,----_._--_.. , 5-7 £n is the disk filename into which you want the data from the tape to be copied. You can save some keystrokes later by naming.it "IPD120". Converting to CYBER 170 Data Format To run PFX1660, use'the following commands at the NOS prompt (/ or READY): ATTACH,PFX1660 PFX1660,fn1,fn2,£n3,T,O,maxerr £n1 1s the disk filename you specified above. If you do not specify a name, the program looks for "IPD120". fn2 is the name of the output file to be produced by PFX1660. If you don't specify a name, it will be named "IPARTD". fn3 Is the name of the file where diagnostic messages will be written. If you do not specify a name, it will be named OUTPUT.· . maxerr Is the maximum number of diagnostic messages to be written in fn3.· If you do not specify a number, the maximum is 100. ~he program displays the following messages: ICEM DON PART FILE TRANSLATOR (CYBER-120 TO CYBER-170) PROCESSING: part name SHEET NO: sheet number NON-FATAL ERRORS • number FATAL ERRORS • number Table E-1 shows the error messages for PFX6016 and PFX1660. You now have a file called "IPARTD" or the name you specified above. The file 1s in the proper form to be read by ICEM DON using 6.1.9.IPARTD MANAGEMENT. . '\ .' . 5-8 ' .. r.ble[)-'. 'F11660. P116016 ERROR K£~SACES Entity De.crlptlon Information (Pert.ln. only to .e,s.aea which reference • p.rticul.r entity) Non-fatal r.tal to r.rt Tr.n.latlon Fatal Error H.... ge INPUT. v ••• NOT SUPPOITED He.nina . DIRECTORY OVER.FLOW Thl ••••••,. c.n only .ppe.r when .xecutln, pr11660. It lndlc.te. that .ore than 91 part. are In the I'AATD fUe. x UNIECOCNIZED IPAlTD FILE Thl ........ can only appe.r vhen .xecutln. 'F16016. It Indicate. the IPAATD file doe. not have • directory (thl file to be tran.l.t.d i. not of .n IPAlTD foraat). x UNlECOC31ZED lECOID Incorr.ct record lenath. INT- lnt•• er valua (decJaal) Thi •••••• ,. can onl7 app.ar for ',X6016. Inte,er too l.r,. to tranal.t. to 16-blta. (V.lue .et to 32,767 or -32.768.) x TAIl, or 'L\I2 PAIT SPECIrICATIONS, CHAR- 2-dlllt hex.decl.. l cod. Thi ......,. can only .pp•• r for ,rX1660. Ch.r.ct.r coda doe. not .xl.t In CYIER 170 6-blt ch.r.ctar cod. r.pr ••• nc.tlon. Qu •• tlon .. rk 1. lub.tltuted for char.ctar. X PART SPECIfICATIONS, Entity x '.rt cr •• tlon v.r.lon not .upport.d by ,rX6016 or ·PFXI660. I LO Tran.lation Patd to FUe Tund.tioD x TAIl, tAl 2 • TAl3 or TAl4 PAIT SPECIFICATIONS. or ToU2 ,:" TAl3 or To\I4 ~ real value (decl.. l) TAl2 SEQ-anUty .. q. DO. TYPE-entlty type cod. FOItH-enUty fon (Method .,.ed to crute .ntlt,. ror ....pl•• polar coordinate. 1. an .nUty fom for the entity typ•• point) UHtIEFINED ENTITY TAl2 SEQ-.nUt, Hq. TYPE-.ntlty type rOlH-.ntlt, fo~ DO. TAl2 SEq-.nUty ..q. TYPE-.nttty type fORH-.ntJt, to~ DO. .. ....:,' TAl2 SEQ-entity ..q. ·no. TYPE-entity type FORM-antlty fon. (1) Eith.r .b.olute v.lue 1. ,r•• t.r tban X (1-16- 6 )x16 63 or .baolut. value 1• Ie •• th.n 16-65 • Cau ••• ab.olut. v.lu• to be I.t to'(1-16- 6 )16 65 or 16-63 • Entity type 1. not ona of thai. ll.t.d in fllur. 2-1. X mmErll1ED ENTITY PORH Unacc.ptable x RCTI' SUPPOJn'ED IN TAaCET SYSTEK Not currantly .upport.d. IEtoaD TOO LOMe The tr.n.l.t.d TAB2 than !ll2 word •• TY'~ fo~ for thla .ntlty. r.~ord X 1. Ir •• ter x ) 60459700 C L-21 •._,.._._ ........-._.. _ - - - - 6-1 ICEM DDN V1.62 SRB 21 JAN 87 6.0 PSR/RSE 6.0 PSR/RSE 6.1 PSRS CORRECTED IN THIS RELEASE THIS SECTION V1.62. CONTAINS PRIORITY CODE: C = U= S = M= PSR NUMBER PRI AD2A275 AD2A451 AD2A476 AD2A482 AD2A483 AD2A526 AD2A529 AD2A586 AD2A602 AD2A629 AD2A635 AD2A637 AD2A659 AD2A694 AD2A720 AD2A721 AD2A733 AD2A735 AD2A742 AD2A743 AD2A758 AD2A759 AD2A762 AD2A772 AD2A777 AD2A781 M U U M M M M M S S C U S M S S M S S M M M C S C M . _ .. _.- .._------_._-_.--_.,. ..... _.. - , A LIST OF PROBLEMS RESOLVED IN CRITICAL URGENT SERIOUS MINOR PROBLEM EXTRACT (7.1) TOOL PATHS SWITCHED FOR TWO VIEW DISPLAY CIRCLES CAUSE CIRCLE RECORD PROBLEMS IN CLFILE. (06.06) CY120-CY270 CAN'T SHARE PARTS CONTAINING FORMAT VIEW. (TERMINAL) 4114/ADM3 THE < AND > MARKS GET INCREMENTED TO THE RIGHT (6.1) PARTS WITH THREE AND FOUR DIGIT SHEET NUMBERS OVERPRINT. (12.3.6) AT INDICATE PT. FOR RHO -- OP REJECT WONT BACK YOU OUT. (6.5.4) OP.REJECT BOUNCES TOO FAR NO RESCALE WHEN DISPLAYING ENTITIES WITH ATTENTION ON RHO AND LOFT CONICS CANNOT BE CONSTRUCTED UNDER PRESENT CODE SURFACES NOT BEING BLANKED WHEN CREATING COMPOSITE SURF GET ERROR MESSAGE IN ROUGHING IN LATHE TRIM TWO ENDS WITH SPLINE AS BOUNDARY FAILS 6.1.10 IPARTD RETRIEVE LOSES SELECTIVE VIEW BLANK INFO LABEL USING SLOPE METHOD POINTS TO THIN AIR A CHECK CURVE LOCATED AT THE END OF AN ENTITY IS IN LATHE ROUGHING, THE FACING OPTION IGNORES THE VALUE PLOT COMPLETE MESSAGE DISPLAY WHEN EXIT WITH NO PLOT COORDINATES OF A TEMPLATE IN A MERGED PART ARE NOT ALWAYS CORRECT SURFACE PIERCE POINT FAILS ON A HALF SPHERE IN OFFSET CURVE, OFFSET DISTANCE DATA REQ SHOULD BE SPELLED OUT DUAL DIMENSION TEXT BRACKETS ARE MISPLACED ON THE RIGHT SMALL FRACTIONAL TOLERANCES ARE BLANK, SHOULD READ ZERO UAE IN INCREMENTAL POINTS [AND] AREN'T HANDLED PROPERLY IN ATTRIBUTE REPORTS 3D ANALYSIS RESULTS INCORRECT ATTENTION INDICATOR FROM THE BEGINNING OF STRING REMAINS ~'cSMALL ------ 6-2 ICEM DDN V1.62 SRB 21 JAN 87 6.0 PSR/RSE 6.1 PSRS CORRECTED IN THIS RELEASE AD2A793 AD2A794 AD2A795 AD2A799 AD2A800 AD2A8"01 AD2A803 AD2A804 AD2A816 AD2A819 AD2A820 AD2A821 AD2A822 AD2A831 AD2A832 AD2A843 AD2A846 AD2A847 AD2A852 AD2A853 AD2A856 AD2A858 AD2A859 AD2A863 AD2A864 AD2A865 AD2A866 AD2A871 AD2A872 AD2A875 AD2A949 AD22258 AD22365 AD22394 AD22535 AD22579 AD22671 AD22718 AD22772 AD22787 AD22795 AD22801 AD22802 AD22809 AD22811 AD22816 AD22824 AD22826 AD22828 ·C C C C S S S U C C C C C U S C U U U S U U S S U S S C S S M M U C S U U S M U M U M C S C C C S 9-DRILL. INCORRECT PULLOUT FEEDRATE WHEN MODIFIED IN GPG 9-CONT. INCORRECT TOOLPATH WHEN ALL GPG VALUES ARE MODIFIED CONTOURING MODIFY GPG- TOOLS IDE COORDS LOST TEXT DISPLAY .IN DIALOG AREA AND DYNAMIC T90L DISPLAY GIVE ERROR IN COMMAND MODE, MATRIX-COPY FROM FILE AND TOOLPATH FAILS MACROS USING A LITERAL STRING INSIDE OF AN IF STATEMENT SYS-AID CALLED IN 3-D ANALYSIS (18.4.1.1) GPL BULK STATEMENT WILL NOT EXECUTE SURFACE MILLING OF SOME CURVE MESH SURFACES - UNDEFINED ADR. 'DEPTH', 'DRIVE', 'TO' & 'LACE' W/ISLAND CAUSES 'GOTOER='. 'VIEW NORMAL', 'STOP', 'ON' W/WAVY SURF. - UND. ADD. EN C. SEVERAL INSTANCES OF SURFACE MILLING FAILING. MODIFY SCALLOP HT GIVE SYSTEM ERROR MESSAGE. SURFACE MILLING OF A CURVE MESH WITH CONTAINMENT FAILS. REPLACE DOES NOT WORK WITH CIRCLE STATEMENTS TEXT DISPLAY IN DIALOG AREA AND DYNAMIC TL DISP GIVE ERROR 5- AXIS SWARF CUTTING HAS REGRESSED--BAD TOOLPATH S. 'CSINK TO DEPTH' ISN'T CALCULATED CORRECTLY. F.9.17 FAN POINTS RESULT IN U.A.E. CL FILE INTERPRETATION OF INTOL AND OUTTOL ARE INCORRECT FOR LATHE CON GPG ERROR IN LATHE DRILLING GPG ERROR IN LATHE DRILLING INTERPRETTING CLFILES OTHER THAN APTIV MESSES UP 'PRINT' STATEMENTS. BAD 'GPL' TOOLPATH IF TOOLS ARE DEFINED AT DIFFERENT TIMES. GPL HANGS WHEN TRYING TO BLANK TOOLPATH AFTER 'PAUSE' GPL DOESN'T DELETE. A TOOLPATH GPL DOESN'T NAME TOOLPATH IF 'ASSIGN' FOLLOWS A 'QUERY' STATEMENT RESULTS FOR.2-D ANALYSIS (SELECTION 6,7,8) DEPENDENT ON SELECTION CONTROL D ON A PROJECTED SURFACE CAUSES UoAoE. THE MACRO 'IF' (EQ.) STATEMENT DOESN'T EVALUATE CORRECTLY CAN'T DELETE COMMON PATTERN FILES, ACL WRONG. SCREEN BLANKS ON 4114 TERMINAL WHEN CREATING A PRINTR FILE IN CLFILE 1.53 PROBLEM WITH DETAIL MAGNIFICATION 7010 BULKIN INPUT DOESN'T ACCEPT TEXT ANGLES ANY MORE, WRITES. F.10.9 LINE THROUGH POINT-PERPTO LINE CREATES A LINE OF 0 LENGTH. ENTITY DRAGGING SPLINE ANALYSIS PRINTOUT IS INCONSISTENT OFFSET CURVE (12.2.1) INCORRECT WITH TRANSLATED "OFFSET 2D SPLINE" DIMENSION TEXT ANSI 73 AUTO DIMENSION MODIFY TEXT-METRIC UNITS EDLLOG IS INCORRECTLY UPDATED WHEN GLOBAL PARTS RESTORE IS USED DDN: DETAIL MAGNIFICATION CONSTRAINT SETS MODE, SYS=1ST CALLED, AND GOTOER ERRORS. PROBLEM WITH 4125 AND 4957 TABLET 2D OFFSET SPLINE IS SOMETIMES WRONG SLOW PATTERN RETRIEVAL OF 1.6 PATTERNS TAPE 31 PART HAS 420 VIEWS, ARC CAN'T MERGE TO RENEW. DIMENSIONS WITH LAST CHARACTER X ARE FOLLOWED BY A COLON X: 6-3 ICEM DDN V1.62 SRB 21 JAN 87 6.0 PSR/RSE 6.1 PSRS CORRECTED IN THIS RELEASE AD22830 AD22855 AD22905 . AD22911 AD22912 AD22913 AD22960 AD22976 AD22978 AD22993 . AD23025 AD23027 AD23069 AD23076 AD23079 AD20826 AD20912 AD21174 AD21198 AD21203 AD21275 AD21479 AD21482 AD21488 U S C S C C C C C S C U C C S S S U U U C M S U AD21597 AD21780 AD22016 AD22017 AD22052 AD22085 AD22266 U U M S U S U AD22300 U AD22303 C AD22314 AD22321 C U AD22402 AD22467 AD22471 AD22491 AD22600 AD22630 AD22635 AD22663 AD22664 S S C U U C S U U GEOMETRY TOL FRAME DOES NOT POINT TO ENTITY IN VIEWS OTHER THEN #1 POINT TO POINT CAN,"' T RETRIEVE ALL PARTS FROM IPARTD FILE. F.7.2.1 ·AFTER PLOT ENTIRE PART, ENTITIES DISAPPEAR FROM'PART. RESTORE MORE THAN 8 PARTS FROM A GPARTS FILE CREATES A TRASHED EDL LOG RESTORING PARTS FROM A GPART FILE WRITES OUT AN INCORRECT EDL LOG UNABLE TO CREATE POINTS ON AN INTERSECTING CURVE. (19.2) RESIZE DOES NOT CONVERT DIMENSION TEXT ON DWGS FROM DDN 1.5X IPARTD FILE IS NOT CREATED CORRECTLY. F.7.2.1 MODE ERROR ON "PLOT ENTIRE PART" N/C VERIFY (F.17.11.4.9.3) ABORTS ICEM-DDN DRILLING (F.17.9.3) DDN WRITES TO EDLLOG EACH TIME AN MSTRING IS CALLED FROM A USER PAGE IPARTD RESTORE FAILS ZOOM NEW CENTER (F.8.6.2) / PLOTTING PROBLEM (17.6/7.1) WRONG DIRECTION FOR CLFILE TOOL AXIS VECTOR NC LATHE ROUGHING FACE CUT ORIGIN IS AMBIGUOUS PROGRAM STOPS ACCEPTING SCREEN POSITIONS LATHE ROUGH BORE PLACES ROUGH STOCK OFFSET ON WRONG SIDE (1.49X) BAD CLFILE OUTPUT OF AN ABSOLUTE TOOLPATH DATA BLOCK(1.49X) FSE INABILITY TO USE TEMPLATES IN DATABASE SAVES AND RESTORES LATHE ROUGH FACING OFTEN "FAIL TEKTRONIX 4115 DISPLAY CHARACTER SIZE IS CHANGED 'WHEN CD2000 IS EXITED (16.16)NEED MORE THAN 8 CHARACTER CAPACITY FOR DATUM (KEY IN NAME)ENHANCE 70 CHARACTER PART NAME "DELETE LAST ENTITY" SQUARE SHOULD BE MOVED SQUARE FOR TURNING Z-CLIP OFF (F.17.9) ICEM N/C LATHE FINISH STOCK NO CIRCLE RECORD OUTPUTTED FOR' LATHE ROUGHING CANNOT GENERATE ROUGH LATHE TOOLPATH WITH .03"RAD AND DEPTH OF CUT .02 BLANKED ENTITIES TRANSLATED/CHANGED LEVEL BY DUPL/TRANS OTHER ENTITIES SCREEN SELECT IS PICKING BLANKED ENTITIES NOT ELIGIBLE IN CURRENT TASK 2-D OFFSET OF A 2-D SPLINE ON 63-CHARACTER SET SYSTEM, A PERCENT SIGN IS CONVERTED TO A COLON THE USE OF CONTROL CHARACTERS F.10.9 THROUGH POINT PERPENDICULAR TO LINE 6.1.7 CHANGING SCALE AND ORIGIN ON PART MERGE DOES NOT WORK UNDEFINED ADDRESS ENCOUNTERED PROBLEM ICEMDDN CROSSHATCHING IMPOSSIBLE OPEN BOUNDARY BUG. SUSPEND FEATURE CUASES BAD IPARTD, HANGS PROBLEM F.6.1.11 PART INTEGRITY CHEC~/RENEW CAUSES 'MORE ERRORS 2/17/86 INTERPRET CLFILE WILL NOT WORK IF THE FILE CONTAINS MULTAX/ON CLFILE TRUNCATES POSTPROCESSOR STATEMENTS 6-4 ICEM DDN Vi.62 SRB 21 JAN 87 6.0 PSR/RSE 6.1 PSRS CORRECTED IN THIS RELEASE AD22667 U AD22668 S AD22669 S AD22690 ·S Ao22702 U AD22722 U .AD22726 S AD22728 ·S AD22729 S AD22730 S AD22746 C AD22771 M AD22779 C AD22781 C AD22788 U AD22819 C AD22820 C AD22823 C AD22831 S AD22861 C REPLACE STRING IN NC EDITOR DOES NOT REPLACE A NEGATIVE VALUE CAN NOT RAISE A NEGATIVE NUMBER TO A POWER IN TOOLPATH MACRO SAVE VARIABLES IN TOOLPATH MACRO VARIABLES HAVE COLONS IN RTL FILING OUT. OF DDN V1.60 INITIATES A NEW SESSION EXTENSION LINES BECOME UNMODIFIABLE 16.13.11 INTERPRET CLFILE DOES NOT WORK ON MANY APT CLFILES NC TOOL IMAGE WILL NOT DISPLAY IF (.) IS PART OF EDITED TOOL NAME WRONG ANSWER FOR FIRST MOMENTS OF INERTIA CALCULATIONS WRONG ANSWER FOR MOMENT OF CENTRIFUGAL WRONG ANSWER FOR MAIN AXES OF INERTIA MIXING OF TOOLPATH TYPES METRIC AUTO DIMENSION TOLERANCE AND LIMITS REFER TO PSR AD22775 SEE THE JUSTIFICATION NCPLIB FILE CAN NOT HAVE /JOB /USER /CHARGE COMMANDS IN THE JOB GPL NC LATHE PATH FAILS IF PRECEDED BY TEXT ENTITY GPL NC LATHE PATH MAY FAIL TO USE ALL SPECIFIED GEOMETRY HORIZ/VERT DIM ENDING EITH 'X' DOES NOT DISPLAY CORRECTLY NC GPG WARNING: INTOL/OUTTOL RESULTS IN 0.0 AND BAD TOOL PATH OCCUR. INTERSECTION CURVES 6-5 ICEM DDN V1.62 SRB 21 JAN 87 6.0 PSR/RSE 6~1 RSES INCLUDED IN THIS RELEAsE 6.2 RSES INCLUDED IN THIS RELEASE THIS SECTION CONTAINS A LIST OF FEATURE ENHANCEMENTS FOR V1.62. PRIORITY CODE: U URGENT S = SERIOUS M = MINOR PSR NUMBER AD21419 AD22776 AD22833 .. --'--_.. _'--" ..... PRI PROBLEM EXTRACT S TEKTRONIX 4115 LOCAL ZOOM SUPPORT U UNABLE TO RESTORE IPARTD FILES U ENTITY SELECT ATTENTION MARKS ARE VERY POOR FOR SURFACE TOOL PATHS _._-----_ ..-,.. _..._.,........_- --._._-_._....._-_.. - ..... ' _. - . __.-.------_._---_._... ..,, .. ------_.,_ .... _...... _..----_._..- .. 6-6 ICEM DDN V1.62 SRB 21 JAN 87 6.0 PSR/RSE 6.3 NEW PSRS OPENED WITH THIS RELEASE 6.3 NEW PSRS OPENED WITH THIS RELEASE THIS SECTION CONTAINS A LIST OF NEW PROBLEMS IN V1.62. PRIORITY CODE: C = U= S = M= PSR NUMBER AD2A95 0 AD2A951 AD2A952 AD2A953 AD2A954 AD2A955 AD2A956 AD2A957 AD2A958 Ati2A959 AD2A96 0 AD2A961 AD2A962 AD2A963 AD2A964 AD2A965 AD2A966 AD2A967 AD2A968 AD2A969 AD2A971 AD2A972 AD2A973 AD2A974 AD2A975 AD2A976 AD2A977 AD2A978 AD2A98 0 AD2A981 AD2A982 AD2A987 AD2A988 CRITICAL URGENT SERIOUS MINOR PRI PROBLEM EXTRACT S U S U S S U S S M S M S S S M U S U U M M S M M S U M S S U U S POCKET DOES NOT COLLAPSE IF CHAIN SELECT NOT RIGHT CAN'T READ COMMON ARRAY USING GPL SYSTEM COMMAND INSERT WITH DOLLAR SIGN FOR CONTINUE FAILS MACRO COpy IS NOT SAVED FOR CLFILE GENERATION LABEL LEADER LINE POSITION BAD THICKNESS DIM. BETWEEN FILLETS SYSTEM COMMAND IN GPL WON!T READ TAB! INFO. COMPILER DOESN'T CHECK FOR CORRECT FORMAT GPL TAB3 INFORMATION IS DIFFERENT THAN INTERACTIVE GROUP UNBLANK DOESN'T APPEAR UNTIL AFTER A REPAINT PRINTOUT FOR 5.6.7 IS INCONSISTENT WITH REF MANUAL SUB-ATTR NAME # INCREMENTS INCORRECTLY IN SSI-FAILS TO FIND COMPLETE INTERSECTION STATEMENT ••. INSERT/' [###] , DOESN'T WORK USING ED. LIST OF CONSTRAINT SET GIVES WRONG INFORMATION CONSTRAINT LISTING SAYS INCLUDE INSTEAD OF EXCLUDE STRETCH WINDOW-RESIZE DOESN'T GIVE CORRECT STRETCH WINDOW-MOVE MOVES THE PART TOO FAR ELLIPSE EVAULATION HANGS IN A LOOP • AND. , .OR., .NOT., ILLEGAL CODING PRACTICES FILLET TO 4 LINES ONLY CREATES 3 ARCS HOST REPAINT REQD TO RESTORE ENTITY COLORS TRIM TWO CURVES AT INTERS. DOES NOT ALWAYS WORK INDICATORS FOR 'WORK VIEW' DO NOT DISAPPEAR HOST REPAINT REQD AFTER REDEFINING TEMPLATE MASTER HOST REPAINT REQD AFTER SELECTIVE VIEW BLANKING PATTERNS NOT RETRIEVABLE ON FORMAT VIEW REGION OUT SELECT OF GROUPED ENT. DOES NOT WORK BLANK-SELECT DOES NOT BLANK ALL ENTITIES ON lEW GENERAL CONIC HAS INCORRECT TAB DATA DELETE LAST ENTITY LEAVES ISO DRAFTING ENT ON·SCRN MSTRING-MULTIPLE LINED MSTRING FAILS USING A CIRCLE FOR CLOSED BOUNDARY FAILS IN SURF M ,. 6-7 ICEM DDN V1.62 SRB 21 JAN 87 6.0 PSR/RSE 6.3 NEW PSRS OPENED WITH THIS RELEASE AD2A991 AD2A992 AD2A993 AD2A994 AD2A995 AD2A996 AD2A997 AD2A998 AD2A999 AD2B001 AD2B002 AD2B003 AD2B004 AD2B005 AD2B006 AD2B007 AD2B008 AD2B010 AD2B011 AD2B012 AD2B013 AD2B014 AD2B015 AD2B016 AD2B017 AD2B019 AD2B020 AD2B029 AD2B030 AD2B031 AD2B036 AD2B038 AD2B055 AD2B056 AD2B059 AD2B060 AD2B061 AD2B063 AD2B064 AD2B065 AD2B066 AD2B067 AD2B068 AD2B069 AD2B070 AD2B071 AD2B072 AD2B073 AD2B074 .-._--_._--- -,," S C C U S M U U U U U U C U S S S U U M M U M M U S C U U U U U M U C S S U U S S S M S M M M' M M ROUGHING - FOLLOW CONTOUR OPTION REPEATS CUTS EDGE INTERSECTION NOT FOUND. INTERSECTION CURVE NOT USABLE DIFFICULTY FINDING ~NTERSECTION CURVE. NO START SI FOUND WHEN SURFACES CLEARLY INTERSECT EDLLOG DOES NOT KNOW ABOUT MOLDCOOL FILES NO RETRACT ON 5 AXIS 2 SURF. PROFILE WRONG START AND INCOMPLETE PATH 2 SURF. PROF. INITIAL CLEARANCE MOVE GOUGES PART UAE DISPLAYED WHEN SELECTING CONTAINMENT. CONTAINMEN T OFF SURFACE ABORTS TO MAIN MENU. MODIFIED SIDE STOCK VALUES CORRUPTEED TOLOLPATH. NEW ATTRIBUTES DEFINED CLOBBERS OLD ONES ON FILE. ASPI ALLOWS LOWER CASE NOTES WITHOUT TILDAS GRAPL ATTRIBUTE MANAGEMENT CAN'T FIND INTERSECTION PT. BETWEEN SPLINE & FAN POINTS NEED REPAINT TO BE DISPLAYED MACHINE CURVES DO NOT ALWAYS TRIM PROPERLY. IPARTD DOESN'T SAVE CHAR. SET AND LEVEL TABLES. GPG ACCEPTS NUMBER WHEN DEFINING FILLET ON WRONG SIDE OF LINES PROFILE FAILS WITH INTOL/OUTTOL .00002 ARC ROUTINE PICKS UP RADIUS VALUE FROM OTHER MENU POCKET NONE ON PRE-GEN INSERTS-GET THEM ANYWAY CLFILE - COMMENTS IN EDITOR CAUSE ERROR IN CLFILE CERTAIN PREGEN INSERTS CAUSE ERROR SEE DAYFILE SWARF CUT DOESN'T MACH. SURF. COMPLETELY ON NOS/AOS. WRITE ON READ ONLY GPG FILE CAUSES ERROR CONTAINMENT - GOTO POINTS NOT TANGENT TO LINE MANAGE FILES TURNS OFF TABLET WHEN RESTARTED FAN POINTS ON ELLIPSE INCORRECT SELECTED PROFILE CAUSES ERROR AND MENU LOCK UP ATTENTION INDICS GOTO STORAGE ON T4114 EA PERIMETER CALCULATION ERRORS SURF.MILL 'GOTOER' ON NOS, 'UAE' ON AOS. REPETITIVE FEATURES MODAL GIVES INCORRECT LIMIT TOL. PART BOUNDARY IS BEING VIOLATED. SNIGLE SELECT FROM GROUP DOES NOT WORK SPACE MISSING BETWEEN TOLERANC~ AND R COUNTERSINK AND COUNTER BORE SYMBOL REQUIRE SPACE THE SPHERICAL DIAMETER SYMBOL S IS TOO CLOSE ZOOM AUTO MAX MIN HAS TO BE ENTERED THREE TIMES TO GEN DEFAULT VALUE FOR DEPTH IN SURFACE MILL SHOULD BE RESIZE OF FT/INCH DIMENSIONS GIVES EXTRA INCH MARKS NO HELP AVAILABLE FOR EXECUTE A MACRO NO HELP AVAILABLE FOR ENTERING OUTPUT MACRO FILE NAME N/C EDITOR DOES NOT ALLOW. INSERT OF CONTINUED STATEMENTS ERRONEOUS MACRO CONTINUATION STATEMENTS ARE WRONG CONSTANTS DISAPPEAR ON PARTNO/, INSERT/, AND PPRINT/ LINES ----,,_._-,-_._--, '''-- -- '",,-"'''''- --'- ' -----,--"... "'-"".-------- 6-8 ICEM DDN V1.62 SRB 21 JAN 87 6.0 PSR/RSE 6.3 NEW PSRS OPENED WITH THIS RELEASE AD2B075 AD2B077 AD2B079 AD2B081 AD2B082· AD2B083 AD2B087 AD2B088 AD2B089 AD2B090 AD2B092 AD2B093 AD2B094 AD2B096 AD2B097 AD2B099 AD2B100 AD2B101 AD2B102 AD2B103 AD2B105 AD2B108 AD2B110 AD2Bl12 AD2B113 AD2B114 AD2B115 AD2B116 AD2Bl17 AD2B118 AD2B119 AD2B120 AD2B121 AD2B122 AD2B123 AD2B124 AD2B125 AD2B126 AD2B127 AD2B129 AD2B130 AD2B133 AD2B136 AD2B137 AD2B138 AD2B139 M S S M M M M S S U C C S M S U S S S S S S S M M M S S M M M M M M M M S M S U M M M M S M MACRO EXECUTABLE LINE LIMIT REACHED NOT PROMPTED CRE INC PTS ALONG CURVE GETS WRNG PARAH FM INDIC POS RETRACT=NONE (POCKET) CAUSES LOOP UNDER 'LIST CONTROL-~ ON MAIN EDITOR MENU WORKS INCONSISTENTLY HELP MESSAGE FOR MAIN" EDITOR MENU IS NOT ALWAYS CORRECT TOOLPATH MUST BE NAMED OTHERWISE 'BLINKING' DOESN'T CHAIN SELECT FOR FILLET CURVES IS AWKWARD ROTATE ENTIRE PART DOESN'T PART BOUNDARY IS VIOLATED AT DIFF. SCREEN POSITIONS. GPL ZOOM SCALE ONLY SCALES WORK VIEW ON MULT. VIEW DISPLAY SURFACE HAS AN UNDESIRABLE LUMP IN IT YOU GET LINEAR BLENDING WHEN YOU REQUEST TWIST TAB3 MEMORY CAN BE EXCEDED WITHOUT EXPLANATION TO THE OFFSET SURFACE DOESN'T WORK WELL WITH SSI CLEARANCE DISTANCE AND FINAL DEPTH ERRORS IN LATHE UNABLE TO RESTORE IPARTD PARTS WITH 4 DIGIT SHEET NUMBERS GPL PROBLEM WITH CHOICE VARIABLE IN MENU COMMAND GPL PROBLEM WITH PATTERN COMMAND PROBLEM WITH GPL PATTERN RETRIEVAL AND BALLOON COMMAND SUGGESTIONS ON GPL SECTION OF MANUALS ADD TOLERANCE NOT WORKING FOR ZERO METRIC CONDITION DRILL LIP REFERENCE POSITION DOESN'T WORK FROM GPL GPL NC GIVES GOTOERR WHEN. NEEDED NAMED POINT IS NOT DEFINED 'FINAL DEPTH CALC.' IS MISSING ERROR MESS. (P.6-18 '5-AXIS SWARF CUTTING' HAS SOME ERRORS IN THE MANUAL 'SURFACE MILLING' HAS SOME ERRORS IN THE MANUAL. UAE WHEN VERY LARGE NUMBER OF SURFACE PATHS (U,V) DEFINED. GPG LIST IN DIALOGUE AREA FAILS UNDER CERTAIN CONDITIONS. WORD MISSING IN MANUAL UNDER 'N/C MODALS'. EXTRA WORDS IN MANUAL UNDER N/C MODALS-EDITOR WRONG STATEMENT UNDER 'LATHE' IN MANUAL. EXAMPLE LISTING DOES NOT MATCH STATEMENT. EXTRA WORD IN MANUAL UNDER 'MODIFY GENERATION MANUAL IS MISSING A WORD IN 'LIST CURRENT SETTINGS' MANUAL HAS CERTAIN THREADING SEQUENCE TURNED AROUND. 'LIST CURRENT SETTINGS' EXAMPLE NOT THE SAME AS USERS MAY ATTEMPT TO EXCEED MAX NUM OF IPARTD PARTS ALLOWED MAX NUM OF ALLOWED IPARTD PARTS IS BURIED IN ERROR IPARTD FILE DATA IS ~ORRUPTED WHEN USER EXCEEDS MAX PARTS 'SWARF CUTTING' PRODUCED BAD TOOL AXIS VECTOR ON FINAL NOS DATA MGMT MANUAL APPENDIX D HAS MINOR TYPING ERRORS NOS DATA MGMT APPENDIX D MISSING IPARTD TAPE PROCESS NOS DATA MGMT APPENDIX D DIRECTS USER TO ENTER A CCL WRONG HELP MESSAGE FOR F.I0.14 SUSPEND ON A 721 TERMINAL DOES NOT RETURN IN GRAPHICS DELETED PART DOES NOT DISAPPEAR UNTIL REPAINT 1 1987/01/15 CONTROL DATA CORPORATION ICEM ENGINEERING DATA LIBRARY V1.2.5 Operating System Level: NOS 2 Level 664 Date: 01/15/87 SOFTWARE RELEASE BULLETIN DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features and parameters. Control Data Corporation gives the user permission to reproduce this document. Please contact the appropriate Hotline if you encounter any problems or have any questions. US outside of Minnesota 800-328-3980 Minnesota and International 612-851-4131 Canada 800-527-0564 SMD131365 1 CONTROL DATA CORPORATION 1987/01/15 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 664 Table of Contents 1.0 INTRODUCTION 1-1 2.0 NOTES AND CAUTIONS 2-1 3.0 PSR/RSE CORRECTIVE CODE. 3-1 . __ .-_.._ - - - - - - - - _... _ . - - - - - - - - - - - - _. 1-1 CONTROL DATA CORPORATION 1987/01/15 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 664 1.0 INTRODUCTION 1.0 INTRODUCTION Version 1.2.5 of the Engineering Data Library incorporates the following new features and enhancements: 1. Compatible versions of EDL V1.2.5 on both NOS and IWOS (AOS/VS) ICEM delivery vehicles. 2. An improved and expanded documentation that includes a new User's Guide and EDL Command Instant. 3. The interactive task MENUMOD has been added to facilitate the customization of EDL's tasks, menu and option messages. These features are the first of an evolving 'Customization Toolkit' for EDL. 4. Improved Customization Guide with more examples and explanations about all aspects of EDL customization. 5. An updated version of IMF 2.1 that addresses all known runtime problems with the IMF data manager. - - - _.._--_ .._.... _ .. _ ...._._------_ ... - - - - _.............. __. _ - 2-1 CONTROL DATA CORPORATION 1987/01/15 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 664 2.0 NOTES AND CAUTIONS 2.0 NOTES AND CAUTIONS 1. On entering EDL, if the user's logged in NOS user name is different than the NOS username in the EDL database, a warning message is displayed. Files created under this condition will not be accessible when the user is logged into the correct username unless the files are specifically permitted to the user. 2. Updating EDL for new files requires you to be running on the NOS username where the file resides. EDL assumes that all new files are private files. If the file is actually a NOS public file, use the EDL PERMIT task to change the file category to PUBLIC. 3. To install data files on a system username such as APPLLIB or LIBRARY, when a SUI statement is used to access the account, use UPDATE EDL FOR ENGINEERING DATA to add the information to EDL, then use CORRECT FILE INFORMATION to change the NOS username of the file to the right username. 4. An indirect access permanent file named USER must exist on the user's NOS username if the user wishes to use TRANSFER tasks on Solid Modeler data. The file USER contains the job card, user card, and accounting charge card image if needed. 5. If two users attempt to update the same EDL record at nearly the same time, a concurrency conflict may occur for the second user. An error message will be displyed and EDL will return to the previous task menu. The user should reobtain the data to determine what change was made by the other user and try the update again if appropriate. 6. If the user uses a Control T to abort Query Update using IMF, occasionally the user job hangs and cannot be dropped. It may be necessary to do an override from the console to drop the job. 7. In a multi-host network, it is not possible to transfer data to a remote host when using the ACCEPT or RELEASE tasks. Data may be submitted to a release procedure _...... - .. -. __._ .. " ._---- ------_ ........... _._-- . ---_ .... _--- 2-2 CONTROL DATA CORPORATION 1987/01/15 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 664 --------------~--------------------------------------- -------------- 2.0 NOTES AND CAUTIONS from any host on the network, but to ACCEPT or RELEASE the data, the releaser must run on the host where the pending or released destination data is desired to reside. 8. Using the EDIT command on non-permanent files or creation files will prompt the user for the character code to be used to edit the file, UPPER CASE DISPLAY CODE or UPPER LOWER CASE ASCII. 9. The correct file type for PATRAN PATDAT, is RANDOM ACCESS DATA. DATA, local file 10. In using the transfer tasks involving an IGES DATA FILE, the user must use the correct data name of the origination file or the destination file. The IGES data name specified must match the origination data name. The transfer data name specified must match the data name in the IGES file, or if the name in the IGES file is blank, the default data name IGES. 11. In a network configuration consisting of two or more hosts where a host is not available, the IMPORT and EXPORT commands will require a control-t to exit the wait status. This will not exit the user from EDL. 12. The reference manual states that a part number cannot be deleted if any released data is associated to the part. In fact, the part cannot be deleted if any data is associated to the part, regardless of the status of the data. 13. The default core memory field length to run EDL V1.2.5 is 175,000 octal. If EDL aborts due to maximum field length (MFL) exceeded, then edit the procedure file E123PRC, procedure EDL, to change the command MFL,175000 to increase the amount of memory allowed for EDL and IMF. 14. The EDL relocatable libraries are compiled at NOS 2.5.1 level 664. If your site is using an earlier version of NOS and the product sets, there may be incompatibilities ._--._-._- . _._._----_.__ ...__.. __. _ - - 2-3 CONTROL DATA CORPORATION 1987/01/15 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 664 2.0 NOTES AND CAUTIONS between the EDL libraries and the system libraries. This may cause problems if the EDL absolute is reloaded using the LOADEDL procedure to include site-written Fortran code. If this situation occurs at your site, upgrade the product sets of your site to level 642. 15. When a permanent file (PF) utility is running, EDL may abort if IMF tries to create a file. User catalogs that have a user index ending in the same number as the user index of the IMF user name will be locked until the PF utility has completed and IMF will not be able to create or extend the files it uses for it's operations. To prevent a possible loss of data, it is recommended that the system administrator be notified when PFLOAD or PFDUMPs are to take place so that they can monitor and coordinate the use of EDL while these utilities are in use. 16. The procedure IGTCEI on EI25PRC, which transfers IGES DATA to EXTERNAL IGES DATA, has been modified to write the EXTERNAL IGES DATA to tape. The procedure EITCIG on E125PRC has been modified to read from tape. The tape's VSN is SCRATC (VSN=SCRATC) and the user executing the transfer must be validated to use UNLABELED tapes. The format of the tape request is as follows: REQUEST,TAPE,NT,LB=KU,D=PE,CV=AS,F=S,VSN=SCRATC, (PO=W if writing to the tape). You may wish to modify this tape request based on your site's needs. Please refer to the IGES Reference Manual for more detail. --,-_." _... _ - - - - .... ".,'-,,- -- , .. , _._--- 3-1 CONTROL DATA CORPORATION 1987/01/15 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 664 3.0 PSR/RSE CORRECTIVE CODE 3.0 PSR/RSE CORRECTIVE CODE The release of EDL V1.2.5 corrects the following PSR/RSE's. PSR/RSE DESCRIPTION ED10205 Standard retrieval aborts if user exited from the previous retrieve. ED10193 File (Data) transfers ln DDN force UM and STANDARD to ENGLISH. EDIA019 Cannot route files to printer. EDIA009 Control T may hang EDL. EDI0228 EDL periodically locks up - all users are affected. EDI0203 EDL hangs all users. EDI0219 Log file records tablet information. EDI0230 DEFINE task allows user to specify local filename, not used when attached. EDI0~31 RELEASE fails for 1.57 drawings. EDIA020 EDL sends a terminal configuration of C790 to UNISTRUC. EDIA021 EDL passes UNISTRUC C790 terminal type incorrectly. EDI0237 MENU/TASK Data Base is difficult to customize. -----_.-.... _ ..__ .. _------- _.. _----_.- ..... _------_._ ...- . _ - - .._ ...- _... _---_._--- CON T R 0 L ~DATE 02/16/87 DAT A COR P 0 RAT ION ASSEMBLY NO CORPORATE FILE NUMBER SCMA 2G007 2043520008 90110 PAGE SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) SHIP TO SOLD TO 1 OF 2 ***************** * PACKING COPY * ***************** COMPUTER PERIPHERALS INC. ATTN: C.W. MARTOCELLO/VFDZON 2621 VAN BUREN AVE. NORRISTOWN, PA 19446 COMPUTER PERIPHERALS INC. ATTN: C.W. MARTOCELLO/VFDZON 2621 VAN BUREN AVE. NORRISTOWN, PA 19446 CUSTOMER P.O. TRANSMIT NO DEPT SALES REP ACCOUNT SUBMITTER SELLING OFFICE INSTALLING OFFICE SYSTEM TYPE· SYSTEM SERIAL FXX FXX CY830 00618 PRODUCT NUMBER RELEASE LEVEL H830-110 664 COMPONENT NUMBER VER PROD QTY ICEM DESIGN/DRAFT 162 1 VER COMP TY COMP UNIT TYPE MN QTY PRICE ICEMDD 162 2400 ICEMGPL· 162 600 ICEM INTRO CONTR RF ICEM DATA MGMT RM RF ICEM BAS CONST RM RF ICEM DRFT FUNT RM RF ICEM GPL REF MAN RF ICEM DDN SRB MEMO ICEM INSTALL INST MEMO ICEM DDN UG UG PROJECT NUMBER FACILITY CODE VFDZON 0150/ PRODUCT NAME COMPONENT NAME /' DIVISION CODE 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 1 1 1 1 1 1 1 1 1 1 ORDER PROCESSING CHARGE 0.00 10 PRODUCT CHARGE 0.00 VREL68 t/REL68C 60457130L 60461410E 60461420D 60461440D 60462520C SMD131371 SMD131372 60456940AF FREIGHT P P P P P M 1 1 1 1 1 1 1 1 1 1 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 EXTND EXTND CP BACKPRICE QTY AV ORDER SHIPPED FROM SMD 1227-1979-SMD380 ROUTING- SURFACE AIR CONTROL DATA CORPORATION SOFTWARE MANUFACTURING AND DIST. 4201 N. LEXINGTON AVE. ARDEN HILLS, MINNESOTA 55126-6198 VIA NUMBER OF PIECES PACKED BY GROSS WEIGHT FREIGHT COST BILL OF LADING .... _-_ _--_._._----_....__ ._-_._ ....... _.__._ ..__...... _........ __... __ ._- --._.. _..._... .... _--- - - - - - - .. S S L L L L L S S L ... _ ------- CON T R 0 L D A T A COR P 0 RAT ION DATE ASSEMBLY NO CORPORATE FILE NUMBER SCMA 02/16/87 2G007 2043520008 90110 P PAGE 2 OF 2 SOFTWARE/CONTROLWARE MOVEMENT AUTHORIZATION (NOT AN INVOICE) PRODUCT NUMBER RELEASE LEVEL H830-119 664 COMPONENT NUMBER PRODUCT NAME VER PROD QTY ICEM FACILITIES 1.4 1 COMPONENT NAME vREL37A (, I 6046169004 SMD131367 SMD131368 VER COMP TY COMP UNIT TYPE MN QTY PRICE FACILITIESV14 1.4 600 ICEM FAC REF MAN RF P FACILT INSTL INST MEMO FACILITIES SRB MEMO 0.00 0.00 0.00 0.00 1 1 1 1 ORDER PROCESSING CHARGE 0.00 4 PRODUCT CHARGE 0.00 l· H830-207 664 vREL76A vREL76B 60458880AG 60459740AH 60498300AJ SMD131365 SMD131366 60000167A 60000168A ICEM ENGR DTA LIB EDL125 125 1200 E125DOC 125 600 ENG DTA LB ADM RM RF ENG DTA LB USH RM RF QUERY UPDATE 3 RM RF EDL SRB MEMO EDL INSTALL INSTR MEMO EDL USER GUIDE UG EDL CUSTOM GUIDE UG 1 1 1 1 125 0.00 0.00 0.00 0.00 EXTND EXTND CP BACKPRICE QTY AV ORDER 1 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 1 1 1 1 1 1 1 1 1 ORDER PROCESSING CHARGE 0.00 9 PRODUCT CHARGE 0.00 M M M M M 1 1 1 1 1 1 1 1 1 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 TOTAL ORDER PROCESSING CHARGE 0.00 23 TOTAL PRODUCT CHARGE 0.00 3 TOTAL ORDER CHARGE S L S S 0.00 S S L L L S S L L U.S. DOLLARS MISCELLANEOUS CONTENTS: 003 001 001 600 - 1200 - 2400 .. _-.----_._------_._--- i CONTROL DATA CORPORATION ICEM Facilities Operating System Level: NOS 2.5.1 level 664 Date: 12/23/86 SOFTWARE RELEASE BULLETIN DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot -be responsible for the proper functioning of undescribed features or parameters. Control Data Corporation gives the user permission to reproduce this document. *** NOTE *** Please contact the elM Hotline at one of the following numbers if you encounter any problems or have any q'Jestions: 1-800-328-3980 U.S. outside of Minnesota 1-800-527-0564 Canada 1-612-851-4131 Minnesota and other international *** URGENT *** Please make this document available to all ICEM Facilities users. ~MD131368 - _._... _-_ _._... _......__ ._._----_..__._.. _ - _ . _ - - - - - .. f\ • CONTROL DATA CORPORATION ICEM Facilities Version 1.4 Software Release Bulletin NOS 2.5.1 Level 664 TABLE OF CONTENTS 1. e) Introduction 1 2.0 Compatabilities 1 3.e) Customizing Instructions 1 3.1 Facilities Customization 1 3.2 Engineering Data Library 1 3.3 Entity Dragging fix 1 Manual Corr'ections 2 4.e> , 'J CONTROL DATA CORPORATION ICEM Facilities Ve~sion 1.4 Software Release Bulletin NOS 2.5.1 Level 664 1.0 1. INTRODUCTION ICEM Facilities is designed to increase the productivity and enable the automatic generation of repo~ts for facilities building managers and plant enginee~s. d~awing 2.0 COMPATABILITIES ICEM Facilities version 1.4 Design/Drafting ve~sion 1.62. ~equires ICEM 3.0 CUSTOMIZING INSTRUCTIONS 3.1 Facilities Customizati~n The p~ocedure files FACVER and ICEMFAC were written assuming that ICEM Facilities is installed on username APPLLIB, ICEM Design/Drafting is stored as a direct access file named ICEMDDN on username APPLLIB, and the GPL overlay library is sto~ed as a direct access file named GOLIB on username APPLLIB. If this is not correct for you~ system, change all references to APPLLIB in p~ocedures FACVER and ICEMFAC to the correct user name fo~ you~ system. You should also cahnge the references to ICEMDDN and GOLIB if these files a~e stored under different filenames for your system. 3.2 Enginee~ing Data Library Customers wishing to use ICEM Facilities under ICEM Engineering Data Library should contact Control Data concerning modifications to the standard EDL. 3.3 Entity dragging fix Two changes should be made in file FACMSTR: 1. The MSTRING labeled F104 (the line directly under F104 in file FACMSTR) should be changed to f.13.S.1.t1t.4.1.Y.Y 2. The MSTRING labeled F114 should be changed to f. 13.8. 1. t 1t. 4. 1. Y. Y , CONTROL DATA CORPORATION ICEM Facilities Version 1.4 Software Release Bulletin NOS 2.5.1 Level 664 j 2. 4.0 MANUAL CORRECTIONS Before executing ICEM Facilities, the user should enter the following commands GET,ICEMFAC/UN=APPLLIB SAVE,ICEMFAC GET,REPORTS/UN=APPLLIB SAVE,REPORTS FACSRB2.GLN . .... . ...-.-.-.-.-.........-... - ...... _._-_. -------------------------------------------------------- CONTROL DATA CORPORATION -------------------------------------------------------ICEM Facilities ver-sion 1.4 Operating System Level: NOS 2.5.1 level 664 Date: 12/23/86 INSTALLATION INSTRUCTIONS ------------------------------------------------------DISCLAIMER NOS and its pr-oduct set ar-e intended for use only as descr-ibed in this document. Control Data cannot be responsible for- the pr-oper functioning of undescribed features or parameters. Control Data Corporation gives the user permission to reproduce this document. *** NOTE *** Please contact the CIM Hotline at one of the following number-s if you encounter any problems or have any q'Jestions: 1-800-328-3980 U.S. outside of Minnesota 1-800-527-0564 Canada 1-612-851-4131 Minnesota and other international SMD131367 CONTROL DATA CORPORATION ICEM Facilities Version 1.4 Installation Instructions NOS 2.5.1 Level 664 1• 1.0 RELEASE DOCUMENTATION ICEM Facilities Version 1.4 runs under the CDC Network Operating System (NOS) Version 2 and the CDC Interactive Facility (IAF) communications subsystem. ICEM Facilities is designed to increase the drawing productivity and enable the automatic generation of reports for facilities building managers and plant engineers. The operation of ICEM Facilities under NOS 2 requires the installation of the CDC Network Access Method (NAM), IAF and the associated products. 2.0 HARDWARE REQUIREMENTS The minimum hardware configuration required for ICEM Design/Drafting 1.62, NOS 2 and IAF is required to support ICEM Facilities 1.4. 3.0 RELEASE MATERIALS The ICEM Facilities release files reside on the tape with a VSN of REL37A. This tape has the following characteristics: 9-track with 1600 CPI binary recording mode, FACILITIESV14 as the file ID in the HDR1 label and the following files: Fi le Fi le Fi le Fi le Fi le Fi le Fi le Fi le Fi le Fi le Fi le Fi le Fi 1e Fi 1e Fi le Fi le Fi le Fi le 1: ..... ':' . ..... '-J • 4: 5: 1.:. : 7: . .... 9: 10: 11 : C' • .... I')· 1':",_I. 14: 15: 1t.: 17: 18: FACINST, FACTFIL, FACMSTR, FACPATl, Installation Procedur'e fi le Tablet overlay file Menu String tablet file Office furniture patterns FACPAT2~ Haworth component patterns FACGPLS, GPL source code FACLIB, Compiled GPL code FACGPRT, Facilities demo parts EXAMPLE, Data for example layout ICEMFAC, Execution procedure file REPORTS, Report generation procedure file HWDATA, Data for Haworth component bill of materials OFDATA, Data for office furniture bill of materials CEDATA, New construction cost estimate data REPSRC, Report generation source code REPABS, Report generation absolute code FACVER t Facilities verification procedure VERIT. Data for verification procedure CONTROL DATA CORPORATION ICEM Facilities Version 1.4 Installation Instructions NOS 2.5.1 Level 664 *** NOTES AND CAUTIONS *** All limitations applicable to NOS 2 and IAF also apply to ICEM Facilities. Existing files with the same names as those listed above will be replaced by the files from this tape. 4.0 INSTALLATION INSTRUCTIONS The files which are part of the ICEM Facilities product are installed by executing the installation procedure~ which is file 1 of the ICEM Facilities tape, VSN=REL37A. ICEM Facilities should be installed on username APPLLIB with a user index of 377774. The installation procedure must be run interactively. Enter the following commands from the System Console: X. DI S. SUI,377774. LABEL , FACTAPE,R,L=FACILITIESV14, VSN=REL37A, F=I,D=PE. COPYBF,FACTAPE , INSTALL. INSTALL. DROP. Successful installation will be indicated by the' following message displayed on the terminal: THE FOLLOWING ICEM FACILITIES FILES HAVE BEEN LOADED FROM REL37A: FACIN8T FACTFIL FACMSTR FACPATI FACPAT2 INDIRECT ACCES~: DIRECT ACCESS DIRECT ACCESS DIRECT ACCESS DIRECT ACCESS FACGPL~: DIRECT ACCESS FACLIB DIRECT ACCESS FACGF'RT DIRECT ACCESS I ND I RECT ACCES!:; EXAMPLE ICEMFAC INDIRECT ACCESS REPORTS I ND I RECT ACCE~:S HWDATA INDIRECT ACCESS I ND I RECT ACCE:::::; OFDATA INDIRECT ACCESS CEDATA REP::;RC I ND I RECT ACeES!:; INDIRECT ACCESS REF'ABS INDIRECT ACCESS FACVEF: INDIRECT ACCESS VERIT INSTALLATION COMPLETE - - - _.._._ ......... - - - - - - - -... ....- ....... _-_ .. \I CONTROL DATA CORPORATION ICEM Facilities Version 1.4 Installation Instructions NOS 2.5.1 Level 664 -":. '-' . *** NOTE *** To install ICEM Facilities on a user name other than APPLLIB, log on to any terminal and enter all commands between and including the LABEL command and the INSTALL pro,:edure call. 5.0 VERIFICATION PROCEDURE To verify the proper installation of ICEM Facilities, complete the following steps. The verification procedure must be run interactively. *** *** NOTE This procedure was written assuming that ICEM Facilities was installed on username APPLLIB s ICEM Design/Drafting Version 1.62 is stored as a direct access file named ICEMDDN on user name APPLLIB s and the GPL overlay library is stored as a direct access file named GOLIB on username APPLLIB. If this assumption is incorrect, the references to UN=APPLLIB and/or the filenames for ICEM Design/Drafting and the GPL overlay library must be modified to specify the username and/or filenames in use. If the above changes are required, similar changes will be required in file ICEMFAC. See the Customization instructions in the Software Release Bulletin for ICEM Facilities for further information. 1: Log into a graphics terminal supported by ICEM Design/Drafting. 2: Enter: CLEAR. GET,FACVER/UN=APPLLIB. FACVER. ICEM Facilities will retrieve certain files from APPLLIB and prompt the user as shown in figure 1 to allow the user to enter ICEM Design/Drafting. .. - 3: Answer the prompts for baud rate and terminal configuration for the terminal you are using. Figure 1 shows the responses for a Tektronix 4114 ter-mina 1. 4~ En t e r- the par t nam e and s ~I e e t nIJ mbera s f I) 1 10 ~IJ S : ENTER PART NAME VERIFY SHEET NUMBER = 1 --_......._._.-_._--------_._---- .-... - ..•. • -_._._----,,_. - ..... _..._ - - - - --,._.-., ... ... "., ._----- 10' CONTROL DATA CORPORATION ICEM Facilities Version 1.4 Installation Instructions NOS 2.5.1 Level 664 4. ICEM Design/Drafting will prompt you for the units of measure and drafting standard. Answer the prompts ass h 0 ttl n bel (:.ttl : --UNITS OF MEASURE 2 --DRAFTING STANDARD 1 After the menu is displayed, enter the following ICEM Design/Drafting command string: 5: F.l.17.4.VERIT ICEM Facilities will create a facilities layout as shown in figure 2. 6: When the layout is complete, enter a blank car-r-iage return. ICEM Faci 1 i ties I_tli 11 leave ICEM Design/Drafting and generate an office bill of materials. Compare the report displayed to figure 3 to verify that it is correct. If the layout and bill of materials agree with the figures, verification of ICEM facilities is complete. ...•. _._' "."_.'''.' , .. _" ... _.---, ... _." ' ' .. " _ . '.. .. ' _. ,."." , ..•... _-_ ... ..•... " _--_._._ ... " .......,,-.- .. .. ' .-._.- .. "_.,,., ..• _ - - .; CONTROL DATA CORPORATION ICEM Facilities Version 1.4 Installation Instructions NOS 2.5.1 Level 664 5. FAeVER ENTER BAOt> RATE. Q ICEHOON VERSION Rt.61AD COPYRIGHT I'WU=ACTURING SERVICES. INC. IQ78 COPYRIGHT CONrROL OttTA 'Q78. lQ7Q, 1Q83. tGs.c. Nfl) CONSULTING ~T[ON 1Q88. 1Q81. lQ82 IGBS. lQ86 WELCOt1E TO ICEI'I)ON GRAPH I CS TE~ I HAL TYPE 1. TEKTRON IX 4014 2. TEkTRONIX 411S 3. TEkTRONIX 41e7 4. TEkTRONIX 41eg 5. TEkTRONIX 4113 6. TEkTRONIX 41t4 7. TEkTRON I X 41 t 5 B. TEkTRONIX 4125 Q. CDC VIKING 721 10. CDC lEW 7Q8 VITH TEKEP1 6 ttENU MEA 1. 2. 1 GRAPH ICS TERHINAL. CDC 722 TABLET 1. 2. OFF TEKTRONIX OPTION 13 4. TEKTRONIX 4QS7 3. 1 LOCAL 'DISPLAY FILE 1. 2. I ON OFF LOCAL owtACTER SET I. ON 2. OFF t FiglJrt.' 1. - - - _ ..... _ - - - - - - - - _ .._--._........__ ._.- . . ....... _--_.._. __ ._............._._--- " CONTROL DATA CORPORATION ICEM Facilities Version 1.4 Installation Instructions NOS 2.5.1 Level 664 6. --------------------------------------------------------------------- I ~ ~ '0 •J I· ! I Figur'e 2. - - - - _ .._..._ _... . _- CONTROL DATA CORPORATION ICEM Facilities Version 1.4 Inst~llation Instructions NOS 2.5.1 Level 664 ------------------------------------------------ ____________ ~: ______ _ . ~PORT , OFFICE BILL OF ~TERIALS 2 ""WRTH BILL OF HATERIALS ~ NEW CONSTRUCTION COST ESTlftATES 4 TERt1I~TE -------TfoilS REPORT RESIDES ON LOCAL FILE OFEULL------REf'tEItBER TO SAVE IT OFFICE SILL OF HATERIALS PART NAME I VER IFY ATTRIBUTE NAHE DESCRIPTION ••••••••• ..........** CHAIR. SYl'tBOL D£SI(. 4472. He CHAIR DESk STD. COUNTOUR .... X72 ... .... ......... gTY UNIT COST 175.75 377.55 EXTENDED COST 175.75 377.55 TOTAL 553.38 -------THIS ~T RESIDES ON LOCAL FILE OFBIU.------RE"EPtBER TO SA YE IT REPORT I 2 3 .. OFFICE BILL OF ftATERIALS HAWORTH BILL OF MTERIALS NEW CONSTRUCT ION COST EST IttATES TERPUHATE CORREC T I NSTALLA TI ON REVERT. w.s BEEN YER IF lED / Fig IJ r' €' FAt:: I N~:;T. GLN ::: • 1987/05/15 CONTROL DATA CORPORATION --------------------------------------------------------------ICEM ENGINEERING DATA LIBRARY Operating System Level: NOS 2 Level 678 Date: 05/15/87 INSTALLATION INSTRUCTIONS --------------------------------------------------------------- DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Control Data Corporation reproduce this document. gives the user permission to SMD131529 · ; 1-1 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 1.0 ICEM EDL VERSION 1.2.6 1.0 ICEM EDL VERSION 1.2.6 1.1 RELEASE DESCRIPTION ICEM Engineering Data Library (EDL) is an application designed to provide a user-friendly interface to Control Data's CAD/CAM products and to manage the engineering data produced by these products. The EDL system runs under the CDC Network Operating System (NOS) Version 2, and the CDC Network Access Method (NAM) and CDC Interactive Facility (IAF) communications pac~ages. Information Management Facility (IMF) interfaces to the EDL database. A run-time subset of IMF is included with EDL. 1.2 HARDWARE REQUIREMENTS EDL requires the m1n1mum hardware configuration for NOS 2 and NAM/IAF. The user station can be a graphic or alphanumeric terminal. EDL requires a field length of 175000 octal words. 1.3 DEPENDENCIES EDL interfaces to the following application packages. ICEM DDN Version ICEM Solid Modeler .Unistruc II ICEM Schematics PATRAN-G IGES V2 UNIPLOT XEDIT - - - -------_.. _-----_._--_.._._,,_.- -... ,_ 1.63 1.13 15AUG84 1.15 2.0 2.21 .. _--,. ......_------ ._--,- ----_. ,-- I • I ' 1-2 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 1.0 ICEM EDL VERSION 1.2.6 1.3 DEPENDENCIES Full Screen Editor Reclaim 1.4 RELEASE MATERIALS . EDL consists of two 9-track, 1600 cpi (D=PE) tapes. The format of the tapes is internal (F=I). The EDL" Version 1.2.6 product resides on the tape VSN=REL76A and has a label of EDL126 (L=EDL126). The EDL Documentation resides on the tape VSN=REL76B and has a a label of E125DOC (L=EI25DOC), same documentation as for EDL 1.2.5. The following files are found on the EDL product release tape. File File File File File File 1 2 3 4 5 6 INSTALL E125PRC E125ABS E125BIN E125LIB E125IBL File 7 File 8 File 9 E125NBL E120CNV EDLCOM File File File File File File File File 10 EDLFIX 11 -.. EDLTRAN MOUT 12 13 E125MMB 14 E125DMB 15 E125MDB E125DDB 16 17 EDLLIST File File File File File 18 19 20 21 22 IMF2LIB IMF2QU MCSIMF2 IMF2STF IMF2SCP File 23 File 24 CLGABS IMF2REC EDL Installation Procedure EDL Version 1.2.6 Procedure file EDL Absolute Program EDL Main Overlay Relocatable Program EDL Relocatable Subroutine Library EDL Relocatable Information Base Subroutine Library EDL Networking Subroutine Library Conversion Program EDL 1.1.3 to EDL 1.2.0 EDL Information Base Common Block Text File Unload and reload database procedures EDL Networking Data Type Text File Subroutine to generate EDLLIST Message and Task Metabase Engineering Data Metabase Message and Task Database Engineering Data Database Default Database Load List IMF Version 2.1 Enforcer Library Query·Update with IMF 2.1 Interface Start-up Procedure for IMF2SCP IMF 2.1 System Tuning File IMF 2.1 System Control Point Absolute Program Program to Associate Log File to Database Offline Recovery Utility I • 1-3 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 1.0 ICEM EDL VERSION 1.2.6 1.4 RELEASE MATERIALS File 25 WMTUN52 File 26 File 27 IMF2LDU MaTHERN Program to Change Metabase Username for a Database IMF 2.1 Load/Unload/Validate Utility Metabase for Metabases, needed by IMF2LDU The following files are found on the EDL Documentation release tape. File 1 File 2 File 3 INSTALL EDLDMAN EDLRMAN EDL Documentation Installation Procedure EDL Database Administrator's Manual EDL Version 1.2.5 Reference Manual the capability to use their database with out doing a major conversion. NOTE: The EDL 1.2.6 file names are the same as the file names for EDL 1.2.5. There are no major differences between the two databases, so maintaining the same file names provides an easier conversion process. 2-1 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.1 ESTABLISH NOS ACCOUNTS Establish a NOS account for the 'EDL programs, procedures, and data base files. This account may have any username and password. Establish a NOS account with username IMF on which the Information Management Facility will reside and run. This use~name must have the name IMF, and must have special validations. It must be able to run a system control point job, communicate with user control points, create unlimited dayfile messages, unlimited CP time, unlimited MS, create direct and indirect files, etc. All usernames from which EDL will be run must have validation to communicate to system control point jobs. Otherwise, they will be automatically logged off when they try to execute EDL. 2.2 MINIMUM VALIDATIONS 2.2.1 UN=IMF . _..... _"-"---"-_.-.,,-_. AP=MCS AP=RBF Message Control System. Remote Batch Facility. AW=CLPF AW=CSPF AW=CCNR AW=CUCP Create direct access files. Create indirect access files. Enter system without charge number. Access system control point facility. __.... _ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I • 2-3 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.2.2 ALL OTHER USERS INCLUDING THE DATABASE ADMINISTRATOR Note 1 - The EDL installation procedure does not enter a CHARGE statement after the secondary USER commands when the procedure moves to UN=IMF and back to the DBA's account. Note 2 - Required for Database other users. administrator, may vary for 2.3 RUN THE INSTALLATION PROCEDURE If you are installing EDL 1.2.6 on the same user number as EDL 1.2.5 (not recommended) rename E125DDB and E125MDB with the following commands. CHANGE,E12BDDB=E125DDB. CHANGE,E12BMDB=E125MDB. Run the product tape installation procedure using the following control cards. Before installing IMF, idle down IMF from the system control point. LABEL,TAPE,VSN=REL76A,F=I,D=PE,R,L=EDL126. COPYBF,TAPE,INSTALL. BEGIN,INSTALL,INSTALL. The installation procedure password of the EDL account, IMF. will prompt for the username and and the password of username If you already have the IMF2.1 files on username IMF and you do not wish to re-install it, answer NONE when prompted for the password of username IMF. For sites currently using EDL 1.2.3 or EDL 1.2.5, it is recommended that the IMF files be reinstalled, since the IMF released with EDL 1.2.6 has been updated. It is suggested that you reinstall IMF even if you don't plan to upgrade to EDL 1.2.6, because the new IMF version contains a number of important fixes. After reinstalling IMF, you must execute the LOADEDL procedure against EDL 1.2.3 to run EDL 1.2.3 or EDL 1.2.5 to run EDL 1.2.5 with the new IMF. --- ---------_.. ----..._------ I • 2-2 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.2.1 UN=IMF CC=77B CM=77B CS=7 DB=7 DF=77B DS=7 FC=7 FS=7 MS=77B PW=pw Max number of batch commands. Max central memory space used. Cumulative size of all indirect access files. Max number of executing jobs and queue files. Max number of MESSAGE requests to system and job dayfile. File size allowed for an individual direct access permanent file. File count. File size allowed for an individual indirect access permanent file. Max number of additional mass storage PRU's the user is allowed to allocat~ to a job. Password for both batch and interactive 2.2.2 ALL OTHER USERS INCLUDING THE DATABASE ADMINISTRATOR AP=IAF AP=RBF Interactive Facility Remote Batch Facility AW=CLPF AW=CSPF AW=CCNR AW=CAND AW=CUCP Create direct access files. Create indirect access files. Enter system without charge number. (Note 1) (magnetic Request nonallocatable devices uni ts) • (Note 2) Acces& system control point facility. CC=77B CM=77B CS=7 Max number of batch commands. (Note 2) Max central memory space used. (Note 2) Cumulative size of all indirect access files. 2) DB=7 tape (Note I Max number of executing jobs and queue files. (Note 2) DF=77B DS=7 FC=7 FS=7 MS=77B PW=pw -_._.. _----_ .•..__ .._--_._-,.- .. Max number of MESSAGE requests to system and job dayfile. (Note 2) File size allowed for an individual direct access permanent file. (Note 2) File count. (Note 2) File size allowed for-an individual indirect access permanent fi le. (Note 2) Max number of additional mass storage PRU's the user is allowed to allocate to a job. (Note 2) Password for both batch and interactive "-'---_.._-_..... ,.,.".,,,.,,--, ... "'_.,', .... _-"'_.. ... , _-_.. _-,... ,------_. ,, .. ----------. "_-"._-,._._-."" . .. ....."-------,,." 2-4 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.3 RUN THE INSTALLATION PROCEDURES To install the IMF files without installing the EDL files, be sure that you are logged into the UN=IMF account and type the following commands. Remember to idle down IMF at the system control point. LABEL,TAPE,VSN=REL76A,F=I,D=PE,R,L=EDL126. COPY~F,TAPE,INSTALL. BEGIN,INSTIMF,INSTALL. More information about starting and tuning IMF can be found in following sections. After installing the EDL Version 1.2.6 product, you may wish to load the EDL Documentation set onto your mass storage devices to modify according to your site's particular needs. To install the EDL Documentation set, mount the Documentation tape onto a 9-track tape drive and enter the following control cards. RETURN,TAPE,INSTALL. LABEL,TAPE,VSN=REL76B,F=I,D=PE,R,L=E125DOC. COPYBF,TAPE,INSTALL. BEGIN,INSTALL,INSTALL. The installation procedure password of the account on Documentation files. This which you've installed EDL will prompt for the user name and the which you wish to install the EDL will usually be the same account on Version 1.2.6. 2-5 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.4 EDIT THE EDL PROCEDURE FILES. 2.4 EDIT THE EDL PROCEDURE FILES. The installation procedure creates the startup file EDL. It is a single CCL proc which gets procedure file E125PRC from the NOS username where EDL is installed and passes that username as the value of the AUN parameter on the BEGIN statement for EDL. No changes to the file EDL should be necessary. The proc header of procedure EDL in E125PRC should be edited to change the default value of the alternate username parameter (AUN) to the username 'on which the EDL programs and databases were installed. This will ensure that EDL will run correctly even when started directly from E125PRC instead of from file EDL. The procedures in E125PRC should be checked to ensure that the correct versions of the application programs are obtained from the' correct usernames. The standard procedure file assumes that all application programs and procedures are on UN=APPLLIB. If this is not the case at your site, E125PRC should be changed. If an application such as ICEM DDN is sysedited into your system so that it can be used as a system command, simply remove the attach statements and the statement that checks to see if the application program has been assigned. 2.5 ACTIVATE THE IMF2.1 SYSTEM CONTROL POINT. Edit file MCSIMF2/UN=IMF to change the commented out USER statement to a valid USER statement for the IMF account. Move this small procedure file to username SYSTEMX (UI=377777B). Note that the user statement in MCSIMF2 is mandatory and cannot be replaced by a SUI statement. The IMF system control point program, IMFSCP, is started like all subsystems by a DSD entry, starting the execution of the procedure file saved under username SYSTEMX. That is, from the console, MCSIMF2. 2-6 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.5 ACTIVATE THE IMF2.1 SYSTEM CONTROL POINT. IMF2SCP can run at any control point. To force it to run at a specific control point, use the following CMR/DSD entry before the MCSIMF2 command. ENABLE,MCS,cpll. To avoid changes to the operating system, the EDL version of IMF2SCP uses the same system identification as the' Message Control System, and cannot run when the Message Control System is active. IMF2SCP is idled through the DSD entry IDLE,MCS. When idled-down, IMF2SCP will complete all processing needed to keep the databases in a consistent state. Idle-down can thus be done without damaging the databases, even if there are use;-s active. 2.6 INSTALLING EDL IN NON-CONCURRENT MODE If you do not need to allow more than one ICEM user at the same time using the same EDL database , you can install EDL so that it will run in mono-user mode without the system control point job being active. To do this, follow the following steps. 1. Define an empty direct access file named EDLLOCK on the username where the EDL Engineering Database is installed. This file should be Public in Write mode. EDL will use this file to ensure that only one person tries to use EDL at a time. Otherwise, EDL may abort when the database is busy_ DEFINE,EDLLOCK/CT=PU,M=W. 2. Edit Procedure EDL in E125PRC to change the statement $IF,$MONO$=$TRUE$,Ll. to $IF,$MONO$=$MONO$,Ll. and put the AC=1 parameter on the E125ABS statement. 2-7 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION 2.7 INSTALLATION VERIFICATION To verify the installation of EDL, do the following steps: Log in to the NOS system using the username established for the database administrator. Initiate EDL by entering: -,EDL The terminal session below shows how to update the DBA's user profile. User responses are indicated by lower case letters. ICEM ENGINEERING DATA LIBRARY VERSION 1.2.6 COPYRIGHT CONTROL DATA CORP., 1984,1985,1986,1987 ALL RIGHTS RESERVED 8?/05/15. ENTER EDL USER IDENTIFICATION ? edlid ENTER EDL PASSWORD ? dba CURRENT TERMINAL CONFIGURATION GRAPHICS TERMINAL CDC VIKING 721 DIALOG AREA ON GRAPHICS TERMINAL COMMUNICATIONS RATE 9600 BAUD COMMUNICATIONS TYPE ASYNCHRONOUS TABLET NO LOCAL ASSIST DEFAULT LOCAL DISPLAY DEFAULT EGM NO BIT PLANES 4 EDLU0037 YOU ARE NOT RUNNING UNDER YOUR OWN NOS USERNAME ADMINISTRATOR TASKS EXIT USER MANAGEMENT GROUP ADMINISTRATION RELEASE ADMINISTRATION 1. 2. 3. 4. - - - - - - - - - - _ . , _... " ",,,.,. -, ,.,., ...... ---_._._.......,- E,EXIT USERMGMT GROUP ADMIN ·RELADMIN , ..-., •.,._ . .,. .,., , 2-8 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION 5. PART, FAMILY, AND VENDOR MANAGEMENT PARTM ENTER TASK ? usermgmt USER MANAGEMENT 1. EXIT 2. LIST USERS 3. ADD USERS 4. DELETE USERS 5. CHANGE A USER'S PROFILE 6. REACTIVATE A USER SELECT OPTION ? c E,EXIT L,LIST A,ADD D,DELETE C,CHANGE R,REACTIVATE ENTER THE EDL ID OF THE USER, LIST, OR CR TO EXIT ? edlid CHANGE USER DATA EXIT PROMPT FOR ALL EDL PASSWORD NOS USER NAME LAST NAME 6. FIRST NAME 7 • MIDDLE NAME 8 • DEP AR TMENT 9. TITLE 10. STREET ADDRESS 11. CITY, STATE, ZIP 12. PHONE 13. FIRST COMMAND 14. DIALOG DELIMITER 15. STRING DELIMITER 16. EDITOR 17. HOST SELECT OPTION 1. 2. 3. 4. 5. E,EXIT P,PROMPT PSW,PW U,UN L,LNM F,FNM MI,MNM D,DEPT T,TITLE A,ADDR C,CITY PH,PHONE CMD,COMMAND DIALOG STRING EDITOR HOST ? p ENTER A NEW EDL PASSWORD OR CR FOR SAME ? dbapw THE USER'S NOS USER NAME IS EDLDBA ENTER A NEW NOS ? edldba U~ER NAME OR CR FOR SAME 2-9 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION THE USER'S LAST NAME IS ENTER A NEW LAST NAME OR CR FOR SAME ? smith THE USER'S FIRST NAME IS ENTER A NEW FIRST NAME OR CR FOR SAME ? john THE USER'S MIDDLE NAME IS ENTER A NEW MIDDLE NAME OR CR FOR SAME ? a THE USER'S DEPARTMENT IS ENTER A NEW DEPARTMENT OR CR FOR SAME ? 2210 THE USER'S TITLE IS DATABASE ADMINISTRATOR ENTER A NEW TITLE OR CR FOR SAME ? THE USER'S STREET ADDRESS IS ENTER A NEW STREET ADDRESS OR CR FOR SAME ? 123 main street THE USER'S CITY, STATE, AND ZIP ARE ENTER A NEW CITY, STATE, AND ZIP OR CR FOR SAME ? minneapolis, mn 55000 THE USER'S PHONE NUMBER IS .•.... __ ._ _.._-------_.__ ..............- - ............ _.... __ . _ - - - - - - - - - - -...- ........... -.... ... .................._ _._ ... _ - _ . _ - - - - - - - .... .. .. , , .. 2-10 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION ENTER A NEW PHONE NUMBER OR CR FOR SAME ? (612) 555-2345 THE USER'S FIRST COMMAND IS ADMIN .ENTER A NEW FIRST COMMAND OR CR FOR SAME ? THE USER'S DIALOG DELIMITER IS / ENTER THE NEW DIALOG DELIMITER OR CR FOR SAME ? THE USER'S STRING DELIMITER IS " ENTER THE NEW STRING DELIMITER OR CR FOR SAME ? THE USER'S DEFAULT EDITOR IS FSE ENTER THE NEW EDITOR OR CR FOR SAME ? CHANGE USER DATA EXIT 2. ·-PROMPT FOR ALL 3. EDL PASSWORD 4. NOS USER NAME 5. LAST NAME 6. FIRST NAME 7 • MIDDLE NAME 8. DEP AR TMENT 9. TITLE 10. STREET ADDRESS 11. CITY, STATE, ZIP' 12. PHONE 13. FIRST COMMAND 14. DIALOG DELIMITER 15. STRING DELIMITER 16. EDITOR 17. HOST SELECT OPTION 1. E,EXIT P,PROMPT psw,pw U,UN L,LNM F,FNM MI,MNM D,DEPT T,TITLE A,ADDR C,CITY PH,PHONE CMD,COMMAND DIALOG STRING EDITOR HOST - - - - - - - _ . - .. _-_._.. _----_...... -.•....... 2-11 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION ? e ,'do', THE USER'S PROFILE HAS BEEN CHANGED *70', ENTER THE EDL 10 OF THE USER, LIST, OR CR TO EXIT ? USER MANAGEMENT 1. EXIT 2. LIST USERS 3. ADD USERS 4. DELETE USERS 5. CHANGE A USER'S PROFILE 6. REACTIVATE A USER SELECT OPTION E,EXIT L,LIST A,ADD D,DELETE C,CHANGE R,REACTIVATE ? list ENTER THE EDL 10 OF THE USER, LIST, OR CR TO EXIT ? li,st 2 SELECTIONS EDL 10 NAME 1. EDLCOM 2. EDLID SMITH, JOHN A. *** *** END OF LIST ENTER A NUMBER, E OR EXIT, OR CR FOR MORE ? 2 EDL USER ID NAME NOS USER NAME DEPARTMENT TITLE STREET ADDRESS CITY, STATE, ZIP PHONE FIRST COMMAND STATUS DIALOG DELIMITER STRING DELIMITER EDITOR EDLID SMITH, JOHN A. 2210 DATABASE ADMINISTRATOR 123 MAIN STREET MINNEAPOLIS, MN 55000 (612) 555-2345 ADMIN ACTIVE / " FSE ENTER CR TO CONTINUE ? --_._._--- - - - _.. __ .. _._... __ ... . _.._.. _--_. __.__. _ - - - -"--'-'--- - " - " - - - 2-12 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.7 INSTALLATION VERIFICATION 2 SELECTIONS EDL ID NAME 1. EDLCOM 2. EDLID SMITH, JOHN A. *** *** END OF LIST ENTER A NUMBER, E OR EXIT, OR CR FOR MORE ? e ENTER THE EDL ID OF THE USER, LIST, OR CR TO EXIT ? USER MANAGEMENT EXIT LIST USERS ADD USERS DELETE USERS CHANGE A USER'S PROFILE 6. REACTIVATE A USER SELECT OPTION 1. 2. 3. 4. 5. E,EXIT L,LIST A,ADD D,DELETE C,CHANGE R,REACTIVATE ? e ADMINISTRATOR TASKS 1. EXIT 2. USER MANAGEMENT 3. GROUP ADMINISTRATION 4. RELEASE ADMINISTRATION 5. PART, FAMILY, AND VENDOR MANAGEMENT ENTER TASK ? quit E,EXIT USERMGMT GROUPADMIN RELADMIN PARTM 2.8 UPGRADING EDL DATABASES If your site is currently running a previous version of EDL, .you must move the information to the new databases. If you have customized EDL for your site, also read the section in the customization manual about upgrading site customizations. 2-13 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.1 CONVERSION FROM EDL 1.1.3 2.8.1 CONVERSION FROM EDL 1.1.3 Conversion from EDL 1.1.3 to EDL 1.2.6 must be accomplished in three steps: EDL 1.1.3 to EDL 1.2.0, EDL 1.2.0 to EDL 1.2.3, and, finally, EDL 1.2.3 to EDL 1.2.6. This section of the document describes the conversion from EDL 1.1.3 to EDL 1.2.0. Conversion from EDL 1.2.3 to EDL 1.2.6 is discussed in section 2.8.2 of this document and conversion from EDL 1.2.3 to EDL 1.2.6 in section 2.8.3. To move from EDL 1.1.3 the data must first be moved to an EDL 1.2.0 database. All conversion'programs and procedures are available on the EDL 1.2.6 release tape. However, you will need to install a default EDL 1.2.0 database from an EDL 1.2.0 release tape. In order to convert the information on an EDL 1.13 database to your EDL 1.2.0 database, you need to run a procedure called CONV113. This procedure must be run from the NOS account where the EDL 1.2.0 database will reside. The EDL 1.13 database need not be on the same NOS account. Begin the conversion procedure by typing: BEGIN,CONV113,E125PRC,UN113=username. Where username is replaced EDL 1.13 database resides. with the NOS account where the This procedure will submit a job to convert the data from the EDL 1.13 database to the EDL 1.2.0 database. There should be no one else using the EDL 1.2.0 database during this time. After CONV113 has run, the output from the job, and the dayfile, will be on file CONVOUT. CONVOUT will contain details of any records which the program was unable to translate. ---_.._._ .. _............ -- - - - - - - - - - ' . --.--.-- 2-14 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 ---------------------------------------------------------------------. 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.1 CONVERSION FROM EDL 1.1.3 If the conversion program is unable to complete, the output and dayfile from the job will be on a file called CONVERR. Possible causes and solutions are: Problem Solution Misspecified UN113 Time Limit Re-run the CONV113 procedure Edit E125PRC, changing the time limit from 1200 on the CONVERT procedure. Reinstall an empty default 1.2.0 database before attempting to rerun the procedure. .._---- .... - _...... ., ...... - - - 2-15 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 , -------------------------------------------------------------------2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.2 CONVERSION FROM EDL 1.2.0 TO EDL 1.2.3 2.8.2 CONVERSION FROM EDL 1.2.0 TO EDL 1.2.3 Before moving engineering data into the EDL 1.2.3 database, you must reapply any Query Update Transactions which you used to customize the EDL 1.2.0 database. ,Otherwise, site defined file types, data types, engineering categories, etc., will not be in the new database, and any engineering data information that uses them will be rejected with constraint violations. You should also delete the user EDLID and the group DBA from the default EDL 1.2.3 database before attempting to convert the old database. This will 'avoid uniqueness constraint violations as that user and group are moved from the EDL 1.2.0 database. Use the user and group management functions of EDL 1.2~3 or Query Update to accomplish the deletion. To move engineering data from an EDL 1.2.0 database to an EDL database, type the following command. 1.2.~ BEGIN,CONV120,E125PRC,UN120=username. where username is replaced with the NOS account where ·the 1.2.0 database resides. EDL This procedure runa the IMF unload-reload utility and a special program to convert data that cannot be handled properly by the unload-reload utility. If you have a very large database, you may wish to begin the procedure in a batch jab. In some cases, the reload utility may find constraint violations which will cause the new database to be marked invalid. You should look at the error report and lists to determine which records caused the problem. Then use Query Update in repair mode to correct the errors and rerun the validate utility. ATTACH,IMF2QU/UN=IMF. IMF2QU. INVOKE EDLDATAW OF EDLDATA KEY EDLORDBA + USING E123DDB REPAIR EDLPW (enter QU directives to DISPLAY and correct the database) END ATTACH,IMF2LDU/UN=IMF. ---,_.,.......... _--------_.-._ ... _----_.,._. -_.._-".- .. _----_. __ ._ ..... _- ._._---- ._-_.. .._----- 2-16 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.8.2 CONVERSION FROM EDL 1.2.0 TO EDL 1.2.3 IMF2LDU. ? VALIDATE THROUGH EDLDATAW OF EDLDATA ? KEY EDLORDBA ? USING E123DDB ? REPAIR EDLPW ? TERM ? If you have customized EDL 1.2.0 piease read the customization . guide before attempting to convert database. It is necessary to adapt and reapply your QU MDB directives before converting the engineering data. - - - _.. _-,,-------,., " .. _--_ ...... -"._... .. - --,-_..... ,,''''----, new the and 2-17 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 . ---------------------------------------------------------------------- ~. 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.9.2 CONVERSION FROM EDL 1.2.3 TO EDL 1.2.6 2.9.2 CONVERSION FROM EDL 1.2.3 TO EDL 1.2.6 Before moving engineering data into the EDL 1.2.6 database, you must reapply any Query Update Transactions which you used to customize the EDL 1.2.3 database. Otherwise, site defined file types, data types, engineering categories, etc., will not be in the new database, and any enginee~ing data information that uses them will be rejected with constraint violations. You should also delete the user EDLID and the group DBA from the default EDL 1.2.6 database before attempting to convert the old database. This will -avoid uniqueness constraint violations as that user and group are moved from the EDL 1.2.3 database. Use the user and group management functions of EDL 1.2.3 or Query Update to accomplish the deletion. To move engineering data from an EDL 1.2.3 database to an EDL 1.2.? database, type the following command. BEGIN,CONV123,E125PRC,UN123=username1,UN125=username2. where username1 is replaced with the NOS account where the EDL 1.2.3 database resides and username2 is replaced with the NOS account where the EDL 1.2.6 database resides. This procedure runs the IMF unload-reload utility. If you have a large database, you may wish to begin the procedure as a batch job. In some cases, the reload utility may find constraint new database to be marked invalid. You should look at the error report and lists to determine which records caused the problem. Then use Query Update in repair mode to correct the errors and rerun the validate utility. violatio~s which will cause the ATTACH,IMF2QU/UN=IMF. IMF2QU. INVOKE EDLDATAW OF EDLDATA KEY EDLORDBA + USING E125DDB REPAIR EDLPW ON username2 (enter QU directives to DISPLAY and correct the database) END ATTACH,IMF2LDU/UN=IMF. - - - - - - - -------- " ... _------ .. _._---_._- - -"---'--'- - - - - --'---'-' ----- --------- 2-18 CONTROL DATA CORPORATION 1987/05/15 . ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.9.2 CONVERSION FROM EDL 1.2.3 TO EDL 1.2.6 IMF2LDU. ? VALIDATE THROUGH EDLDATAW OF EDLDATA ? KEY EDLORDBA ? USING E125DDB ? REPAIR EDLPW ? TERM ? If you have customized EDL 1.2.3 please read the customization guide before attempting to convert database. It is necessary to adapt and reapply your QU MDB directives before converting the engineering data. new the and 2.9.3 CONVERSION FROM EDL 1.2.5 TO EDL 1.2.6 If you installed EDL then you should have installing EDL 1.2.6 commands to maintain 1.2.6 on the same user number as EDL 1.2.5 renamed your database files before per instructions. Execute the following your 1.2.5 databases for EDL 1.2.6. CHANGE,E12RDDB=E125DDB. (version 1.2.6, R=release) CHANGE,E12RMDB=E125MDB. (version 1.2.6, R=release) CHANGE,E125DDB=E12BDDB. CHANGE,E125MDB=E12BMDB. If you installed EDL 1.2.6 on a different user number than EDL 1.2.5, execute the fo1l~wing commands to use your EDL 1.2.5 database files (or EDL 1.2.6. Under the EDL 1.2.5 user number (user125). PERMIT,E125DDB,user126=R. 2-19 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.9.3 CONVERSION FROM EDL 1.2.5 TO EDL 1.2.6 Under the EDL 1.2.6 user number (user126). CHANGE,E12RDDB=E125DDB. (version 1.2.6, R=release) CHANGE,E12RMDB=E125MDB. (version 1.2.6, R=release) DEFINE,E125DDB. DEFINE,E125MDB. CHANGE,E125DDB/CT=S,M=RM. CHANGE,E125MDB/CT=PU,M=W. ATTACH,E12XDDB=E125DDB/UN=user125. ATTACH,E12XMDB=E125MDB/UN=user125. COPY,E125XDDB,E125DDB. COPY,E12XMDB,E125MDB. PERMIT,E125DDB,IMF=W. Execute LOADEDL to add your ovcaps and routines. Run EDL, all data and customized menus and messages should be present. In order to avoid confusion between the EDL versions you are running you can modify the EDL Version Header displayed when EDL is initiated. Execute the MESSAGEMOD task within EDL's MENUMOD task. When prompted for the message name enter EINIT2. Modify the message EINIT2 from 'ICEM ENGINEERING DATA LIBRARY 1.2.5' to 'ICEM ENGINEERING DATA LIBRARY 1.2.6'. Also to correct the MSTRING character code execute the following commands. ATTACH,IMF2QU/UN=IMF. IMF2QU. INVOKE EDLDATAW OF EDLDATA KEY $EDLORDBA$ USING E125DDB IF FTFTC=$DDN MENU STRING FILE$ MODIFY SETTING FTCHR » $A$ END ._---- ...._-" ..- ._-- . _ - - - , . ,.. _._--- 2-20 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.10 IMF DATABASE MAINTENACE 2.10 IMF DATABASE MAINTENANCE 2.10.1 BACKUP AND RECOVERY IMF 2.1 provides utilities for d~tabase journal logging and offline database recovery. There are two procedures in EDL that make these utilities easy to use to backup and recover the EDL database. These procedures must be run from the NOS account on which the EDL database resides. They should be run only when there are no EDL users on the system. 2.1Q.l.1 Backup Procedure BEGIN,BACKUP,E125PRC This procedure copies the EDL database file E123DDB to a backup file named E123BAK. It also creates a journal log file named E123LOG which will automatically capture a record of all changes to the EDL Engineering Data Database. You should run this procedure periodically depending on the amount of EDL activity at your site. Be careful that the database is good before you run the BACKUP procedure since it 2-21 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.10.1.1 Backup Procedure will overwrite any previous backup and log files. Before running BACKUP, you may wish to copy E125DDB, E125BAK and E125LOG to magnetic tape. 2.10.1.2 Recovery Procedure BEGIN,RECOVER,E125PRC,DBN=username. This procedure is to be used only in the unlikely event that a system crash occurs when the database is open and the EDL database is destroyed. RECOVER copies the backup file E125BAK over the current database file E125DDB and runs the offline recovery utility to update the database with the journal entries from file E125LOG. This restores tha database to a consistent state as it ~ppeared just before the database was d~stroyed. Then this procedure causes the BACKUP procedure described above to be run, ensuring that any subsequent changes are logged. 2.10.1.3 Unload and Reload Database Procedure EDLFIX is a procedure file containing procedures to be used to unload and then reload an EDL database. EDLFIX consists of four procedures, UNLOAD, RELOAD, VALID, and CLEARDB. UNLOAD is a procedure to unload the contents of the E125DDB to files. RELOAD is a procedure to load the information obtained from the UNLOAD utility back into an empty database. (E125DDB) VALID is a procedure to validate a database if the RELOAD utility utility has problems. CLEARDB is a procedure that takes an "empty" database supplied on the EDL125 release tape and makes it totally empty. This should help the RELOAD procedure run smoothly( use to obtain an empty database for the RELOAD). 2-22 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.10.1.3 Unload and Reload Database Procedure TO RELOAD YOUR DATABASE: 1. Run the UNLOAD procedure against your current database. BEGIN,UNLOAD,EDLFIX. 2. Swap .databases so that the default database from the EDL125 release tape is called E125DDB. Do not delete the old database yet. Remember to CHANGE (E125DDB/CT=S,M=RM) and PERMIT(E125DDB,IMF=W). If you have run through the process before you can use the true empty database created by step 5 rather than the one o~ the EDL release tape. 3. Run the CHMUN procedure to ensure that the metaun is correct. BEGIN,CHMUN,E125PRC,FN=E125DDB,METAUN=username. 4. If your site does not run with journal logging, then you must turn it off again because logging is turned on in the default database on the EDL release tape. To turn journal logging off enter: BEGIN,CHLOG,E125PRC, FUNC=OFF, FN=E125DDB,AFN=E125LOG. You do not need to run this step if you have done it previously and saved the true empty database from the next step. 5. Run the CLEARDB procedure. The procedure may complain about the AI records which is ok, if the procedure complains about any other records you should call the Hotline. To run the procedure enter: BEGIN,CLEARDB,EDLFIX. 6. After executing the CLEARDB utility, make a copy of the resulting E125DDB. Then, the next time you need to RELOAD data, you can use that database instead of the default DB on the release tape. Then you can skip steps 4 and 5. . 7. Run the RELOAD procedure. empty database. BEGIN,RELOAD,EDLFIX. --_. --,---,_.•.. , . ' . _ - "., This will reload the data into the 2-23 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.10.1.3 Unload and Reload Database Procdure 8. Run the CHMUN procedure to ensure that the metaun is correct. BEGIN,CHMUN,E125PRC,FN=E125DDB,METAUN=username. 9. Test everything. NOTE: To run these procedures against EDL123 modify EDLFIX to reflect the E123DDB, i.e. change all occurrances of E125DDB to E123DDB. 2.10.2 RUNNING WITHOUT JOURNAL LOGGING To turn journal logging off for the EDL database, execute the following procedure. BEGIN,CHLOG,E125PRC, FUNC=OFF, FN=E125DDB ,AFN=E125LOG. Substantial improvements in resource utilization can be achieved by turning journal logging off. However, without journal logging, it is impossible to use the RECOVER procedure to reestablish the database to the point of failure in case the system. crashes while a user has the EDL database open. Instead, the file E125DDB must be restored from the last system file backup. It is unlikely that the database will be corrupted by anything other than a operating system or hardware failure, since IMF performs reprieve processing to close the database gracefully if an program fails or a user uses control T to abort the program. The risk of losing a day or half day of EDL information may be acceptable at your site. The application --- ._.._.-. - - ._.......... _ - - --- '''-._--._. __ _.__.. .. - . - - _......._........ _ - - ... _---_ - - - ... --_._----_.- 2-24 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.10.2 RUNNING WITHOUT JOURNAL LOGGING data such as drawings and journal logging. models are not affected by IMF 2.11 IMF TUNING CONSIDERATIONS The IMF System Tuning File, IMF2STF/UN=IMF, determines certain parameters that IMF 2.1 uses to control it's operation at the system control point. These parameters can affect resource utilization of EDL, respon~e time, and overall system throughput. The tuning parameters are read from the file every time the IMF (MCS) subsystem is started. To some extent, the optimal settings depend on the type of load on your system. The parameters on the tuning file provided on the EDL release tape are set to reasonable values for.an ICEM environment. They are set to minimize the impact of IMF and EDL on system throughput at the possible expense of EDL response time. 2.12 EDL AUTOSTART FOR USERS If a user wishes to log in to EDL without typing his EDL user id and password, create an indirect file called EDLUSER on the user's NOS username. This file should have a single line with the user id in columns 1-10 and the EDL password in columns 11-20. EDL will attempt to read this file and will prompt the user only if the file does not exist or if the information on the file is invalid. 2.13 PASSWORD MASKING If all terminals at your site are communicating in full duplex mode, you may cause EDL to temporarily disable echoplex mode while the users are entering passwords so that the password characters do not appear on the terminal screen. This is accomplished by changing the title of the message 2-25 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY INSTALLATION INSTRUCTIONS NOS 2 Level 678 2.0 INSTALLATION OF EDL AND THE IMF SUBSET. 2.13 PASSWORD MASKING named "DUPLEX" to "FULL", using a MDB transaction file or query update. See the customization guide section "CUSTOMIZING THE MESSAGE AND TASK DATABASE" for an explanation of how to change EDL messages. 2.14 USING QUERY UPDATE For the most part, IMF2QU functions as described in the Update Version 3 Reference Manu~l 60498300. Query The Invoke clause used to open an IMF 2.1 database schema, is different than the one documented for IMF Version 1. INVOKE external-schema-name OF conceptual-schema-name [ KEY use-literal] USING database-file-name [ nos-username ] t REPAIR repair-literal] [ CONCURRENT ] To query the EDL Engineering Database, INVOKE EDL OF EDLDATA USING E125DDB nos-username CONCURRENT To query the EDL Message and Task Database, INVOKE EDLMENUR OR EDLMENU USING E125MDB nos-un To query or update the Engineering Database, INVOKE EDLDATAW OF EDLDATA KEY $EDLORDBA$ + USING E125DDB nos-un CONCURRENT To query or update the Message and Task Database, INVOKE EDLMENUW OF EDLMENU KEY $EDLORDBA$ + USING E125MDB nos-un Sometimes Query Update will not display data for all records of a record type unless a FOLLOW directive is entered to specify the access path or coset to be used to retrieve the records. See the Query Update manual and the EDL record layout section of the customization guide. 3-1 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY 1.2.6 INSTALLATION INSTRUCTIONS NOS 2 Level 678 3.0 CREATING A NETWORK IN EDL 3.0 CREATING A NETWORK IN EDL This section explains how to set up a network of EDL databases, one on each mainframe. Hosts in an EDL network are configured in a "star", with many subordinates clustered around a single master host. Administrative functions (user validation, part definition) are carried out on the master host. The DBA in the network is responsible for running a job (started with the command INITNET) which polls other hosts in the network (a subordinate polls the master, while the master polls each subordinate), then rolls out for a site defined period before repeating the polling cycle. This information is repeated in section 16 of the EDL Customization Guide. It is recommended that the System Administrator become familiar with that document before attempting these changes. 3.1 DEFINE HOSTS The default EDL database host name is blank. In order to identify multiple hosts in a network, each host must be given a unique name within EDL. This name should be the three character LID (Logical IDentifier) by which the host is known to RHF. One host should be designated as the MASTER host for the network. This host must communicate directly to all subordinate hosts which run EDL. All administrative functions, such as validating users, and defining parts, and vendors, will be done on this host, and the information will be passed to the subordinates. All transactions dealing with data are done on the subordinate hosts, and then passed up to the master. Therefore, the master host will contain information about the data on all subordinate hosts. 3-2 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY 1.2.6 INSTALLATION INSTRUCTIONS NOS 2 Level 678 3.0 CREATING A NETWORK IN EDL 3.2 DEFINE COMMUNICATION LINKS 3.2 DEFINE COMMUNICATION LINKS CL records must be created for each host in the database, telling EDL which other hosts a specific host can communicate with. Note that each link must be defined twice, saying that HOST A c.an communicate with HOST B, and that HOST B can communicate with HOST A. 3.3 QU DIRECTIVES TO DEFINE A NETWORK A sample network could consist of two Cyber mainframes, and a Cyber 120 which does not run EDL, but whose data is managed by MA4 (whose data is passed up to MB1). Following are the QU directives to update the MASTER host (in this case MB1) for thi~ network configuration. INVOKE EDLDATAW OF EDLDATA KEY $EDLORDBA$ USING E125DDB STORE SETTING HIHOS,HIOFF,HIOS,HIEDL,HIHOSS $MB1$ 1 $NOS$ $T$ $MB1$ $MA4$ 100000 $NOS$ $T$ $MB1$ $SD2$ 200000 $AOS/VS$ $F$ $MA4$ "rEND STORE SETTING UVUSR UVHOS UVOUN $EDLID$ $MA4$ $EDLDBA $ $EDLID$ $MB1$ $EDLDBA $ $EDLID$ $SD2$ $DJH $ $EDLCOM$ $MA4$ $EDLDBA $ $EDLCOM$ $SD2$ $DJH $ $EDLCOM$ $MB1$ $EDLDBA $ *END STORE SETTING CLHOSS CLHOSR $MA4$ $MB1$ $MB1$ $MA4$ $MA4$ $SD2$ $MB1$ $SD2$ "rEND REMOVE USING UVHOS $ $ *END REMOVE USING HIHOS $ $ *END . -'-"'-'--'-'-"" ------_._._-- -_.-.-._--_ .. _....... - .. _._.. ---- .. _---_ ........ _..- - - 3-3 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY 1.2.6 CUSTOMIZATION GUIDE NOS 2 Level 678 3.0 CREATING A NETWORK IN EDL 3.3 QU DIRECTIVES TO DEFINE A NETWORK MODIFY USING HIHOS SETTING HIOFF $MB1$ 0 *END END Once the network has been defined on what will be the master host, this configuration should be copied to subordinates. EDL should be installed, then this same QU file should be run on each subordinate host. EDL must run on the same NOS account on each host. 3.4 El25PRC MODIFICATIONS 3. 4.,1 PROCEDURES GETMAS AND GET SUB Procedure GETMAS and GET SUB contain .DATA files with MFLINK directives. These directives are used to poll alternate hosts in the network for information which should be sent from the master to the subordinates, or vice versa. The first line in the .DATA files are USER,EDLDBA,EDLDBA. This user statement should be replaced with the batch user statement for the username where EDL will be running in the network. Since the master host will be using these MFLINK directives to poll each subordinate, this means that the username and batch password where EDL runs on each subordinate must be the same. A recommended modification to the GETMAS and GETSUB procedures is to remove the .DATA files from E125PRC (which is available to all users running EDL) , put this information into a private file on the username on which EDL resides, and modify the procedures to read these files rather then the .DATA files. 3.4.2 PROCEDURE EDL Procedure EDL on file E125PRC must be changed on each host, telling EDL the name of the host. The updated procedure header will look like: - - - _........__....•... _ _. .... . --_._-,--,,-_._--- _._, .._,----, . _ - - - - • f 3-4 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY 1.2.6 CUSTOMIZATION GUIDE NOS 2 Level 678 3.0 CREATING A NETWORK IN EDL 3.4.2 PROCEDURE EDL .PROC,EDL, I=INPUT, IT=O/IT,OT=O/OT,HOST=hos,AUN=EDLDBA. where hos is replaced by the name of the host on which this file resides. This is the only change to E125PRC given host. which is specific to a 3.4.3 EDL LOG FILES Each subordinate should have, on the username on which EDL is installed, a file called EDLSLOG. The master should have a file called EDLMLOG, and one file for each subordinate which runs EDL. These files will be called EDLMhos, where hos is replaced with the host identifier for the subordinate. These files should be public, or permitted to all usernames which can ,run EDL, in WRITE mode. These files contain log entries of each transaction which needs to be shipped either from the subordinates to the are polled master, or vice versa. These log files periodically by their destination hosts. 3.5 NETWORK INITIALIZATION The DBA should log into each host on the account where EDL resides, and enter the command INITNET. This will start up a job wh i ch will: 1. 2. 3. 4. Poll the subordinates (or master) for transactions which should be sent to this host. Run EDL in batch mode to process these transactions. Rollout for the interval defined in the procedure NETROLL in EI25PRC. Repeat. This job will have the UJN of NETJOB. It should continue to cycle until the system is deadstarted, at which time the INITNET task should be run again. If the job is dropped, the transaction data is not lost. Network transactions will 3-5 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY 1.2.6 CUSTOMIZATION GUIDE NOS 2 Level 678 3.0 CREATING A NETWORK IN EDL 3.5 NETWORK INITIALIZATION accumulate in the log files, and will be sent to other whenever the INITNET job is run on the receiving host. end ---""-,,-, '''' ,-"-----'"---",''''' ---,--" .. hosts ***** Affected Products: Subject: Date: Installation Bulletin IeEM ***** EDL 1.2.5/1.26 for NOS ICEM EDL 1.2.5/1.26 Common Block Correction 06/10/87 The EDLCOM file supplied with ICEM EDL 1.2.5, and also the file supplied with version 1.26, contains an incorrect image of the EDL_COMMON block. Three of the character size specifications are in error. This is a problem if the· site adds customized code to EDL and uses this common block. Below is a corrected copy of the EDL_COMMON common block. It is recommended that the site administrator edit the EDLCOM file (using FSE or XEDIT) to make the following corrections: 1. Line 14: The size of the CYES and CNO variables is now 5, rather than 3. 2. Lines 17 and 19: than 7. The size for these fields is 100, rather Below is an image of the corrected common block. The asterisks in column 1 are intended to show which columns need to be changed. Do not include the asterisks in the modified common block . C C * * * ..." EDL_COMMON EDL PRIMARY COMMON BLOCK COMMON /ECOM1/ HOST, USR, PWD, MDISP, SCLOCK, +CHELP, CLIST, CEXIT, CMENU, CCLEAR, +CWORK, CREL, CSUBM, CPEND, COBS, +CPAUSE1, CPAUSE2, CINOPT1, CEXTM1, +CYES, . CNO , +NOSUN, STRDEL, INPDEL, +AUN, DUN, DDB, MUN, MDB, AC, IT, OT, ALTINP, ALTOUT CHARACTER*lO HOST, USR, PWD, MDISP, SCLOCK CHARACTER*10 CHELP, CLIST, CEXIT, CMENU, CCLEAR CHARACTER*lO CWORK, CREL, CSUBM, CPEND, COBS CHARACTER*70 CPAUSE1, CPAUSE2, CINOPT1, CEXTMl CHARACTER*5 CYES,CNO CHARACTER*7 NOSUN CHARACTER*1 STRDEL, INPDEL CHARACTER*100 AUN, DUN, DDB, MUN, MDB CHARACTER*2 AC CHARACTER*100 IT,OT,ALTINP,ALTOUT COMMON /ECOM2/ NSYNC, PW, PL, NL, SCROLL, ECHO INTEGER NSYNC, PW, PL, NL LOGICAL SCROLL, ECHO If you have any questions about the information contained in notice, please call: this Central Software Support at 800-345-9903 or 612-851-4131 SMD131S45 ---- ~- --- --.. " .- - ._-- -------- -"" -"'~'''-' ,. -'--'-'- --_._ ..... 1987/05/15 CONTROL DATA CORPORATION ICEM ENGINEERING DATA LIBRARY V1.2.6 Operating System Level: NOS 2 Level 678 Date: 05/15/87 SOFTWARE RELEASE BULLETIN NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible fo the proper functioning of undescribed features and parameters. Control Data Corporation gives the user permission to reproduce this document. Please contact the appropriate Hotline if you encounter any problems or have any questions. US outside of Minnesota Minnesota and International Canada 800-328-3980 612-851-4131 800-527-0564 SMD131528 - - - - - - - - - - - - - - - " " - " . _ . _ . _ - - - _.. _... 1 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 678 Table of Contents 1.0 INTRODUCTION .... 1-1 2.0 NOTES AND CAUTIONS 2-1 3.0 PSR/RSE CORRECTIVE CODE 3-1 ... '-'--'--'- - - - ' - - " - - - ' , 1-1 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 678 1.0 INTRODUCTION 1.0 INTRODUCTION Version 1.2.6 of the Engineering Data Library is a System Software Update Release (SSU) containing PSR corrective code, new IMF 2.1 release, and a new unload/reload database procedure, EDLFIX. . -_.-.,,, ..,,_. _.. _--_ .•. - - _...... ----_._. 2-1 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 678 2.0 NOTES AND CAUTIONS 2.0 NOTES AND CAUTIONS 1. The EDL 1.2.6 file names have the same file names as EDL 1.2.5. There are no major differences between databases, so maintaining the same file names provides an easier conversion process. To distinguish EDL 1.2.6 the dayfile states the version level. 2. On entering EDL, if the user's logged in NOS user name is different than the NOS username in the EDL database, a warning message is displayed. Files created under this condition will not be accessible when the user is logged into the correct username unless the files are specifically permitted toOthe user. 3. Updating EDL for new files requires you to be running on the NOS username where the file resides. EDL assumes that all new files are private files. If the file is actually a NOS public file, use the EDL PERMIT task to change the file category to PUBLIC. 4. To install data files on a system username such as APPLLIB or LIBRARY, when a SUI statement is used to access the account, use UPDATE EDL FOR ENGINEERING DATA to add the information to EDL, then use CORRECT FILE INFORMATION to change the NOS username of the file to the right username. 5. An indirect access permanent file named USER must exist on the user's NOS username if the user wishes to use TRANSFER tasks on Solid Modeler data. The file USER co~tains the job card, user card, and accounting charge card image if needed. 6. If two users attempt to update the same EDL record at nearly the same time, a concurrency conflict may occur for the second user. An error message will be displyed and EDL will return to the previous task menu. The user should reobtain the data to determine what change was made by the other user and try the update again if appropriate. 7. If the user uses a Control °T to abort Query Update using IMF, occasionally the user job hangs and cannot be dropped. It may be necessary to do an override from the console to drop the job. 8. In a multi-host network, it is not possible to transfer data to a remote host when using the ACCEPT or RELEASE ° 0 _ _ _ _ _ 0• • " • • 0_0 _ _ _ 2-2 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY.· SOFTWARE RELEASE BULLETIN NOS 2 Level 678 2.0 NOTES AND CAUTIONS tasks. Data may be submitted to a release procedure from any host on the network, but to ACCEPT or RELEASE the data, the releaser must run on the host where the pending or released destination data is desired to reside. 9. Using the EDIT command on non-permanent files or files will prompt the user for the character code to be used to edit the file, UPPER CASE DISPLAY CODE or UPPER LOWER CASE ASCII. cr~ation 10. The correct file type for PATRAN PATDAT, is RANDOM ACCESS DATA. DATA, local file 11. In using the transfer tasks involving an IGES DATA FILE, the user must use the correct data name of the origination file or the destination file. The IGES data name specified must match the origination data name. The transfer data name specified must match the data name in the IGES file, or if the name in the IGES file is blank, the default data name IGES. 12. In a network configuration consisting of two or more hosts where a host is not available, the IMPORT and EXPORT commands will require a control-t to exit the wait status. This will not exit the user from EDL. 13. The reference manual states that a part number cannot be deleted if any released data is associated to the part. In fact, the part cannot be deleted if any data is associated to the part, regardless of the status of the data. 14. The default core memory field length to run EDL V1.2.6 is 175,000 octal. If EDL aborts due to maximum field length (MFL) exceeded, then edit the procedure file E125PRC, procedure EDL, to change the command HFL,175000 to increase the amount of memory allowed for EDL and IHF. 15. The EDL relocatable libraries are compiled at NOS 2 level 67s:---tf-your site is using an earlier version of . NOS and the product sets, there may be incompatibilities 2-3 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY SOFTWARE RELEASE BULLETIN NOS 2 Level 678 --------------------------~----------------------~---- -----------, 2.0 NOTES AND CAUTIONS between the EDL libraries and the system libraries. This may cause problems if the EDL absolute is reloaded using the LOADEDL procedure to include site-written Fortran code. If this situation occurs at your site, upgrade the product . __~_~t~~.9_f__ y-o-u.r-.s.i.te--to--1.e.v.el.-6.7.8..... ~__~ ---- 17. When a permanent file (PF) utility is running, EDL may abort if IMF tries to create a file. User catalogs that have a user index ending in the same number as the user index of the IMF user name will be locked until the PF utility has completed and IMF will not be able to create or extend the files it us~s for its operations. To prevent a possible loss of data, it is recommended that the system administrator be notified when PFLOAD or PFDUMPs are executing so that they can monitor and coordinate the use of EDL while these utilities are in use. 18. The procedure IGTCEI on El25PRC, which transfers IGES DATA to EXTERNAL IGES DATA, has been modified to write the EXTERNAL IGES DATA to tape. The procedure EITCIG on E125PRC has been modified to read from tape. The tape's VSN is SCRATC (VSN=SCRATC) and the user executing the transfer must be validated to use UNLABELED tapes. The format of the tape request is as follows: REQUEST,TAPE,NT,LB=KU,D=PE,CV=AS,F=S,VSN=SCRATC, (PO=W if writing to tape). You may wish to modify this tape request based on your site's needs. Please refer to the IGES Reference Manual for more detail. ----_._.".. , " , .---_..... ,,,, ..,-------_._._--- ...•••.. -.- .. _ --...... --_ _--_._... _---_ ......._.._-_ ......_ _--_ .......... .. . 3-1 CONTROL DATA CORPORATION 1987/05/15 ICEM ENGINEERING DATA LIBRARY . SOFTWARE RELEASE BULLETIN NOS 2 Level 678 --------------------------------------------------------------------.... 3.0 PSR/RSE CORRECTIVE CODE 3.0 PSR/RSE CORRECTIVE CODE The release of EDL V1.2.6 corrects the following PSR/RSE's. PSR/RSE DESCRIPTION ED10254 Character code for MSTRING file type defined incorrectly in database. ED10255 Inadequate documentation regarding IMF subset installation. ED10256 Error processing for IMF subset installation in EDL 1.2.5 inadequate. ED~0259 Application information in E125PRC in nonstandard form. ED10260 EDL in network configuration cannot delete files. ED10261 Some E125PRC file names and user numbers incorrect. ED10263 Deleting a file from the local host machine causes EDL error C8905. ED10264 IMF for 1.2.5 installed on EDL 1.2.3 required ovcaps load to' run' EDL. end . --_._•.. _ - - - - - _......._- CONTROL DATA CORPORATION ICEM DDN VERSION 1.63 INSTALLATION INSTRUCTIONS NOS Operating System Level: NOS 2 Level 678 Date: 5/15/87 DISCLAIMER NOS and its product set are intended for use only as described in this document. Control Data cannot be responsible for the proper functioning of undescribed features or parameters. Control Data Corporation gives the user permission to reproduce this document. 4197c SMD131525 Index Section I Release Description page 1 Section II Tape Formats and Files page 2 Section III Installation Instructions ICEM DDN Design/Drafting Package Page 4 ICEM DDN Advanced Design Package page 5 ICEM DDN Numerical Control Package page 6 Section IV ICEM DDN Verification Instructions page 7 Section V Plotter Verification page 7 9 APPENDICIES ---- .. Appendix A International Drafting Standards page Appendix B Terminal Set-up Procedures page 11 Appendix C GPL and G!G! Execution page 15 Appendix D Cyber 800 Tuning Guide for ICEM DDN page 16 _._._._--_._-_ _._._-----------_._----_._--_..__._-- _---_._...__ ... - -----_._--.. ... ._ CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 I. 1 5/15/S7 Release Description lCEM DDN is a computer-aided design and computer-aided manufacturing (CAD/CAM) system that runs under the NOS and NAM/IAF communications package. ICBM Design/Drafting Package The ICEM Design/Drafting file contains overlays for Basic Geometry, ANSI Mechanical Drafting, and Geometric Analysis. For International Drafting Standards, see Appendix A. ICBM Advanced Design Package The ICEM Advanced Design consists of all the overlays in the lCEM Design/Drafting plus additio~a1 overlays for Advanced Design. lCEM Numerical Control Package The IeEM Numerical Control consists of all overlays in lCEM Design/Drafting and leEM Advanced Design, plus additional overlays for Numerical Control. ICBM GPL lCEM GPL is a high level computer language designed to provide a user with features of the lCEM DDN product. The features are provided parametrically from within algorithms. The ICEM GPL system within the standard programs must first interpreted by ICEM consists of two parts: an interpreter located ICEM DDN and a stand-alone compiler. Source GPL be compiled before those programs can be DDN. The ICEM GPL compiler is provided with the purchase of any portion of ICBM DDN (Design/Drafting, Advanced Design, or Numerical Control) •. Hardware Requirements ICEM DDN requires the minimum hardware configuration for NOS and NAM/lAF. A maximum field length of 170,300 octal is required for execution. The user station is a Tektronix 4014 or 4016 with Extended Graphics, Tektronix 4105, 4107, 4109, 4113, 4114, 4115, or 4125, lEW 790 with TEKEM and Control Data Corporation 721. CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 II. 2 5/15/87 Tape Formats and Files All tapes are nine-track made with a density of 1600 cpi (n-PE). tapes are ANSI-labeled and in INTERNAL format (LB-KL.F-I) • All VSN-REL68 L-ICEMDD VSN-REL68A L-ICEMAD VSN-REL68B L-ICEMNC VSN-REL68C L-ICEMGPL ill #1 #2 #2 #1 #2 13 #1 #2 #3 INSTALL ICEMDDN #3 DDNSRB #4 DDNVER #5 DDNVIT #6 DDNUTIL 17 OPTIM #8 VERUTIL #9 TAPE 9 #3 INSTALL ICEMAD COPYLDR #4 INSTALL lCEMNC COPYLDR PPFULL 14 #5 #6 #7 118 INSTALL GPL GTGT GOLIB PFX1660 PFX6016 XREC170 XTRX170 Description of Files (I) Indirect Access File (D) Direct Access File COPYLDR (I) is a copy utility used in the integration of the Advanced Design or Numerical Control overlays into ICEM DDN Design/Drafting. DDNSRB (D) is a text file containing the Software Release Bulletin. This document explains the new features and provides general information regarding this release. ", (I) is the relocatable binary for the interface between leEM DDN draw files and UNlPLOT/UNIPOST. DDNUTIL DDNVER (I) is a CCL verification procedure file for the installation test of ICEM DDN. DDNVIT (I) is a verification script input file for lCEM DDN. GOLIB (D) is the absolute binary for the ICEM GPL interface. GPL (D) is the absolute binary of the leEM GPL Compiler. CONtROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 (D) GTGT _... _........ _............. 5/15/87 is the GRAPL-to-GPL Translator. See Appendix C for information on how 'to use this translator. ICEMAn * is the module of Advanced Design overlays only. It is integrated into ICEMDDN upon the execution of the INSTALL Procedure on tape REL68A. ICEMDDN (D) is the absolute binary for ICEM DDN zero overlay and the primary overlays. ICEMNC * is the module of Numerical Control overlays. It is integrated into ICEMDDN upon the execution of the INSTALL procedure on tape REL68B. INSTALL * is a CCL procedure to transfer the files on tape to disk under the user number under which the procedure is executed. The files are stored as either Direct (D) access files or as INDIRECT (I) access files depending on file size. All files are unloaded as PUBLIC, READ-ONLY files. OPTIM (D) is the relocatable binary PFX1660 (D) is the absolute binary for translating CY120 to CY170 IPARTD part files. PFX6016 (D) is the absolute binary for translating CY170 to CY120 IPARTD part files. PPFULL (D) is a text file containing expounded PP word library. 7APE9 (I) is a verification data file for DDNUTIL and OPTIM. VERUTIL (1) is a CCL verification procedure file for the installation test of ICEM DDN plotter interface. XREC170 (1) is an absolute binary needed for IPARTD file to file transferring when using HAMLET. XTRX17 0 (I) is an absolute binary needed for IPARTD file to file transferring when using HAMLET. PPFULL (1) Is a text file containing expanded PP word library. * ............. ... 3 These files are temporary files used during the execution of the INSTALL procedure • __. _ . _ - - - - - - - - - CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 4 5/15/87 III. Installation Instructions Installation of ICEM DDN Design/Drafting only Two tapes are needed to install the complete ICEM DDN Design/Drafting package. They are REL68 and REL68C. The tapes can be installed on any user number, however, it is recommended they be installed on user number APPLLIB from the console. The instructions assume the tapes are being installed from the console. If not, begin at the LABEL command and disregard the DROP at the end. X.DIS SUI,377774. LABEL, TAPE,VSN-REL68, L-ICEMDD,D-PE,F-I,NT. BEGIN, ,TAPE. DROP. Informational notes are displayed on the screen during the installation. The INSTALL procedure for REL68 will prompt the user when REL68C needs to be mounted on the tape drive. See Section IV for ICEM DDN Verification instructions. See Section V for ICEM DDN Plotter Interface Verification. See Appendix D, Section 3.2 for comments concerning having ICEM DDN as system resident. '----------_._--'--_.,-_.".- ,., ...... ,'--"-_... __ ._._---"._-,--_._-----.-._-- CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 5 5/15/87 Installation of ICEM DDN Advanced Design and pesign/Drafting Three tapes are needed to install the ICEM DDN Advanced Design package. They are REL68, REL68A and REL68C. The tapes can be installed on any user number, however, it is recommended they be installed on user number APPLLIB from the console. If not, begin at the LABEL command and disregard the DROP at the end. X.DIS SUI,377774. LABEL,TAPE,VSN-REL68A,L-ICEHAD,D-PE,F-I,NT. BEGIN"TAPE. DROP. Informational messages are dlsplayed on the screen as necessary. The INSTALL procedure for REL68A will prompt the user when REL68 and REL68C need to be mounted on the tape drive. See Section IV for ICEM DDN Verification instructions. See Section V for ICEM DDN Plotter Interface Verification. See Appendix D, Section 3.2 for comments concerning having ICEM DDN as system resident. CONTROL DATA CORPORATION lCEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 6 5/15/87 Installation of ICEM DDN Numerical Control, Advanced Design and Design/Drafting Four tapes are needed to install the lCEM DDN Numerical Control package. They are REL68, REL68A, REL68B and REL68C. The tapes can be installed on any user number, however, it is recommended they be installed on user number APPLLIB from the console. The instructions assume the tapes are being installed from the console. If not, begin at the LABEL command and disregard the DROP at the end. X.DIS SUI,377774. LABEL,TAPE,VSN-REL68B,L-ICEMNC,D-PE,F-I,NT. BEGIN"TAPE. DROP. Informational messages are displayed on the screen as necessary. The INSTALL procedure for REL68B will prompt the user when REL68A, REL68C, and REL68 need to be mounted on the tape drive. ~ee Section IV for ICEM DDN 'Verification instructions. See Section V for ICEM DDN Plotter Interface Verification. See Appendix D, Section 3.2 for comments concerning having ICEM DDN as system resident. -------------------------- CONTROL DATA CORPORATION IeEM DON I~STALLATION INSTRUCTIONS NOS 2 Level 678 IV. 7 5/15/87 I Verification of the ICEM DON (all packages) Log into NOS using one of the valid terminal types. Valid terminal types and set-up information can be found in APPENDIX B. In the instructions below, the use of 'username' should be replaced with the user number where the files were installed. The use of 'baudrate' should be replaced by the first digit of the baud rate of the communications line. For example, 3 is the baud rate of 300, 1 is the baud rate of 1200, etc. The use of 'terminal type' should be replaced by the user's type of terminal. The default is T4014. The terminal type specified must be one of the valid terminal types listed on page 3. GET,DONVER/UN-'username'. DONVER,'baudrate','username', 'terminal type'. Ignore the request for input. It is being supplied by the verification input file. The output is emulating a Tektronix 4014 terminal. The result should match the display in figure ICEM DDN-l. v. Verification of the leEM DON Plotter Interface Log into NOS using one of the valid terminal types. V~lid terminal types and set-up information can be found in APPENDIX B. In the instructions below, the use of 'username' should be replaced with the user number where the files were installed and where UNIPLOT/UNIPOST files reside. It is assumed lCEM DDN plotter interfacer files are installed on the same user number as UNIPLOT/UNIPOST. GET.VERUTIL/UN-'username'. VERUTIL,'username'. The procedure VERUTIL executes UNIPOST. following manner. AUTOMATIC HARDCOPY (yIN) ? 2. 4. 6. 4010 ASYNCHRONOUS 4014 ASYNCHRONOUS 4014 EGM ASYNCHRONOUS ENTER BAUD RATE ? UNIPOST will prompt you in the Specify Y if a hardcopy is desired and is available; specify N if not. Specify 6 as Tektronix terminal type. Enter the baud rate of the communication line (example 1200, 9600, etc ). The screen will display the CDC logo (ICEM DDN-l). When the logo is drawn, crosshairs will appear. Press any key (A through Z) and the screen will clear and return you to NOS. NOTE: Refer to the UNlPLOT Reference Manual for additional information. CONTROL DATA CORPORATION ICEM.DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 8 5/15/87 CONTROL DATA lCEM DON FIGURE leEK DDN - 1 __ __._- . _ - - - - - - - - - - - - - - - - - - .. ._-_ ....__._----_. CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 9 5/15/87 APPENDIX A INSTALLATION INSTRUCTIONS International Drafting Standards o German Drafting Standard (DIN) library and installation instructions are available by contacting the Control Data CAE software development manager in Frankfurt. Germany. - o French Drafting Standard library is unavailable. Questions may be answered by the Control Data CAE software development manager. Paris. - o Control Data France 27 Cours Des Petites Ecuries B.P. 139 77315 Marne LaVallee. Cedex 2 France British Drafting Standard library is unavailable. Questions may be answered by the Control Data design/drafting analyst in London. - o Control Data GMBH Stresemanna1lee 30 6000 Frankfurt Main 70 West Germany Control Data Limited Control Data House 179-199 Shaftesbury Avenue London WC2H SAX Swedish Drafting Standard library and installation instructions are available by contacting the design/drafting analyst in Goteborg. Sweden. - Control CAD/CAM Box 10. S-40120 Sweden Data AB Applications Baldersgatan 4 Gothenburg - ~--.-~~ ---- CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 o 5/15/87 Japanese Drafting Standard library and installation instructions are available by contacting the design/drafting analyst in Tokyo. Japan. - o 10 Control Data Japan. LTD. Sunshine Bldg •• 27th F. 1-1 Higashi-Ikebukuro 3-Chome Toshima-Ku Tokyo 170. Japan Chinese Drafting Standard Library and installation instructions are available by contacting the design/drafting analyst in Tokyo. Japan. - Control Data Japan. LTD. Sunshine Bldg •• 27th F. 1-1 Higashi-Ikebukuro 3-Chome Toshima-Ku Tokyo 170. Japan --- ~.--- -- -_.__. .. ~ ~.~~-.- .. ~~~~ .. --~. ~- ~- ... -. --~- ... CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 11 5/15/S7 APPENDIX B TERMINAL SET UP PROCEDURES The terminal used for the installation of ICEM DDN must be initialized. Instructions for initializing the 4014, 4016, 4105, 4107, 4109, 4113, 4114, 4115, and 4125 Tektronix terminals follow. Please refer to IEW790 with TEKEM manuals for 790 terminal initialization. .- TEKTRONIX 4014 and 4016 TERMINALS • 1. The following terminal strapping options are for initial terminal installation. a. ECHO - ON b. GIN terminators - CR only c. CR effect - CR d. LF effect - LF 2. Turn the terminal power on. The 4014 POWER switch is on the front . lower right corner of the pedestal stand. The 4016 POWER switch is located on the right side of the terminal head. The green POWER indicator, located on the keyboard, will light when power is switched on. 3. Allow the terminal to warm up. Warm up is complete when pressing the RESET PAGE key completely clears the screen. 4. Set the ASCII/ALT switch to the ASCII position. S. Initialize the OPTION 1 or OPTION 20 according to the procedure below, as applicable. 6. To obtain the small character size, set the terminal to LOCAL mode. Press the ESC key and the j (semicolon) key together and return to LINE mode. 7. Dial the appropriate telephone number, if applicable. 8. Press the RETURN key to obtain the login FAMILY message. -----_._- - - - - _ . ---------_ .. __ ... __ ._ .... - .-.- ._."._ .............. -........ _....... " .... - 'CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 12 5/15/87 OPTION 1 INITIALIZATION 1. Select the appropriate baud rate switch setting using the BAUD RATE switch located at the rear of,the pedestal stand. 2. Set the HALF/FULL DUPLEX switch to FULL. 3. Set the INTF/OFF/AUX switch to INTF. 4. Set the TTY LOCK key. OPTION 20 INSTALLATION - - NOTE - If the terminal is equipped with both the OPTION 1 and the OPTION 20, set the INTF/OFF/AUX switch of the OPTION 1 to OFF. (Asynchronous lines only). Place the terminal in LOCAL mode. Press the SHIFT key and the CNTL key together. While both the SHIFT and CNTL keys are depressed, press and release the RESET key; then press the P key and release all keys. Place the terminal in LINE mode. _ Set the CODE EXPANDER switch to OFF. TEKTRONIX 4105, 4107, 4113, 4114, 4115 and 4125 TERMINALS Complete the following to set up the Tektronix 4113, 4114, 4115 or 4125 terminal. 1. Turn the terminal power on by pushing the POWER button. 2. Allow the terminal to initialize (some keys on the keyboard remain lit until the terminal has completed its initialization). 3. Press "the SET UP key so the terminal operating modes can be changed at the keyboard. An asterisk (*) should appear to the left of the cursor. CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 4. 13 5/15/87 Enter: STA to display the released terminal status settings. 5. Ensure the termina~ has the following settings. The remaining Tektronix 4105. 4107. 4109. 4113. 4114. 4115. and 4125 terminal status settings will either be set by ICEM DDN or will not affect the operation of IeEM DDN. To change a setting. reenter the new setting. Status 4105, 4107, 4109 4113. 4114. 4115. 4125 TBSTATUS emulation only Not Applicable Out for 4014 . TBHEADER CHARS emulation only Not Applicable Out for 4014 RLINE LENGTH 140 140 ECHO, Yes Yes LOCK KEYBOARD No No SNOOPY No No BAUDRATE Applicable Baud Rate Applicable Baud Rate FLAGGING INPUT INPUT EOLSTRING Not Applicable Not Applicable BLOCKMODE " No No (4113 only) BREAKTIME 100 100 - - - - - - - - - - - - - - - ----,-------,---"--- --------_. __ .- - -- ..... - ._-- --- CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 14 5/15/87 Status 4105, 4107, 4109 4113, 4114, 4115, 4125 QUEUESIZE 8100 8100 DUPLEX' Not Applicable Full (4113 only) XMTDELAY 0 0 XMTLIMIT Applicable Baud Rate Applicable Baud Rate Without Echoplex NL NL With Echoplex LF LF BYPASS CANCEL ._ .. ,- ........_-"""... _-,_._.. _._, .,------------- - - - - - - - - - - - - - - - - - - " , .. ,'---"........ CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 15 5/15/87 APPENDIX C Using the GPL Compiler Log into NOS using one of the valid terminal types. Valid terminal types and set-up information can be found in APPENDIX B. In the instructions below, the use of 'username' should be replaced with the user number where the files were installed. In addition, 'source program' should be replaced by the file name of your GPL program; 'grapl program' should be replaced by your translated GRAPL program file name; 'output file name' should be replaced by our output file name (default is OUTPUT); 'list file name' should be replaced by the file name you wish the translated program to be put on. To create a new GPL object library: ATTACH,GPL/UN-'username'. GET,'source program'. GPL,I-'source program',L-GPLLIST. DEFINE,GPLLIB. LIBEDIT,B-GPLOBJ,P-GPLLIB,C,Z./*BUILD GPLD. REWIND,·. To add additional compiled programs to an existing GPL object library: ATTACH, GPL/UN-'username'. GET,'source program'. GPL,I-'source program',L-GPLLIST. ATTACH,GPLLIB/M-W. LIBEDIT,B-GPLOBJ,P-GPLLIB,C,z.I*BUILD GPLD. REWIND,·. Using the GRAPL to GPL Translator GTGT E~~mple: ATTACH,GTGT/UN-'username' GET,'grapl program' GTGT,I-'grapl program',o-'output file',L-'list file' -NOTETHE TRANSLATION IS NOT ALWAYS 100%. CHECK FOR REMARKS IN THE GPL SOURCE OUTPUT. (For more information, see Appendix F of the ICEM GPL Reference -Manual.) - - - - - - - - - _ .__._._._------_ ...... -. CONTROL DATA CORPORATION ICEM DDN INSTALLATION INSTRUCTIONS NOS 2 Level 678 16 5/15/87 APPENDIX D CYBER 800 TUNING GUIDE FOR IeEM DDN --_._---------------- 1 800 Tuning Guide for ICEM DDN 87/05/15 Table of Contents 1-1 1.0 INTRODUCTION: • • • • • • 1.1 BACKGROUND - PROBLEMS •• 1-1 .... 2.0 OVERVIEW OF 800'5 • 2.1 800 FEATURES 2.2 800 MEMORY USE •• 3.0 TUNING METHODS •• 3.1 STEPS FOR TUNING • • • • 3.2 DDN SYSTEM RESIDENT • : .• 3.3 DDN OVERLAYS IN CENTRAL MEMORY •• • • 3. 4 CPU BOUND 800 • • • • • • • • • 3.5 CPD READING • • • • • • • • • • 3.5.1 SYSTEM PARAMETERS AND EST CONFIGURATION • • 3.5.2 SYSTEM CONTROL INFORMATION • • • • 3.5.3 INTERVAL SAMPLE ••• • • • 3.6 PROBE • • • • • • • • • • .'. • 3.7 CONSOLE WATCHING •• • • • • • • • 3-1 3-1 3-2 3-2 3-4 3-4 3-5 3-5 3-6 3-7 3-7 4.0 PERMANENT/TEMP FILE ALLOCATION 4-1 .... 5.0 EDL TUNING 7.0 APPENDIX 5-1 6-1 6.0'CONCLUSION 7-1 • _ - - - - - - - - .-_.._.. . 2-1 2-1 2-2 __ .. ,.._..... ".,., ,-_._-'._----_.------ .. ,_ ..... _... "" ..•. ,-" ... 1-1 800 Tuning Guide for ICEK DDN 87/05/15 1.0 INTRODUCTION: ------------------------------------------------------------------~~ 1.0 INTRODUCTION: 1.1 BACKGROUND - PROBLEMS This guide will explore possible solutions to some common tuning situations. of the The main problem is that users are expecting to set-up and play the hardware/software with no adjustments. This practice causes the site to run with the default setup parameters which were built for a small job environment. DDN is usually overlay bound and has a rather large field length. Depending on the disk configuration, the site is usually disk bound due to overlay loading and swapping DDN to disk. In the cases where the site has a lot of memory, the memory is not being utilized because no one has designated it as a "DE" equipment for DDN overlays and/or a swap device. Because system analysts don't have a quantitative method of ascertaining what tuning functions cause improvements, tuning is ~ot attempted. By using CPD, CTIME, RTlME, and ICEM DDN trace files, an objective index of performance can be obtained and improvements made. --------- .. _.._-_._----_._. 2-1 800 Tuning Guide for ICEM DDN 87/05/15 2.0 OVERVIEW OF 800'5 . -------------------------------------------------------------------- 2.0 OVERVIEW OF 800'5 . 2.1 800 FEATURES The 800 has the following features: The 800 has a high speed central processing unit that runs with a memory that can be very large - 2 to 128 megabytes (262 thousand to 16 Million central memory words). * * * Peripheral processors operate at 4 times the original PPU speed. * The range of ability for each machine has more than one dimension. As you go up the line in CPU power, the memory size can also be upgraded. The cache memory speeds up effective memory cycle. The 800 microcoded instruction set allows both NOS and NOS/VE operating systems to exist and run in the same machine (dual state). The following chart shows the different models and the allowed memory size options and multiple CPU option: MODEL 810 810A 815 825 830 830A 835 840 845 850 855 860 870 990 990E 995E ----------- MEMORY SIZE OPTION (Megabytes) 2 4 8 12 16 32 64 96 128 X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X ..-._ ...__.._,_ .. _... -._------ .- .. X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Dual CPU NO NO NO NO YES YES .NO NO NO NO YES YES YES YES NO YES 2-2 800 Tuning Guide for ICBM DDN 87/05/15 2.0 OVERVIEW OF 800'S 2.1 800 FEATURES -------------------------------------------------------------------. The 840A, 850A, 860A and 870A have an I/O 20 PPUs and 24 channels. subsystem of In dual state only one processor can be executing in the CYBER 170 mode. Currently 16 megabytes is the maximum memory that use. NOS can It is the memory expansion characteristic that is most interesting for large applications like DDN. It has been observed that customers are overlooking the ability of the 800 to use this memory in many different ways. 2.2 800 MEMORY USE The 800 memory can be used in the following ways: (1) Job area - the job execution area is normally about 262K but can be bigger or smaller. Don't allocate more job area than it is possible to use (i.e. job area <-= number of control points x max job length). (2) Swap area - Rather than roll the job to disk, it can be swapped from memory to memory to avoid the disk accesses. (3) System resident - specific overlays and/or PPU programs can be stored and retrieved from memory to avoid disk accesses. (4) Buffer area for -buffered disks. (5) NOS/VE execution area. All the above memory allocations are controlled by deadstart parameters in the CMR, EQPD, and IPRD decks. The EQPDxx entry for UEH is - "EQ005-=DE,ST-=ON,ET-EH,SZ-4000." (1 million words of UEM). The IPRDxx entry for the secondary rollout threshold is - "SRST-2000" ( The maximum of 200,000 job field length will be rolled to the secondary rollout). -----_._-_ ...__.. __ .. _-_. _... .._--_._--_. __ .. __ __ ._---_. __ . --- 3-1 800 Tuning Guide for ICEM DDN 87/05/15 3.0 TUNING METHODS 3.0 TUNING METHODS 3.1 STEPS FOR TUNING The following is a summary of the steps one can go through tune 800s for ICEM DDN: to 1) Run CPD - Find what the bottlenecks are. Tune by making NOS configuration changes such as system resident and channel/disk configuration (see section 3.5). Check disk use percentages from the CPD run. 50-60~ is pretty high. Moving overlays to eM or UEM and/or allowing ICEM DDN to run as system resident will help speed up the product and decrease disk access. Also, try to arrange your configuration so that equal access is occurring across all disk channels. Avoid channel 0 because it cannot be alternated in each mass storage device Equipment Status Table (EST) entry. 2), Run ICEK DDN with the T option on and collect overlay load numbers (CT file) for a given script. The IT file, resulting from the T option run is used for input (I-Ifn) so that the run can be repeated for comparison after each tuning attempt (base timing). A program included in the appendix counts and sorts the counts by overlay for each overlay that was loaded during the script execution. 3) Based on CPD and the CT counts, move selected overlays into CM (Central Memory) and/or UEM (Unified Extended Memory). In level 630 of NOS a limited number of overlays can be put in CM, and near 400K the system hangs. The work around is to put additional overlays. in UEM. At this level of the system, there does not seem to be any performance difference between overlay loading from CM or UEM. 4) Recheck response time by running a script in a quiet system with CTIME and RTlHE control cards on each side of the ICEM DDN call. These numbers will tell you the amount of CPU time and real time used to make the run. Also, rerun CPD to check what is happening to the system resources. There is a Timesharing Instrumentation Package which measures response time, think time . and transaction rates of IAF (LDS Publication number 15190016). This package will show how tuning has affected response time • _--_...__ ...._._._ _._ ___ . ... ..•.. .. .. .. ----._------ 3-2 800 Tuning Guide for ICEM DDN 87/05/15 3.0 TUNING METHODS 3.2 DDN SYSTEM RESIDENT 3.2 DDN SYSTEM RESIDENT The advantage of having DDN system resident is that when it is in the system, more than one copy of the code is available from multiple disk channels. Also, selected overlays can be resident in CM. Don't bother moving ICEM DDN to the system if you have only one channel to disk and you don't want to move overlays to CM or UEM. Also, remember that ICEM DDN will increase your system file by about lOOK PRUs on each device that is designated as a system device. On small capacity disk systems put ICEM DDN on the deadstart tape rather than on a permanent file which is SYSEDITed after deadstart. This will save lOOK PRUs of permanent file space. GPL overlays must be on a local file at execution time for GPL users. It currently does not run any other way. Hake an entry in the LIBDxx deck of "*FL ABS/ICMEDDN-6560" so that it will execute from the system file. 3.3 DDN OVERLAYS IN CENTRAL MEMORY The problem with NOS 800 performance is caused by DDN having to load overlays from the disk. Generally, if the most frequently called overlays can reside in memory, the disk accesses will be much lower. If all the overlays that are called are put in memory, a script will run as well as it would on NOS/VE (virtual environment). Of course, the data caching ·won't be as good as VE but the performance should be considerably better than before the overlays were put in CM. 3-3 800 Tuning Guide for ICEM DDN 87/05/15 3.0 TUNING METHODS 3.3 DDN OVERLAYS IN CENTRAL MEMORY Following is an example of the performance improvement on an 855 with the overlays in CM and other numbers showing relative performance: SYSTEM Running time CPU time Comment 374 18 78 138 13 12 48 78 DDN153 on 844s (System file) DDN153 on FMD's 760 NOS 760 NOS 371 291 7 7 DDN157 on 844s (System file) DDN157 on FMDs (Local file) 855 NOS 855 NOS 267 160 9 9 DDN157 on Disk (System file) 3 overlays in CM+System file 760 855 830 810 NOS NOS/VE NOS/VE NOS/VE " " " " " " The 100 second improvement for the 855 NOS is caused by reducing disk accesses. In theory, if all the overlays that ar~ called are put in memory, the script would run as well as the 855 NOS/VE (18 seconds). Also, notice the CPU time for each of the above machines. The CPU time requirement for DDN157 is less than DDN153 •. -The 830 and 810 is 4 and 6 times less capable than the 760 or 855. If the site is CPU bound, the moving of the overlays into memory may not help response time during p~rio~s of CPU saturation. The following table typical script:· Overlay ------CL04 CL52 CL02 CL72 CL270 CL75 CL51 CL14 CL54 * Load Count ---------276 247 136 135 97 88 62 56 48 summarizes the overlay situation with a Accumulated Sum* Field Length of Overlay* --------------- ----------------------53040 52551 43215 23066 44031 60042 54513 41300 30441 54K 126K 171K 215K 261K 340K 415K 457K 507K Field length and sum are in octal. - - - - - - - - - - - - - - - " - " , , ..- .._.. __ ._ ..__ .._"._---- 3-4 800 Tuning Guide for ICEM DDN 87/05/15 3.0 TUNING KETHODS 3.3 DDN OVERLAYS IN CENTRAL KEMORY These 9 overlays were loaded 1145 times. There were overlay loads in all with a total of 32 overlays used. 1442 After the 4th or 5th most freguently loaded overlay, the payoff from having the overlay in Central Memory (CM) goes down. The rest of the CM can be used for swap area. Both of these uses take away some CPU usage that would be normally available to user programs. But because most sites are disk bound, the swapping and overlay loading from memory to memory saves on disk access and speeds up the user response time. If CPD runs and RTIME and CTIKE-control cards are used around a script run before and after these tuning suggestions, the effect can be measured. With less disk access the product (ICEM DDN) will speed up and will make more use of the CPU so that swapping and overlay loading will occur faster. This can have a secondary effect of causing more CPU utilization due to more jobs (through CPU swapping) having access to the CPU and less disk access due to overlay loading from memory to memory loading. This secondary effect may necessitate a reduction in the the job switch delay so that the CPU is shared better between competing jobs. In any case, the above tuning should have a positive effect on response time for the average ICEM DDN user. 3.4 CPU BOUND 800 If your site is CPU bound (95-99~) , the moving of the overlays to Central Memory may cause the individual ICEM 'user to run a lot faster but when a large terminal load is present the total throughput may decrease. You may take steps to decrease the CPU usage to optimize. Because the CPU is used to move ··overlays around in memory, the moving of overlays to disk may decrease CPU usage. This will slow down the terminal response for the user at light loaded times but should make the user at CPU bound times run better. This situation seems to be rather rare and is found only on the 825s and lower machines. In determining if your site is CPU bound don't be mislead by maintenance jobs or batch jobs which soak up the CPU when the time-sharing.jobs are not running. 3.5 CPD READING CPD or TRACER (NOS System Maintenance Reference Manual 60459300) and PROBE are used for statistical analysis of your 3-5 800 Tuning Guide for ICEM DDN 87/05/15 3.0 TUNING METHODS 3.5 CPD READING --------------------------~----------------------------------------~ system performance. The data is used to determine areas where problems occur, where improvements in design and system tuning can be made. These products work by periodically gathering data about the system and writing the data to a file. TRACER is made up of 4 programs: , 1) ICPD - Starts up CPD PPU program 2) CPD - CPD is a dedicated PPU program which monitors system activity. Data is written to a direct access permanent file for future analysis. 3) ACPD - A post-processor program which generates an output report from the direct access permanent fi.le wri tten by CPD. See the NOS Maintenance manual (60459300) for details of calling parameters for TRACER. The following sequence will start and complete TRACER operation: 1) ICPD,pl,p2, ••• pn. (starts CPD up) 2) ENDCPD. (ends CPD data gathering) 3) ACPD,p1,p2, ••• pn. (processes the CPD data and generates a report) The ACPD report is in three sections 1. 2. 3. System parameters and EST configuration. System Control Information. Interval Samples. 3.5.1 SYSTEM PARAMETERS AND EST CONFIGURATION The System Parameters relate such things as the start date and time, report interval, memory size, UEM, number of PPUs and various lengths of software tables. The EST table is dumped showing the channel and disk connections. 3.5.2 SYSTEM CONTROL INFORMATION The System Control Information relates what the priority is for each job class. The BC, TS, and DI classes are especially important to good system response. The BC and DI should have a lower PR (CPU priority) than the TS class. This will allow time-sharing to always get the CPU before BC or DI can get it • ...._."."."" .. _._ ..... _..... - .......- ----------- 3-6 800 Tuning Guide for ICEM DDN 87/05/15 3.0 TUNING METHODS 3.5.2 SYSTEM CONTROL INFORMATION The other important parameters are the UP (upper priority limit) and LP (lower priority limit). These parameters are set based on how often batch jobs are rolled in and out without ever getting executed. If there is usually a lot of CM available, the UP and LP can be lower for batch and detached jobs than for time-sharing jobs. These parameters control the rolling out of batch or detached jobs when a time-sharing job requests more memory than what is currently available. If the execution memory is small in comparison to the field length requests, the batch and detached jobs should have the same UP and LP so that jobs are not rolled in and out without doing any work. The NJ parameter can help this ~ituation. By controlling the number of batch jobs that can execute at the same time, the batch field length can be controlled. The NJ parameter for time-sharing controls the number of users allowed. The FL and AM parameters for each job class can be designated to limit by job and/or job class how much Field Length (FL) may be used and when to schedule the job to CM. These parameters can be used to partition the memory by job class and run specific jobs at a selected time of the day. 'The CM parameter controls how long the UP priorities are in effect. With faster CPUs a sort duration 4-5 seconds is desired so that users that are running batch jobs in time-sharing mode are dropped down to the batch priority (assuming that batch priority is the same as the time-sharing lower bound priority). Thus,. short duration time-sharing tasks will get the most attention. 3.5.3 INTERVAL SAMPLE The following table shows some of the parameters and what action might be taken to improve performance when a high percentage of use is shown: Parameter (high percentage) PPUS ACTIVE NO PPU AVAILABLE CHANNEL ACTIVE CPU USAGE IDLE SYSTEM Cause(Information Not enough Disk Channels or PPUs. Same as PPUS ACTIVE. 50-60+ up means that more disk channels will improve response time. High idle percent means the CPU is not being used could be caused by the system being disk bound. System Software using excessive CPU. 3-7 800 Tun.ing Guide for ICEM DDN 87/05/15 3.0 TUNING METHODS 3.5.3 INTERVAL SAMPLE SUB-SYS SYS ORG USER FL AVAILABLE IAF USERS TRACKS AVAILABLE Same as SYSTEM. Same as SYSTEM. You are getting as much as you can out of the system. Application CPU usage may be excessive. Large percent is good - lots of room to run jobs. If coupled with secondary rollout filling up, FL needs to be moved to the secondary rollout area. Number of users. When a device has only 10% of its tracks available the system automatically does not use this device for TEMP files. TOTAL ROLLOUTS SECONDARY ROLLOUTS TOTAL SECTORS ROLLED SECONDARY SECTORS ROLLED INSUFFICIENT CM NO CONTROL POINT The statistics on total and secondary rollouts will tell you if your secondary rollout threshold is large enough and how much your secondary rollout device is being used. Number of times no CM was available to bring in a job. This number will tell you if you have enough control points defined. 3.6 PROBE The PROBE utility measures the following: 1) The number of times a PP routine was loaded. 2) The number of CIO RA+1 requests by function number. 3) The number of PP requests to CPUMTR by function number. 4) The number of MTR requests to CPUMTR by function number. S) The statistical data accumulated in low central memory - includes such items as number of sectors rolled and number of rollouts. PROBE data gathering is enabled at deadstart time by an IPRDECK entry. SYSEDIT resets the PROBE data tables to zero. PROBE is useful in moving PP routines to eM when they are called frequently enough, thus improving system performance. 3.7 CONSOLE WATCHING Many times all the various tools are not as useful as just watching the system console for .signs of thrashing and/or particular user abuse. The following items are worth watching for: 1) Users running batch jobs in time-sharing mQde. 2) Batch jobs that are being rolled in but not getting the CPU before. they are rolled out again • ..,"--_._--.,--...,---., '" '.",,_ ..... _--------- 3-8 800 Tuning Guide for ICEM DDN 87/05/15 3.0 TUNING METHODS 3.7 CONSOLE WATCHING 3) Jobs that have excessive resource requests over extended peri s. 4) Maintenance jobs running at too high a priority and/or too many running. One job (CT7) is probably enough. Too many maintenance jobs cause a forced rollout .every time a time-sharing job is brought in. 5) Permanent file dumping and loading during the prime shift will slow down or stop any PF requests by your users. 6) NOS/VE running in a dual 800 can have a default priority that allows NOS/VE to take the CPU away from NOS. ---_._._-_._.- .. -....._ - - - __ _------_._ _._ ._-----_._-_. .. .. ..._.. _--- 4-1 800 Tuning Guide for ICEM DDN 87/05/15 4.0 PERMANENT/TEMP FILE ALLOCATION 4.0 PERMANENT/TEMP FILE ALLOCATION It has been found that allowing temporary and permanent files to be allocated on every device seems to be the best strategy to spread the load onto as many units as possible. 5-1 800 Tuning Guide for ICEM DDN 87/05/15 5.0 EDL TUNING --------------------------~----------------------~--------------~~ 5.0 EDL TUNING In many sites the Engineering Data Library (EDL) runs with ICEM DDN and can contribute to excessive resource use. The following EDL file (IMF2STF/UN=IMF) should have fhe following values for best performance: 3 NUMBER OF USER PROCESSES TO CHECK FOR EACH MTR LOOP 2 SEMI-IDLE RECALL TIME (MILLISECONDS) 15 ACTIVE RECALL TIME (MILLISECONDS) 1 K-DISPLAY REFRESH CYCLE 50 MAX NUMBER OF TIMES IDLE BEFORE SCP SWAP-OUT 30 MAX NUMBER OF CONNECTED USERS 10 MAX NUMBER OF OPEN DATA-BAS~S 170 MAX NUMBER OF ATTACHED FILES 3 NUMBER OF ALLOCATED USER STACKS 5 NUMBER OF INPUT BUFFERS 1 NUMBER OF INPUT QUEUE ENTRIES 3 NUMBER OF I/O BUFFERS o NUMBER OF TRANSACTION FILES ON ECS 1 NUMBER OF LONG WAKE-UP WAITS ALLOWED AT STACK 2 NUMBER OF SHORT WAKE-UP WAITS ALLOWED AT STACK 6000 LONG WAKE-UP WAIT SWAP-OUT DELAY 4000 SHORT WAKE-UP WAIT SWAP-OUT DELAY 30 PARCEL STACK PREEMPTION DELAY 30 SINGLE READ STACK PREEMPTION DELAY 1 TRACE The file DEFSTF/UN-IHF (installation file for IHF) should be used as a model. The default values which have been changed above are: ACTIVE RECALL TIME TRACE - 1 ~ 30 Also, journal logging may be turned off for the EDL database. This will save considerable overhead. However, if the system crashes with the database open, the database file may have to be reloaded from the last permanent file backup, instead of being recovered to the point of failure. To turn off journal logging, log into the account where the EDL database file E120DDB resides, and type the following commands: GET,CHLOG21/UN~IHF CHLOG21,OFF,E120DDB,E120LOG • . .... __..•. _._ ....... _--- .. 6-1 800 Tuning Guide for ICEM DDN 87/05/15 6.0 CONCLUSION -----------------------------------------------------------------_.6.0 CONCLUSION Due to the many ways DDN is used, and considering the many other applications that are run on 800s, the tuning recommendations mayor may not be applicable. If after you have tried to tune your system it still has bad response time, please send CIM Field Support the following information and they will try to assist you: 1. Your name and phone number. 2. Describe response time with·the general areas of DDN that are used. 3. Computer model (810, 830, 860, etc.), memory size, and length of time your system has been running DDN. 4. NOS level of the operating system and indicate if running dual state. 5. 'Disk configuration - Channels, disk models, and hookup configuration. 6. DE entry - memory allocation - Job area, overlay, and swap area. 7. List the names of DDN overlays that are resident in memory. 8. If possible, include a Tracer listing which contains much of the above information. The Tracer listing should be from an average day. --_._............ ---.--. ----- ......... _.-. ----_._--_... .- ---_._...__ ..----.- .. .,. . 7-1 800 Tuning Guide for ICEM DDN 87/05/15 7 .0 APPENDIX 7 .0 APPENDIX The following procedure and program will count the times each overlay is called and the total number of overlays called by processing the CT file which is output from a ICBM DDN run with the T option on: .PROC,SORTCT. PACK,CT,TAPE2. FILE,TAPE2,BT-C,RT-U. FTN5,I-SORTC,BaLGO,L-L,OPT-2. LGO. NOTE./ RESULTS ON FILE LIST. . PROGRAM SORTCT(INPUT,OUTPUT,TAPE2,LIST,TAPEI-LIST) INTEGER IBUF,INUM(512) REWIND 1 REWIND 2 ITOTAL -= 0 READ(2,END=15)IBUF IF(IBUF .GT. 512)GO TO 5 IF(IBUF .LT. O)GO TO 5 lNUM(IBUF) -= lNUH(IBUF)+1 ITOTAL -= ITOTAL+l GO TO 5 . ~DATA,SORTC. 5 C 15 20 30 9000 1000 2000 3000 DONE READING CT. WRITE(I,3000) DO 30 J-1,512 K -= 0 LASTBG - 0 DO 20 1-1,512 IF (INUH(I) .GT. LASTBG) THEN LASTBG -= INUM (I) K- I ENDIF CONTINUE IF(LASTBG .EQ. O)GO TO 9000 WRITE(1,1000) K,INUM(K) INUM(K) - 0 CONTINUE WRITE(1,2000) ITOTAL FORMAT (' CL - ',03,3X,II0)" FORMAT (' SUM - ',110) FORMAT ('l','OVERLAY NUMBER',' END COUNT') end --------- , External Reference Specification I. OVERVIEW The Electrostatic Plot Subsystem (EPS) is a NOS Version 2 subsystem that removes raster formatted files from the NOS plot queue and plots them on an electrostatic plotter. The plot files are INTERSYS one bit per pixel images and can be generated by INTERSYS, XPLOR, MCIDAS, XAMIN, or ~y UNIPLOT/UNIPOST. EPS used Benson electrostatic plotters. Three Benson models are supported; 9324, 9336, 9344 with resolutions of 200 dots per inch. Benson plotters are connected via the Channel Interface Unit (CIU). EPS will support multiple CIUs with each CIU having multiple plotters. EPS provides the NOS operator status and control through the NOS K-display facility. EPS is comprised of three major software modules: 1) 'PLOTSS -- Cyber CPU resident subsystem code 2) XOO -- CIU/Plotter PP driver 3) ICSYS -- CIU resident plotter driver See Fig. 1 for the relationship of the major compomnents of EPS. • ----------------------------- --------------------------------------------------------------- ------------------- ---------------- II. USER INSTRUCTIONS The user can ~ause EPS to plot a file by placing the file in the NOS plot queue. The file can be placed into the plot queue by using the ROUTE control statement. To plot a file the user would execute the following control statement: ROUTE,lfn,DC=PL. where ulfn" is the local file name of the file to be plotted. E~·:ecuting this statement would place the file into the NOS plot queue and EPS would plot the file on the first available plotter. If the resolution of the plot file exceeds that of the plotter, EPS will truncate the plot file to fit on the plotter. If the user wants the file to be plotted on a plotter with a known resolution, the following statement should be eNecuted: ROUTE,lfn,DC=PL,ID=id. where Hid" is the plotter type identification. lIid are: The legal values for II 24 Specifies a 24 inch plotter with a resolution of 4224 pi >:el s per line. " 36 Specifies a 36 inch plotter with a resolution of 7040 pi ;.{ el s per 1 i ne. 44 Specifies a 44 inch plotter with a resolution of 8690 pixels per"line. -----------" ,----- .\ .. ;' I,I , :.. ~ '... ~: :, ", --------------- - -- -- ----------------------- ----------------------------------------------------- --------~ III. NOS OPERATOR INTERFACE The NOS operator communicates with EPS through the K-display. The K-display provides a one line status display for each plotter connected to EPS. The format of the status line is: EST JSN STATUS eq Ifn NOT READY HARD ERR. LOW SUPPa eq Indicates the EST ordinal of the plotter. lfn This field contains either the JSN of the file currently being plotted on this plotter or either IDL or IDL*. The character string IDL indicates that this plotter _does not have a plot file assigned to it. The character string IDL* indicates that this plotter has just finished plotting a file and EPS is waiting for the plot buffers to clear. If IDL* is displayed for an extended time and no other status indications are displayed, either a hard~are or software error exists. NOT READY The presence of this character string indicates that the plotter is either powered-off or is off-line. A plot file will not be assigned to an idle plotter if the plotter is NOT READY. HARD ERR. The presence of this character string indicates that a hardware error was detected in the CIU. The only way to clear this error is to IDLE EPS. LOW SUPPa The presence of this character string indicates that the plotter is low on either paper, toner, or concentrate. A plot file will not be assigned to an idle plotter if the plotter has LOW SUPPLIES. If a plot file is being plotted when the LOW SUPPa indicator appears, the entire plot file will be plotted. The NOS operator can control the plot process by entering one of the following commands: K.eq,REPLOT K.eq,END where fleq" is the EST ordinal of the plotter. The REPLOT command is used to halt the plotting of a file and return the file to the plot queue. The END command is used to halt the plotting of a file. The END command does not return the file to the plot queue. IV. INSTALLATION INSTRUCTIONS EPS is supplied on a single nine-track magnetic tape recorded at 1600 bpi. ·The installation tape contains eight files. The contents of the files are: File 1 A CCL procedure to copy each of the remaining files to a permanent file. File 2 A CCL procedure to make the necessary system modifications and assemble/compile the EPS modules. The analyst performing the installation should inspect this file to assure that the NOS system modifications do not conflict with local site modifications. This procedure produces a binary file of corrections/additions for the system deadstart tape and also a number of binary files used for the initialization of EPS. This file is copied to file INSTALL. File 3 This file is a sample CCL procedure file that will be invoked wHen EPS is started. This file is copied to file EPS. File 4 This file contains the modify OPL for EPS. copied to file EPS2PL. File 5 This file contains the binary load module for the CIU. It~s copied to file PDPLGO~ File 6 This file contains the binary for the PDP Compass assembler. It~s copied to file PDP. This file will normally not be used. It will only be used if modifications are required to the CIU program. File 7 This file contains a test plot. file TESTPLT. File 8 This file contains a test plot a bit more interesting than the plot on file 7. It~s copied to file DRAGON. It~s It~s copied, to The steps to follow to install EPS are: 1. Assign the local file name "TAPE" to the installation tape and e}·:ecute "BEGIN" TAPE. " 2. Inspect the NOS system modifications in file INSTALL for any conflicts with local site modifications. 3. Execute BEGIN, ,INSTALL. This will create a binary file of additions and changes for the system deadstart tape ._---_._---_._--_.- ......... _....... _. __ __ .. _.. .- ------------- and· also other files that will be used to initialize EPS. The files created by this procedure are: 4. LGO This file contains the additions/corrections for the deadstart tape. FVTESTB This file contains the binary for a quick test on the CIU. The test transfers random data to the CIU and then reads it back and checks for errors. This test is executed each time EPS is initialized. FVLDRB This file contains the binary for the CIU boot loader. It reads the CIU program on file PDPLGO and loads it into the CIU. VRETURN This file contains the binary for a program used by the procedure file EPS to return a local file assigned to equipment type VT. LIST This is a local file that will contain the list oufput from the modification of the system OPL. It will also contain the list output from COMPASS for the assembly of the modified routines (CPUMTR is not listed, the modificatio.n is trivial and the listing huge). LIST2 This is a local file that will contain the list output from the COMPASS/FTN5.assembly of the EPS modules. The program for the CIU is not included in this listing. .Create a new CMR deck wi th a EST entry for the CIU. The format of the EST entry is: EQxx=VT,ST=ON,CH=xx,EQ=O,UN=11. The unit numbers associated with the CIU are four bit numbers. 'The lower three bits designate the physical device and bit 3 indicates if this unit is bootable. The CIU program supplied with EPS has three units defined: Unit 0 Unit 1 Unit 2 Ramtek display used with INTERSYS (an interactive image processing system). Benson plotter. Benson plotter with an Logic Sciences HSR-11 rasterizer. This version of EPS does not support the HSR-11 rasterizer. If the system will include both a Ramtek display and a Benson plotter, the EST entries should be: ----- -.----- . . .- - - - - - -.._....... ... __._ .. EQxx=VT,ST=ON,CH=cc,EQ=O,UN=OO. EQyy=VT,ST=ON,CH=cc,EQ=O,UN=ll. RAMTEK BENSON This will allow INTERSYS and EPS to share the CIU but will only allow the CIU to be booted from unit 11 which should always be assigned to EPS. 5. Create a new deadstart tape. 6. Create a plotter configuration file. This file must be an indirect access permanent file and should have the name PCFILE. It~s accessed by the procedure file EPS when EPS is initialized. Since all EST entries associated with a CIU are identical, there is no distinguishing field that specifies a particular EST entry as being a plotter or the type of plotter (9324, 9336, 9344). PCFILE contains a coded line image for each plotter in the system. The format of the lines in PCFILE are: EQ=~{}< , t yp e • where xx is the EST ordinal and type is one of the following, 9324, 9336, or 9344. 7. Modify the file EPS to reflect the proper user index and EST ordinal. Place a copy of EPS under user index 377777. ... _-_.._--_._-_._-_.... _ - - _ . _ . _ - . -------------- v. PLOTSS -- CYBER CPU RESIDENT SUBSYSTEM CODE DATA STRUCTURES The routines in PLOTSS use a data structure comprised of a PLOTTER TABLE, a CONTROLLER TABLE and FETs. The data structure is used for communicating with the PP routines CIO and XOO and for maintaining the state of each plotter. Various fields in each type of data structure (PLOTTER TABLE, CONTROLLER TABLE, CIO FET, and XOO FET) contain pointers to another structure. Refer to Fig. 2 to see how the different data structures are linked together. PLOTTER TABLE The PLOTTER TABLE contains a sixteen word entry for each plotter connected to EPS. Refer to Fig. 3 for a schematic of the PLOTTER TABLE. The definition of each field in the.PLOTTER TABLE is: JSN Contains four characters that are either the JSN of the plot: file assigned to this plotter or the characters IDL or IDL*. The character string IDL denotes that this plotter does not have a plot file assigned to it. The character string IDL* denotes that this plotter has just finished plotting a file and is waiting for the XOD circular buffer to empty. STATE Contains an address of the current state routine in the module PLDTF (Plot File Executi ve) • RESOLUTION Contains the number of pixels per line. EST Contains the Equipment Status Table ordinal. ID Contains the plotter ID. This field is used to select the proper plotter when a file is routed with ID=xx specified. E Set when the END plot command is entered. R Set when 'the REPLOT command is entered. ERR Contains the address of the error message to be plotted. QAC PEEK Words 4 through 15 contain the first 12 words returned by the QAC PEEK request. These words are filled by the module PPQ (Process Plot Queue) • XDO FET The communication with the PP routine XOD is performed by a FET and circular data buffer. Refer to Fig. 4 for a schematic of the XDO FET. The first five words of the XOD FET have the same format as a FET that - _._-----------------_.---------_._----- - - - - - is used with CIO. Words FET+5 through FET+17 have special meaning. definition and use of these words are: MNEMONIC DROP DEFINITION AND USE This field is used as the drop command for the PP routine XOO. XOO will continue to write data to the plotters until this field is non-zero. This field is only valid in the first FET of a controller chain. STATUS This field contains the status of the plotter. It~s written by XOO and used by the K-display routines and by PPQ. PPQ will not assign a plot file to a plotter that is either not ready or has low paper supplies. FIRST FET This field contains a pointer to the first FET in a controller chain. All the FETs associated with a common CIU are linked together. When XOO is called, only the address of the first FET in the chain is passed -to XOO. PLOTTER This field contains a pointer to the PLOTTER TABLE entry for this plotter. NEXT This field contains a pointer to the next FET in the chain. NEXT is initialized by PRESET and used by XOO. XO.RL The number of 60-bit words to transfer to the plotter for each plot raster line (record). XO.RL is initialized by PLOTF and used by PLTF. XO.HDR This is a five word entry that contains the control word and a fifteen 16-bit word header that is placed in the circular buffer at the beginning of each record. It is initialized by PLOTF and used by PLTF. XO.NWDS This is a working location used by the module PLTF. It is used to count the number of 60bit words that have been transferred to the plotter. It is reset at the beginning of each record. XD.STAT This field represents the PLTF for this plotter. A indicates that PLTF is at record. A non-zero value is processing a record. ------- state of the module zero value the start of a new indicates that PLTF - - - ._-------_... _.....__....._._._-_. __._.._.... _....._.-...--_._ __.._-_._-_.•__ .. .. .- _ .. The XO.SIZE This field contains the size of the circular buffer. Initialized by PRESET. XO.NREC This field counts the number of records processed. Updated by PLTF and not used by anybody. CIO FET The FET that is used to communicate with CIO ha~ three non-standard fields defined in FET+8 through FET+l0. The definition of these fields are: CIO.NWDS FET+9 Number of 60-bit words in the next pru. CIO.EOR FET+9 Non-zero if an EOR was read. CIO.SIZE FET+l0 Contains the size of the circular buffer. CONTROLLER TABLE The CONTROLLER TABLE contains a single word for each CIU connected to EPS. Refer to Fig. 3 for a schematic of the CONTROLLER TABLE. The definitions of the fields are: FIRST XOO FET This field contains the address of the first FET in the chain. All FETs that are associated with a common CIU are linked together. CS This field contains the channel number of this CIU. PRS -- PRESET The main program defines the data structures PLOTTER TABLE, XOO FETs, and CIO FETs with the macro PLOTTER. The main program also allocates space for the CONTROLLER TABLE. The main program, however, does not link the various data structures together, allocate space for circular buffers, or initialize the PLOTTER TABLE fields RESOLUTION, EST, and ID~ This is the function of PRS. PRS determines how to initialize the data structures by reading directives from the file PCFILE. PCFILE contains directives in the form of line images. Each directive defines one plotter. The format of the directives is: EQ=nnnn,type. nnnn The EST ordinal for the plotter. type Denotes the type of plotter. The legal values of "t}'pe can be 9324, 9336, or 9344. ll After PRS determines the type and EST ordinal, it calls the PP routine XIO to assign the file name PLOTTERn to the specified EST ordinal. XIO returns the EST word in FET+6. PRS uses the EST word to determine the channel for this plotter. The channel number is used to build the CONTROLLER TABLE and to link the XOO FETs of all plotters sharing a common controller (CIU). When PRS has processed all the directives on the PCFILE, the field length is increased and the circular buffers for CIO and XOO are allocated. SOFTWARE MODULES CONNECTIONS The CPU resident code consists of seven modules: 1) 2) 3) 4) 5) 6) 7) PLOTSS MAIN LOOP PPQ -- PROCESS PLOT QUEUE PLOTF -- PLOT FILE EXECUTIVE PLTF -- PLOT FILE DRIVER BANRGEN -- GENERATE BANNER PAGE KDISPLA -- K DISPLAY GENERATION KINPUT -- OPERATOR INPUT Refer to Fig. 5 for the direct connections between the main m"odules. MAIN LOOP The main loop of PLOTSS performs two types of tasks. 1) 2) Tasks that are performed each time through the main loop. Tasks that are performed periodically, approximately every two seconds. Each time through the main loop, PLoTSS: 1) 2) 3) Calls PLOTF for each plotter. Calls KINPUT to process operator commands. Conditionally calls PPQ (if PPQSW is non-zero). Approximately every two seconds, PLoTSS performs the following functions: 1) 2) ExamiDes each CIU defined by the CONTROLLER TABLE. If the CIU is idle, i.e., a copy of XOD is not currently assigned to it, a call to Xoo is made to update the status of' all the plotters connected to the CIU. Calls KDISPLA to update the information in the K-display buffers. PPQ -- PROCESS PLOT QUEUE PPQ uses QAC to search the plot queue for the plot file with the greatest priority. If a file is found that can be plotted, the file is - - - - _ ... _--_...... .._-_._._----_. , attached with a QAC GET request and assigned to the appropriate plotter. PPQ is designed to be reentered multiple times. Whenever PPQ calls QAC for either a PEEK or a GETi it returns to the main loop before the PEEK or GET request completes. This allows the main loop to service the circular buffers of any active plotters. The location PPQSW contains the address in PPQ where processing is to continue. The values that location PPQSW can contain and the associated processing functions are: negative This is the initial entry to PPQ. The PEEK request block is initialized and the initial call to QAC is executed. PPQONE Each file returned in the PEEK reply buffer is examined. The file(s) with the highest priority and a compatible plotter ID is assigned to an available plotter. The assignment is performed by moving the twelve words from the PEEK reply buffer into the last twelve words of the PLOTTER TABLE. The actual attaching of the plot file is done by the processing in the next phase. PPQTWO Each entr~ in the PLOTTER TABLE is examined. For each plotter that is idle (word 0 of the PLOTTER TABLE contains IIIDLII) and has a plot file assigned (word 4 of the PLOTTER TABLE contains an JSN) , QAC is called to attach the fi Ie. PPQTHREE This phase waits for the QAC GET request to complete. When the GET request is complete, the plotter status is changed to BEGIN PLOT. This is accomplished by setting word 0 of the PLOTTER TABLE to the plot file JSN and the address of P.BEGIN (an entry point in the module PLOTF). PLOTF -- PLOT FILE EXECUTIVE PLOTF is the PLOT FILE EXECUTIVE and its task is to manage the transfer of data from the disk resident plot file to the plotter. PLOTF is called from the MAIN LOOP for each plotter defined in the PLOTTER TABLE. With respect to PLOTF, each plotter can be in one of six states. Thestate of each plotter is defined by an address of the associated processing routine in PLOTF and is stored in the lower 18 bits of the first word in the PLOTTER TABLE. A brief description of each state is given below. For a more complete description, refer to the listing. SYMBOL P.IDLE P.BEGIN DESCRIPTION This state indicates that the plotter does not have a plot file assigned to it. When the plotter is in this state, PLOTF does nothing more than e}{ it. This state initializes the plot process. Some initialization commands are sent to the plotter via XOO along with the banner page. The first ---_.- ._-_.. _---_._. __. _ - - record of the plot file is read and the file checked for the proper format. P.PLOT When the plotter is in this state, plot data is being transferred from the disk resident plot file (via CIO) to the plotter (via XOO). PLOTF does not transfer the data, rather it calls the module PLTF to transfer the data. P.DONE When all the data has been transferred from the plot file to the plotter, this state is entered. This state plots the ending banner and sends commands to the plotter to position the paper so that the plot is exposed. P.FLUSH This state waits until the circular buffer for XOD is empty. P.END This state checks the repeat count of the plot file and either sets the state to P.BEGIN to repeat the plot or to P.IDLE if another copy is not required. PLTF -- PLOT FILE DRIVER PLTF is the routine that transfers data from the disk resident plot file to the Benson plotter. PLTF calls CIO to read the plot file and calls XOO to write the data to the plotter (via the CIU). PLTF is called from PLOTF and is passed the address of aCID FET and the address ofaXOO·FET. PLTF will transfer data from the CIO buffer to the XOO buffer until one of the following conditions is true: 1. END-OF-FILE on the plot file. 2. CIO buffer emtpy. 3. XOO buffer full. 4. Record limit reached. The record limit is currently set for 100 records. 5. An error condition is detected from XOD. PLTF is a finite state machine with only two states: State 0 Initialize to process a new record. State 1 -- Transfer data (in prus) from the CIO buffer to the XOD buffer. Refer to the comments in the listing for ~ complete description of the processing steps for each state. When PLTF is executing, certain registers are dedicated: AO: CID FET address XO: XOD FET address B2: Contains the number of 60-bit words remaining to be transferred to XOD. B5: The current value for the XDD circular buffer IN pointer. B6: The value of the XDD circular buffer LIMIT pointer. BANRGEN -- GENERATE BANNER PAGE ....... _........... _--_._._--- BANRGEN plotter words 4 routine is called from PLOTF to generate the character data for the banner page. BANRGEN generates the banner from the data in through 15 of the PLOTTER TABLE. These words are filled by the PPQ when the file is attached. K-DISPLAV ROUTINES The K-display module contains two routines. The routine KINPUT is called each pass through the main processing loop to process NOS operator commands. The routine KDISPLA is called approxiametly every two seconds to update the K-display buffers. VI. XOO -- PLOTTER PPDRIVER XOO is a pool PP program that transfers data from a Cyber resident circular buffer to a eIU resident buffer. XOO is a modified version the the PP program XIO. The differences between XOO and XIO are: 1. XOO performs only one type of function (WRITE DATA) while XIO performs both reads and writes as well as control functions. 2. XOO is called with a list of FETS. XID only operates on a single FET. 3. The main processing loop of XOD and XIO are completely different. Refer to Fig. xx for a flowchart of the processing loop of XOD. VII. Iesvs -- eIU PROGRAM ICSVS is the CIU resident program that contains the hardware device drivers. ICSVS contains three device drivers: 1. Ramtek 9400 color raster display. 2. Benson 93xx electrostatic plotter. 3. Benson 93xx electrostatic plotter with a ~ogic Sciences HSR-11 rasterizer. This device is currently not supported by EPS. The main function of the CIU resident program is to receive data from the Cyber, do any reformatting that may be necessary, and send the data to the appropriate device. Refer to the document PDP Executive and Device Software Specifications for a detailed description on the internal structure of ICSVS and the communication protocol between ICSVS and the Cyber (XIO and XDO). VIII. PLOT FILE FORMAT EPS accepts plot files in INTERSVS image format. INTERSVS image files are raster-formatted files with one raster per fixed length record. EPS requires that the pixel length be one bit per pixel. The first record of INTERSYS image files is an header record that describes the pixel length, record size, and contains other routine dependant data. Refer to appendix 1 for a schematic of the header record. IX. XOD/CIU PLOTTER RECORD FORMAT When EPS transfers plot data to the eIU resident plotter driver, it preceeds the plot data with a header of fifteen sixteen-bit words (four sixty-bit words). This header is used to communicate the type of datarecord to the plotter driver. Only the first three words of the header contain information. The format for the first three words is: . _...__ .. _--_ .. _ ... __ ._ ..- ._......... - - - command RASTER TEXT word-l 10 ea ) 12 eEJ) BEGIN PLOT 2 END PLOT 4 6 SLEW HSR RESET HSR DATA 14
Source Exif Data:File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.3 Linearized : No XMP Toolkit : Adobe XMP Core 4.2.1-c041 52.342996, 2008/05/07-21:37:19 Create Date : 2017:01:12 07:53:01-08:00 Modify Date : 2017:01:12 08:34:04-08:00 Metadata Date : 2017:01:12 08:34:04-08:00 Producer : Adobe Acrobat 9.0 Paper Capture Plug-in Format : application/pdf Document ID : uuid:447a2de0-9438-ff40-aca9-db06c4065d4d Instance ID : uuid:0cb762ba-657b-f345-af1a-39e7258fd6cf Page Layout : SinglePage Page Mode : UseNone Page Count : 1542EXIF Metadata provided by EXIF.tools