Guardian Programming Reference Summary for ptal and TAL

Transcription

1 Guardian Programming Reference Summary for ptal and TAL Abstract This summary provides a quick reference to information required for Guardian programming in ptal and TAL. Product Version G09 Supported Releases This manual supports G06.15 and all subsequent releases until otherwise indicated in a new edition. Part Number Published February 2002

2 Document History Part Number Product Version Published D20 September D30 March G06.03 December G06.06 August G09 February 2002 Ordering Information For manual ordering information: domestic U.S. customers, call ; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice. Please check with your authorized representative to make sure you have the most recent information. Export Statement Export of the information contained in this manual may require authorization from the U.S. Department of Commerce. Examples Examples and sample programs are for illustration only and may not be suited for your particular purpose. The inclusion of examples and sample programs in the documentation does not warrant, guarantee, or make any representations regarding the use or the results of the use of any examples or sample programs in any documentation. You should verify the applicability of any example or sample program before placing the software into productive use. U.S. Government Customers FOR U.S. GOVERNMENT CUSTOMERS REGARDING THIS DOCUMENTATION AND THE ASSOCIATED SOFTWARE: These notices shall be marked on any reproduction of this data, in whole or in part. NOTICE: Notwithstanding any other lease or license that may pertain to, or accompany the delivery of, this computer software, the rights of the Government regarding its use, reproduction and disclosure are as set forth in Section of the FARS Computer Software Restricted Rights clause. RESTRICTED RIGHTS NOTICE: Use, duplication, or disclosure by the Government is subject to the restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS RESTRICTED RIGHTS LEGEND: Use, duplication or disclosure by the Government is subject to restrictions as set forth in paragraph (b)(3)(b) of the rights in Technical Data and Computer Software clause in DAR (a). This computer software is submitted with restricted rights. Use, duplication or disclosure is subject to the restrictions as set forth in NASA FAR SUP (April 1985) Commercial Computer Software Restricted Rights (April 1985). If the contract contains the Clause at Rights in Data General then the Alternate III clause applies. U.S. Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract. Unpublished All rights reserved under the Copyright Laws of the United States.

3 Guardian Programming Reference Summary for ptal and TAL Tables What s New in This Manual iii Manual Information iii New and Changed Information iv About This Manual v Your Comments Invited v Notation Conventions v Compaq Computer Corporation i

4 Contents 1. Process Name and ID Formats 1. Process Name and ID Formats 2. File Codes 3. Device Types and Subtypes 4. Procedure Calls Summary (A-C) 5. Procedure Calls Summary (D-F) 6. Procedure Calls Summary (G-N) 7. Procedure Calls Summary (O-Q) 8. Procedure Calls Summary (R-Z) 9. CONTROL Operations 10. SET^FILE Operations 11. SETMODE Operations 12. Completion Codes 13. Traps 14. Interprocess Messages 15. Error Codes 16. ASCII Character Set 17. TNS Instruction Set Tables TNS Alphabetical List of Instructions 17-1 Table 3-1. Device Types and Subtypes (page 1 of 14) 3-1 Table 9-1. CONTROL Operation Table 9-2. CONTROL Operations Table SET^FILE Operations That Set Values 10-1 Table SET^FILE Operations That Set Addresses 10-8 ii

5 What s New in This Manual Manual Information Guardian Programming Reference Summary for ptal and TAL Abstract This summary provides a quick reference to information required for Guardian programming in ptal and TAL. Product Version G09 Supported Releases This manual supports G06.15 and all subsequent releases until otherwise indicated in a new edition. Part Number Published February 2002 Document History Part Number Product Version Published D20 September D30 March G06.03 December G06.06 August G09 February 2002 iii

6 What s New in This Manual New and Changed Information New and Changed Information This revision of the Guardian Programming Reference Summary for ptal and TAL includes the following changes: An entry has been added to Section 4, Procedure Calls Summary (A-C), for the CPU_GETINFOLIST procedure that directs users to the PROCESSOR_GETINFOLIST_ documentation. The unsupported proc call GETSYSTEMSERIALNUMBER has been removed from Section 6, Procedure Calls Summary (G-N). Table 3-1, Device Types and Subtypes, on page 3-1, has been updated to include an entry for the 4619 disk drive. iv

7 About This Manual Your Comments Invited After using this manual, please take a moment to send us your comments. You can do this by returning a Reader Comment Card or by sending an Internet mail message. A Reader Comment Card is located at the back of printed manuals and as a separate file on the Tandem User Documentation disc. You can either fax or mail the card to us. The fax number and mailing address are provided on the card. Also provided on the Reader Comment Card is an Internet mail address. When you send an Internet mail message to us, we immediately acknowledge receipt of your message. A detailed response to your message is sent as soon as possible. Be sure to include your name, company name, address, and phone number in your message. If your comments are specific to a particular manual, also include the part number and title of the manual. Many of the improvements you see in Tandem manuals are a result of suggestions from our customers. Please take this opportunity to help us improve future manuals. Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: LIGHTS [ ON ] [ OFF ] [ SMOOTH [ num ] ] K [ X D ] address-1 v

8 About This Manual General Syntax Notation { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON OFF } Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF ON SAVEABEND } Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [, new-value ]... [ - ] { }... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation. Parentheses, commas, semicolons, and other symbols not previously described must be entered as shown. For example: error := NEXTFILENAME ( file-name ) ; LISTOPENS SU $process-name.#su-name Quotation marks around a symbol such as a bracket or brace indicate that the symbol is a required character that you must enter as shown. For example: "[" repetition-constant-list "]" Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In the following example, there are no spaces permitted between the period and any other items: $process-name.#su-name Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] CONTROLLER [, attribute-spec ]... vi

9 About This Manual Notation for Messages!i and!o. In procedure calls, the!i notation follows an parameter (one that passes data to the called procedure); the!o notation follows an parameter (one that returns data to the calling program). For example: CALL CHECKRESIZESEGMENT ( segment-id!i, error ) ;!o!i,o. In procedure calls, the!i,o notation follows an / parameter (one that both passes data to the called procedure and returns data to the calling program). For example: error := COMPRESSEDIT ( filenum ) ;!i,o!i:i. In procedure calls, the!i:i notation follows an string parameter that has a corresponding parameter specifying the length of the string in bytes. For example: error := FILENAME_COMPARE_ ( filename1:length!i:i, filename2:length ) ;!i:i!o:i. In procedure calls, the!o:i notation follows an buffer parameter that has a corresponding parameter specifying the maximum length of the buffer in bytes. For example: error := FILE_GETINFO_ ( filenum!i, [ filename:maxlen ] ) ;!o:i Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Bold Text. Bold text in an example indicates user entered at the terminal. For example: ENTER RUN CODE?123 CODE RECEIVED: The user must press the Return key after typing the. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name vii

10 About This Manual Notation for Management Programming Interfaces [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For example: Event number = number [ Subject = first-subject-value ] A group of items enclosed in brackets is a list of all possible items that can be displayed, of which one or none might actually be displayed. The items in the list might be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: LDEV ldev [ CU %ccu CU %... ] UP [ (cpu,chan,%ctlr,%unit) ] { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list might be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LBU { X Y } POWER FAIL process-name State changed from old-objstate to objstate { Operator Request. } { Unknown. } Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: Transfer status: { OK Failed } % Percent Sign. A percent sign precedes a number that is not in decimal notation. The % notation precedes an octal number. The %B notation precedes a binary number. The %H notation precedes a hexadecimal number. For example: % P=%p-register E=%e-register Notation for Management Programming Interfaces The following list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual. UPPERCASE LETTERS. Uppercase letters indicate names from definition files; enter these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type!r. The!r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING.!r viii

11 About This Manual Change Bar Notation!o. The!o notation following a token or field name indicates that the token or field is optional. For example: ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32.!o Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE). The CRE has many new message types and some new message type codes for old message types. In the CRE, the message type SYSTEM includes all messages except LOGICAL-CLOSE and LOGICAL-OPEN. ix

12 About This Manual Change Bar Notation x

13 1 Process Name and ID Formats D-Series Process File Name Formats The syntax for a process file name that identifies an unnamed process is: [node]$:cpu:pin:seq-no The syntax for a process file name that identifies a named process is: [node]process-name[:seq-no][.qual-l[.qual-2]] node specifies the name of the node on which the process is running. A node name consists of a backslash (\) followed by as many as seven alphanumeric characters; the first alphanumeric character must be a letter. cpu pin specifies the number of the processor in which the process is running. The value of cpu is one or two digits representing a value in the range 0 through 15. specifies the PIN (process identification number) of the process. The value of pin is from one through five digits representing a value in the range 0 through the maximum value allowed for the processor. seq-no specifies the system-assigned sequence number of the process. The parameter seq-no has a maximum of 13 digits. Any leading zeroes are suppressed. process-name specifies the name of the process. A process name consists of a dollar sign ($) followed by as many as five alphanumeric characters; the first alphanumeric character must be a letter. qual-1 and qual-2 are optional qualifiers. The first qualifier consists of a pound sign (#) followed by as many as seven alphanumeric characters; the first alphanumeric character must be a letter. The second qualifier contains from one through eight alphanumeric characters; the first character must be a letter. 1-1

14 Process Name and ID Formats Process Descriptors A process descriptor is a form of process file name that always includes the node and seq-no sections of the name; when identifying a named process, it never includes the optional qualifiers qual-1 or qual-2. Operating system procedures always use the external file-name notation when returning a process descriptor. Process Handles A process handle is a 10-word structure that identifies a single named or unnamed process. 1-2

15 2 File Codes For additional information about file codes, refer to the Guardian Procedure Errors and Messages Manual.. File Code Description 100 TNS object file 101 EDIT-format file 110 EDIT VS recovery file 111 EDIT VS stack dump file (data area image) 115 TEDIT TEDPROFL file Spooler control files 129 Spooler job file 130 Inspect save file 134 TMF audit-trail file 170 XRAYSCAN structured files for Enform reports 175 Measure data file 176 NonStop SQL Table file for Surveyor 180 C data file 223 Enable log file Ada data file 250 Transfer profile file 251 Transfer session file 252 Transfer item descriptor file 253 Transfer recipient file 254 Transfer folder file 255 Transfer item data file 256 Transfer distribution list file 257 Transfer ready file 258 Transfer time file 259 Transfer network file 260 Transfer inverted folder file 261 Transfer restart file 262 Transfer name file 263 Transfer DIN file 2-1

16 File Codes File Code Description 264 Transfer alias file 265 Transfer trace file 266 Transfer queue file 267 Transfer inverted attachment file 268 Transfer external objects file 275 Transfer WORDLINK and Translator format name file 276 Transfer WORDLINK and Translator character map file 277 Transfer WORDLINK and Translator batch gateway configuration file 278 Transfer WORDLINK and Translator format type file 280 Transfer WORDLINK and Translator text server text file 281 Transfer System Management Monitor database monitor sample file 282 Transfer System Management Monitor queue monitor sample file Transfer files 300 TPS (Pathway) TCL program directory file 301 TPS (Pathway) TCL program code file 302 TPS (Pathway) SCREEN COBOL symbol file TPS (Pathway) files 305 TPS (Pathway) TCP data area swap file 306 TPS (Pathway) AM control file 307 TPS (Pathway) Path TCP dump file 308 TPS (Pathway) Pathway trace file 309 TPS (Pathway) PATHMON stack dump file TPS (Pathway) files 400 Tape simulator control file 401 Tape simulator data file 410 EXERCISE message file 411 EXERCISE error information file EXERCISE files 430 EXERCISE Tandump segmented save file 440 TACL saved variable segment file 450 C00 file server and ViewPoint status display configuration file 451 Event display configuration file 500 NonStop II processor microcode file 502 NonStop II microcode file for SHADOW 2-2

17 File Codes File Code Description Tri-Density tape drive microcode object file 510 Standard (unformatted) microcode file 520 NonStop TXP processor microcode file 521 GASM-format microcode object file 525 NonStop VLX processor microcode file Safeguard files NonStop SQL files 600 MUMPS global file 601 MUMPS routine file 602 MUMPS global directory file MUMPS files 660 Encore capture file Encore files 700 Native object file Comm trace files Comm configuration files Comm configuration database files 840 SNAX utility file 841 COUP database file 842 COUP process image file 843 EMS logger file 844 EMS formatter template 845 EMS compiled filter 846 Cover files NetBatch files 849 DNS configuration file 850 DNS database file 851 SNAX5 configuration file 852 NonStop CLX shutdown file Optical disk files 855 FUP restart file 888 Enform compiled query file 904 Exchange trace file 2-3

18 File Codes 2-4

19 3 Device Types and Subtypes Table 3-1. Device Types and Subtypes (page 1 of 14) Type Device Sub type D-Series Description G-Series Description 0 Process 0 Default subtype for general use 1-49 Reserved for definition by Tandem. The following subtypes are defined: 1 = CMI process 2 = Security monitor process 30 = Device simulation process 31 = Spooler collector process 1 Operator console For general use 0 $0 (operator process) or alternate collector 1 $0.#ZSPI ($0 opened to receive SPI commands) 2 $Z0 (compatibility distributor) 2 $RECEIVE 0 3 Disk (160 MB formatted capacity) (240 MB formatted capacity) or 4106 (64 MB formatted capacity) (moving-head part, 64 MB formatted capacity) (540 MB formatted capacity) Default subtype for general use Reserved for definition by Tandem. The following subtypes are defined: 1 = CMI process 2 = Security monitor process 30 = WANBOOT process 31 = Spooler collector process 48 = TFTP server process 49 = SNMP trap multiplexor For general use $0 (operator process) or alternate collector $0.#ZSPI ($0 opened to receive SPI commands) $Z0 (compatibility distributor) N.A. N.A. N.A. N.A. N.A. 3-1

20 Device Types and Subtypes Table 3-1. Device Types and Subtypes (page 2 of 14) Sub Type Device type D-Series Description G-Series Description 3 Disk (fixed-head part, 1.45 N.A. MB formatted capacity) , 4111 (128 MB N.A. formatted capacity) 4120 (V8) (128 MB N.A. formatted capacity) or 4115 (264 MB N.A. formatted capacity) (XL8) (415 MB N.A. formatted capacity) (V80) (265 MB formatted capacity) with 3125 controller N.A (145 MB formatted capacity) (XL80) (895 MB formatted capacity) with 3129 controller (300 MB formatted capacity) with 3681 MFC (8 GB) with 3129 controller (648 MB formatted capacity) with 3681 MFC (1038 MB formatted capacity per spindle) with 3128 controller (1038 MB formatted capacity) with 3681 MFC (160 MB formatted capacity) (2 GB formatted capacity) with 3681 MFC (2 GB formatted capacity per spindle) with 3128 controller N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. N.A. 3-2

21 Device Types and Subtypes Table 3-1. Device Types and Subtypes (page 3 of 14) Type Device 3 Disk (1038 MB formatted capacity) with 3681 MFC (2 GB formatted capacity) with 3681 MFC 36 NonStop Storage Management Foundation (SMF) virtual disk process (2 GB formatted capaity per spindle) with 3129 controller 4 Magnetic tape unit Sub type D-Series Description G-Series Description N.A. N.A (2 GB formatted capacity per spindle) with ServerNet/DA (4 GB) 4570 (4 GB) with ServerNet/DA 41 N.A (4 GB) 42 N.A (8 GB) 4609 (8 GB) 43 N.A (18 GB) 43 N.A (18 GB) (15,000 rpm) 44 N.A (36 GB) 4590 (18 GB) with ServerNet/DA (18 GB) 4590 (18 GB) with ServerNet/DA Optical Disk Subsystem (1.3 GB per volume) with 3128 controller N.A , 5103, 5104, 5110, 5114 (9-track, 45/125 ips) tape units with 3202 controller (7-track, 45 ips) tape unit with 3203 controller (tri density) master tape unit or 5107 slave unit with 3206 controller N.A. N.A. N.A. 3-3

22 Device Types and Subtypes Table 3-1. Device Types and Subtypes (page 4 of 14) Type Device 4 Magnetic tape unit Sub type D-Series Description G-Series Description , 5103, 5104, 5110, 5114 (9-track, 45/125 ips) tape units with 3207 controllers N.A (9-track, 200 ips) master tape unit or 5131 slave unit with 3208 controller cartridge tape unit with 3209 or 3681 controller in 3681 MFC tape unit (1600 bits per inch, or bpi) or 5170 tape unit (1600, 6250 bpi) with 3214 controller or 3681 MFC or PMF/IOMF master tape unit (9-track, 200 ips) or 5131 slave unit with 3211 controller tape unit (18 track, bpi) with 3215 controller tape unit (18 track, bpi) with 3216 controller or 3681 MFC and 5194 tape unit (36 tracks, bpi) tape unit (38000 bpi) with 3217 controller N.A. N.A tape unit (1600, 6250 bpi) PMF/IOMF or ServerNet/DA N.A. N.A tape unit (18 track, bpi) or 5194 tape unit (36 tracks, bpi) with PMF, IOMF, or ServerNet/DA N.A DAT with PMF or IOMF 5 Printer 0 SNAX PRT protocol , 5503, 5504, 5510, 5513, and 5514 (parallel printers) or 5518 parallel printer (for 7-bit data transfer) with 3601 UI N.A (serial printer) 3-4

23 Device Types and Subtypes Table 3-1. Device Types and Subtypes (page 5 of 14) Sub Type Device type D-Series Description G-Series Description (serial printer) 5 Printer , 5513, 5514 (alternate character set) for parallel (band) printers or 5518 parallel printer (for 8-bit data transfer) with 3601 UI N.A (letter-quality serial printer) , 5516 dot matrix (parallel and serial printers) 5518 dot matrix (parallel printer) or 5574 laser (serial printer) dot matrix (serial printer) laser (serial printer) 32 ASYNC_PRT Device. Nonstandard serial printers (DTR printer and 554x printers) 6 Terminal 0 Conversational mode (P/N 6401/6402) or ASYNC_TERM device Conversational mode (P/N 6401/6402) or PATP- TERM (non-tandem) device 1 Page mode (P/N 6511, 6512) Page mode (P/N 6511, 6512) 2 Page mode (P/N 6520, 6524) Page mode (P/N 6520, 6524) 3 Page mode (P/N 6520 remote) ITI protocol for use by AM6520 N.A. 4 Page mode (P/N 6526, 6528, 653x) 5 Page mode (P/N 6530 remote) ITI protocol for use by AM6520 Page mode (P/N 6526, 6528, 653x) N.A Conversational mode Conversational mode 3-5

24 Device Types and Subtypes Table 3-1. Device Types and Subtypes (page 6 of 14) Sub Type Device type D-Series Description G-Series Description 6 = 3277 (screen size 12x40) 6 = 3277 (screen size 12x40) 6 Terminal 7 = 3277 (screen size 24x80) 7 = 3277 (screen size 24x80) 8 = 3277 (screen size 32x80) 8 = 3277 (screen size 32x80) 9 = 3277 (screen size 43x80) 9 = 3277 (screen size 43x80) SNAX Interactive Terminal Interface (ITI) Protocol 10 = 3277 (screen size 12x80) 10 = 3277 (screen size 12x80) FaxLink 6340 FaxLink 16 Nonstandard device with 3606 controller, for read-continuous/type-ahead capability , & -11, , , & -12, , , 3178-C10, -C20, -C3, & - C4, 3191-A1K & -A2K, A, -2B, -S2A, -S2B, & -02X, , -002, F-6652-A, & -C , , , A, -3B, -S3G, & -03X & -14, , , 6580-A04, -A06, - A08, & -A , 3284, 3286, 3282, , & -11, , , & -12, , , 3178-C10, -C20, -C3, & - C4, 3191-A1K & -A2K, A, -2B, -S2A, - S2B, & -02X, , -002, F A, & -C , , , A, -3B, -S3G, & - 03X & -14, , , 6580-A04, -A06, -A08, & -A , 3284, 3286, 3282, Hard-copy console 6603/6604 terminal 3-6

25 Device Types and Subtypes Table 3-1. Device Types and Subtypes (page 7 of 14) Type Device 7 Envoy data communications line Sub type D-Series Description G-Series Description 0 BISYNC, point-to-point, nonswitched 1 BISYNC, point-to-point, switched 2 BISYNC, multipoint, tributary 3 BISYNC, multipoint, supervisor 8 ADM-2, multipoint, supervisor 9 TINET, multipoint, supervisor 10 Burroughs, multipoint, supervisor 11 Burroughs, point-to-point, contention 13 Burroughs, point-to-point, contention BISYNC, point-to-point, nonswitched BISYNC, point-to-point, switched BISYNC, multipoint, tributary BISYNC, multipoint, supervisor ADM-2, multipoint, supervisor TINET, multipoint, supervisor Burroughs, multipoint, supervisor Burroughs, point-to-point, contention Burroughs, point-to-point, contention 30 Full duplex (FDX), out line Full duplex (FDX), out line 31 Full duplex (FDX), in line Full duplex (FDX), in line 32 NASDAQ, Full duplex (FDX), out line 33 NASDAQ, Full duplex (FDX), in line NASDAQ, Full duplex (FDX), out line NASDAQ, Full duplex (FDX), in line 40 Asynchronous line supervisor 50 Isochronous line N.A. 56 Automatic calling unit (ACU) N.A. 8 Open SCSI N.A. 9 Process-to-process interface 0 X25AM process 3-7

26 Device Types and Subtypes Table 3-1. Device Types and Subtypes (page 8 of 14) Type Device 10 Terminal SNAX Cathode-Ray Tube (CRT) protocol 0 327x CRT mode Interface 327x CRT mode Interface , & -11, , , & -12, , , 3178-C10, -C20, -C3, & - C4, A, -2B, -S2A, -S2B, & -02X , , , A, -3B, -S3G, & -03X & -14, , , 6580-A04, -A06, - A08, & -A , & -11, , , & -12, , , 3178-C10, -C20, -C3, & - C4, A, -2B, -S2A, - S2B, & -02X , , , A, -3B, -S3G, & - 03X & -14, , , 6580-A04, -A06, -A08, & -A , , , , , 3284, 3286, 3287, , 3284, 3286, 3287, EnvoyACP/XF 40 FRMEXF or SDLCXF (synchronous data-link control) line 41 HDLCXF (high-level data-link control) line 42 ADCCP (advanced data communications control procedures) line 43 Frame protocol 12 Tandem-to-IBM Link (TIL) 0 13 SNAX/XF or SNAX/APN Sub type D-Series Description G-Series Description 5 SNASVM (Service Manager Process) 14 SNALU 0 SNA Application Logical Unit (SNALU) 15 SNAX/ Data Encryption Devices 3501 Data Encryption Devices 3-8

27 Device Types and Subtypes Table 3-1. Device Types and Subtypes (page 9 of 14) Sub Type Device type D-Series Description G-Series Description 15 SNAX/ Key manager (ZKEY) Key manager (ZKEY) 3 High performance security modules NSP 4 Atalla A6000 Network Security Processor with 3605 controller High performance security modules Atalla A6000 Network Security Processor 19 IPX/SPX 0 Manager process Manager process 1 Protocol process Protocol process NTM/MP 0 NonStop Transaction Manager/MP NonStop Transaction Manager/MP 24 OSS Open System Services Open System Services 25 SMF pool 0 N.A. Storage pool process 26 Tandem Hyper- Link (THL) 0 27 IPBMON 0 Interprocessor bus monitor for Fiber Optic Extension (FOX) or TorusNet vertical subsystem in FOX-compatibility mode 5 $IPB1 (TorusNet vertical subsystem master service manager in multiple-link mode) 6 Service manager for additional TorusNet vertical links Interprocessor bus monitor for Fiber Optic Extension (FOX) or TorusNet vertical subsystem in FOX-compatibility mode $IPB1 (TorusNet vertical subsystem master service manager in multiple-link mode) Service manager for additional TorusNet vertical links 28 $ZNUP 0 Network Utility Process 29 $ZMIOP 1 Subsystem manager 30 Optical disk unit Optical Storage Facility (OSF) disk drive with 3128 controller N.A optical disk subsystem with 3219 controller optical disk subsystem with 3220 controller N.A. N.A. 3-9

28 Device Types and Subtypes Table 3-1. Device Types and Subtypes (page 10 of 14) Sub Type Device type D-Series Description G-Series Description 30 Optical disk unit optical disk subsystem N.A. with 3220 controller 31 SNMP 0 NonStop SNMP Agent NonStop SNMP Agent 36 TandemTalk 1 AppleTalk Transaction N.A. Protocol (ATP) 2 AppleTalk Data Stream N.A. Protocol (ADSP) 3 AppleTalk Session Protocol N.A. (ASP) 4 AppleTalk Printer Access Protocol (PAP) N.A. 37 ISDN 0 Integrated Services Digital Network Subsystem Manager Integrated Services Digital Network Subsystem Manager 43 SLSA 0 N.A. ServerNet LAN Systems Access (SLSA) manager process (LAN MAN) 1 N.A. ServerNet LAN Systems Access (SLSA) monitor process (LAN MON) 44 any device type > is displayed as the type for any device with a device type greater than 63. The program is unable to return information on device types greater than 63. Use the newer Guardian procedures (those that are not superseded) to obtain information on device types that are greater than is displayed as the type for any device with a device type greater than 63. The program is unable to return information on device types greater than 63. Use the newer Guardian procedures (those that are not superseded) to obtain information on device types that are greater than QIO 0 Queued I/O Monitor Process Queue I/O Monitor Process 46 TELNET 0 TELNET Server Process TELNET Server Process 48 TCP/IP 0 49 SNAX/CDF 0 N.A. 3-10

29 Device Types and Subtypes Table 3-1. Device Types and Subtypes (page 11 of 14) Sub Type Device type D-Series Description G-Series Description 50 CSM 0 Communications Subsystem Manager with 3650, 6100, or 6110 controller N.A. 1 Single-board (SBSCSM) N.A. with 3605 or 3606 controller 2 N.A. SWAN Concentrator Manager(CONMGR) 3 N.A. $ZZWAN WAN manager process 63 Subsystem Control Point (SCP) Subsystem Control Point (SCP) 51 CP Line interface unit (LIU) Line interface unit (LIU) 1 Bisynchronous (BISYNC) point-to-point line 3-11 Bisynchronous (BISYNC) point-to-point line 2 ADCCP line ADCCP line 3 TINET line N.A. 4 MPSB Burroughs multipoint MPSB Burroughs multipoint 52 SMF master 0 N.A. SMF master process 53 ATP ASYNCTERMPROC: Terminals or serial printers attached to 3605, 6105, or 6110 controller (LIU-1) 1 ASYNCTERMPROC: Terminals or serial printers attached to 3606, 6105, or 6110 controller (LIU-4) 2 ASYNCPROC: ATP6100 lines on the 3681 multifunction controller 54 DDNAM 0 Non-3650 or non or Open Systems Interconnection (OSI) 1 N.A. OSI/Application Services (OSI/AS) Manager 4 N.A. Transport service provider (TSP)

30 Device Types and Subtypes Table 3-1. Device Types and Subtypes (page 12 of 14) Type Device 55 Open Systems Interconnection (OSI) 5 N.A. Tandem application, presentation, and session (TAPS) processes 11 N.A. OSI/Message Handling System (OSI/MHS) 12 N.A. OSI/Message Handling System (OSI/MHS) 20 N.A. OSI/FTAM Application Manager 21 N.A. OSI/FTAM Services 24 N.A. OSI/CMIP 25 N.A. OSI/FTAM Services 56 Multilan 0 MLAM line attached to the 3613, 3615, or 3616 TLAM controller N.A. 1 Network-basic - N.A. system (NETBIOS) 2 Dynamic Configuration N.A. Management 3 Controller Debug N.A. 4 SAP NAM (Expand) N.A. 5 Ethernet N.A. 6 Logical link control (LLC) N.A. type 1 57 GDS 0 General Device Support General Device Support 58 SNAX/XF or SNAX/APN Sub type D-Series Description G-Series Description 0 SDLC (6203 or 6204) line with 3604 controller 1 Line to 3605, 6100, or 6110 controller 2 Line attached to 3840, or 3841 SNAXLink controller (SNAX/XF only) 3 SNAX/XF Over X.25 (SOX) 4 Support for TLAM token-ring lines N.A. 3-12

31 Device Types and Subtypes Table 3-1. Device Types and Subtypes (page 13 of 14) Type Device 59 AM Line attached to a byte-synchronous controller 10 Line attached to 3605, 6100 CSS, or 6105 or 6110 CC 60 AM Line attached to a bytesynchronous controller 10 Line attached to 3605, 6100 CSS, or 6105 or 6110 CC TR Line attached to a bytesynchronous controller 11 Line attached to 3605, 6100 CSS, or 6105 or 6110 CC 61 X Line attached to a 3604 controller 62 Line attached to a 3681 multifunction controller 63 Line attached to 3605, 6110 controller, or 6100 CSS N.A. N.A. Line attached to SWAN concentrator Line attached to SWAN concentrator N.A. N.A. Line attached to SWAN concentrator 62 Expand NCP 0 $NCP Network Control Process 63 Expand Line Handler Sub type D-Series Description G-Series Description 0 NETNAM single-line handler attached to a non-3605 controller 1 NETDIRECT multiline line handler 2 Multiline line handler attached to a non-3605 controller 3 NETCLUSTER FOX line handler 5 NETDIRECT single-line handler attached to 3605, 6100, 6110 CSS, or 6105 CC 6 Multiline line handler attached to 3605, 6100, 6110 CSS, or 6105 CC NETNAM single-line handler attached to a non-3605 controller NETDIRECT multiline line handler Multiline line handler attached to a non-3605 controller NETCLUSTER FOX line handler NETDIRECT single-line handler attached to 3605, 6100, 6110 CSS, or 6105 CC Multiline line handler attached to 3605, 6100, 6110 CSS, or 6105 CC 3-13

32 Device Types and Subtypes Table 3-1. Device Types and Subtypes (page 14 of 14) Type Device 65 Storage Subsystem Manager 66 NonStop Kernel Management 67 SCSI Lock Management Sub type D-Series Description G-Series Description 0 N.A. responsible for the configuration and control of storage I/O processes 0 N.A. responsible for the configuration and control of system-wide attributes and generic processes 0 N.A. responsible for coordinating resource sharing SCSI I/O subsystem components across processors 3-14

33 4 Procedure Calls Summary (A-C) This section lists procedure calls in alphabetic order and briefly describes the syntax of each. For additional information about the procedure calls, refer to the Guardian Procedure Calls Reference Manual. ABEND (Superseded by PROCESS_STOP_) Deletes a process or a process pair. CALL ABEND ( [ process-id ],[ stop-backup ],[ error ],[ compl-code ],[ termination-info ],[ spi-ssid ],[ length ],[ text ] ); process-id, INT:ref:4 stop-backup, INT:value error, INT:ref:1 compl-code, INT:value termination-info, INT:value spi-ssid, INT.EXT:ref:6 length, INT:value text, STRING.EXT:ref:length < (CCL) The process-id parameter is invalid, or an error occurred while ABEND was terminating the process. = (CCE) ABEND was successful. ACTIVATEPROCESS (Superseded by PROCESS_ACTIVATE_) Returns a process or process pair from the suspended state to the ready state. CALL ACTIVATEPROCESS ( process-id ); 4-1

34 Procedure Calls Summary (A-C) process-id, INT:ref:4 < (CCL) ACTIVATEPROCESS failed, or no process is designated process-id. = (CCE) The process is activated. ADDDSTTRANSITION (Superseded by DST_TRANSITION_ADD_) Allows a super-group user (255, n) to add an entry to the daylight-saving time (DST) transition table. CALL ADDDSTTRANSITION ( low-gmt,high-gmt,offset ); low-gmt, FIXED high-gmt, FIXED:value offset, INT:value < (CCL) You are not the super ID (255,255), you loaded the DST table inconsistently (the DST table contains gaps or an overlap of entries), or you were loading the DST table at the same time someone else was loading the DST table. = (CCE) The DST table was loaded successfully. ADDRESS_DELIMIT_ Obtains the addresses of the first and last bytes of a particular area of the caller s logical address space. It can also obtain a set of flags that describe the area and the logical segment ID of the area. error := ADDRESS_DELIMIT_ ( address,[ low-address ],[ high-address ],[ address-descriptor ],[ segment-id ],[ error-detail ] ); 4-2

35 Procedure Calls Summary (A-C) error, INT 0 No error; the requested values are returned. 2 Parameter error; the address parameter was missing. 3 Bounds error; error-detail contains the number of the first parameter found to be in error, where 1 designates the first parameter on the left. This error is returned only to nonprivileged callers. 4 address is not mapped. 5 address.<0> = 1, address is an invalid address. address.<0> <> 1, address is within relative segment 1, 2, or 3.! address, INT(32):value low-address, INT(32):value high-address, INT(32):value address-descriptor, INT.EXT:ref:1 <0:6> Bits are reserved; 0 is returned. <7> A flat, unaliased segment. An unaliased segment does not have a corresponding absolute segment address. <8> A flat, aliased segment. An aliased segment has a corresponding absolute segment address. <9> The currently addressable extended data segment. <10> Accessible only by privileged processes. <11> Shared by another process. <12> Cannot be deallocated. <13> Writeback-inhibited. <14> Extensible. <15> Resident. segment-id, INT.EXT:ref:1-110 Last valid extended data segment ID Accelerator-generated code segment Accelerator read-only data segment for user code segment Accelerator-generated user library segment Accelerator read-only data segment for library code segment. 4-3

36 Procedure Calls Summary (A-C) -105 TNS user code segment TNS user library segment TNS user data segment Main RISC stack segment Debug stack segment Priv RISC stack segment. -99 System data segment. -98 System code segment. -97 System code segment. -96 System code segment. -95 System code segment. -94 System code segment. error-detail, INT.EXT:ref:1 ADDRTOPROCNAME Accepts a P register value and stack marker ENV value and returns the associated symbolic procedure name and various optional items that describe the procedure in detail. error := ADDRTOPROCNAME ( p-reg,stack-env,proc-name,proc-name-size,proc-name-length,[ base ],[ size ],[ entry ],[ attributes ],[ pin ] ); error, INT 0 Successful call; the procedure name is deposited into proc-name for procname-length bytes. 11 A procedure name was not found. 22 One of the parameters specifies an address that is out of bounds. 23 The p-reg, stack-env, and pin parameters do not indicate a legal code location. 4-4

37 Procedure Calls Summary (A-C) 24 The pin parameter was supplied and the caller is not privileged. 29 A required parameter was not supplied. 122 The supplied value of proc-name-size is less than the length of the procedure name that is to be returned into proc-name. p-reg, INT:value stack-env, INT:value <4> Library bit <7> System code bit <11:15> Space ID bits proc-name, STRING.EXT:ref proc-name-size, INT:value proc-name-length, INT.EXT:ref:1 base, INT.EXT:ref:1 size, INT.EXT:ref:1 entry, INT.EXT:ref:1 attributes, INT.EXT:ref:1 <0> Priv bit <1> Callable bit <2> Resident bit <3> Interrupt bit <4> Entry point bit <5> Variable bit <6> Extensible bit <7:15> PEP number pin, INT:value = (CCE) The symbolic procedure name was found; error contains 0. > (CCG) An error occurred; error contains the error value. 4-5

38 Procedure Calls Summary (A-C) ALLOCATESEGMENT (Superseded by SEGMENT_ALLOCATE_) Allocates a selectable extended data segment for use by the calling process. It can also be used to share selectable extended data segments or flat extended data segments allocated by other processes. status := ALLOCATESEGMENT ( segment-id,[ segment-size ],[ filename ],[ pin-and-flags ] ); status, INT 0 No error File-system error related to the creation or open of the swap file. -1 Illegal segment-id. -2 Illegal segment-size. -3 Bounds violation on file-name. -4 Illegal combination of options. -5 Unable to allocate segment space. -6 Unable to allocate segment page table space. -7 Security violation on attempt to share segment. -8 The pin does not exist. -9 The does not have the segment allocated. -10 Trying to share segment with self. -11 Requested segment is currently being resized or is incompatible. segment-id, INT:value segment-size, INT(32):value filename, INT:ref:12 pin-and-flags, INT:value, <8:15> Optional PIN for segment sharing. <5:7> Not used; must be zero (0). <4> Allocate an extensible segment. <3> Allocate a segment sharable by the file-name method. 4-6

39 Procedure Calls Summary (A-C) <2> Allocate a writeback-inhibit segment. <1> If 1, bits <8:15> are ignored. <1> If 0, allocate a segment sharable by the PIN method. ALTER (Superseded by FILE_ALTERLIST_) Changes disk file characteristics that cannot ordinarily be changed while the file is open. This procedure operates only on Guardian objects. CALL ALTER ( filename,function,newvalue,[ partonly ] ); filename, INT:ref:12 function, INT:value 1 Change file code. 2 Change the TMF audited characteristic of the file. 3 Change the refresh flag. 4 Oddunstr:allow odd byte positioning and transfers. 5 Change the alternate key description. This function is not supported for format 2 files. 6 Change the partitioning description. This function is not supported for format 2 files. 7 Resets the broken flag. 8 Change the expiration date. newvalue, INT:ref:* partonly, INT:value < (CCL) An error occurred (call FILEINFO). = (CCE) The call to ALTER was successful. > (CCG) An error occurred (call FILEINFO). 4-7

40 Procedure Calls Summary (A-C) ALTERPRIORITY (Superseded by PROCESS_SETINFO_) Is used to change the execution priority of a process or process pair. CALL ALTERPRIORITY ( process-id,priority ); process-id, INT:ref:4 priority, INT:value < (CCL) ALTERPRIORITY failed, or no process was designated as process-id. = (CCE) The priority of the process is altered. ARMTRAP (Superseded by SIGACTION_INIT_) Specifies a location within the application program where execution begins if a trap occurs. CALL ARMTRAP ( traphandlr-addr,trapstack-addr ); traphandlr-addr, INT:value trapstack-addr, INT:value AWAITIO[X] Completes a previously initiated I/O operation. CALL AWAITIO[X] ( filenum,[ buffer-addr ],[ count-transferred ],[ tag ],[ timelimit ],[ segment-id ] ); 4-8

41 Procedure Calls Summary (A-C) filenum, buffer-addr, count-transferred, tag, INT:ref:1 (AWAITIO), INT.EXT:ref:1 (AWAITIOX) INT:ref:1 (AWAITIO), INT(32).EXT:ref:1 (AWAITIOX) INT:ref:1 (AWAITIO), INT.EXT:ref:1 (AWAITIOX) INT(32):ref:1 (AWAITIO), INT(32).EXT:ref:1 (AWAITIOX),, timelimit, INT(32):value (AWAITIO, AWAITIOX) > 0D A wait-for-completion is specified. = -1D An indefinite wait is indicated. = 0D A check for completion is specified. < -1D File-system error 590 occurs. omitted An indefinite wait is indicated. segment-id, INT.EXT:ref:1 (AWAITIOX only) < (CCL) An error occurred (call FILEINFO). = (CCE) An I/O operation finished. > (CCG) A warning occurred (call FILEINFO). BACKSPACEEDIT Sets the current record number of an IOEdit file to that of the line preceding what was the current record before the call. BACKSPACEEDIT is an IOEdit procedure and can be used only with files that have been opened by OPENEDIT or OPENEDIT_. error := BACKSPACEEDIT ( filenum ); error, INT filenum, INT:value 4-9

42 Procedure Calls Summary (A-C) BINSEM_CLOSE_ Closes access to a binary semaphore. error := BINSEM_CLOSE_ ( semid ); error, INT 0 No error. 29 Required parameter missing. The semid parameter must be specified Invalid parameter. The semid parameter does not identify a binary semaphore that is opened by the calling process. The corresponding OSS errno value is EINVAL Deadlock. The binary semaphore specified by semid cannot be closed because it is locked by the calling process. The corresponding OSS errno value is EDEADLK. semid, INT(32):value BINSEM_CREATE_ Creates, opens, and locks a binary semaphore. error := BINSEM_CREATE_ ( semid,security ); error, INT 0 No error. 22 Bounds error. The semid parameter cannot be written to by the calling process. 29 Required parameter missing. The semid and security parameters must be specified. 4-10

43 Procedure Calls Summary (A-C) 4022 Invalid parameter. The security parameter is not a valid value. Specifying an invalid value for security could cause unpredictable results in future releases. The corresponding OSS errno value is EINVAL Process cannot open the binary semaphore. The process has reached the maximum number of binary semaphores it can open, or the process file segment (PFS) has reached the maximum limit of available space. The corresponding OSS errno value is EMFILE No space. The processor has reached the maximum limit of space available for binary semaphores. The corresponding OSS errno value is ENOSPC. semid, INT(32).EXT:ref:1 security, INT:value BINSEM_FORCELOCK_ Forces a lock on a binary semaphore. status := BINSEM_FORCELOCK_ ( semid,processhandle ); status, INT 0 No error. 22 Bounds error. The processhandle parameter cannot be written to by the calling process Invalid parameter. The semid parameter does not identify a binary semaphore that is opened by the calling process. The corresponding OSS errno value is EINVAL Deadlock. The binary semaphore was forsaken before the procedure call, and it is now locked. The corresponding OSS errno value is EDEADLK Already locked. The binary semaphore was locked by the calling process before the procedure call, and it remains locked. The corresponding OSS errno value is EALREADY. semid, INT(32):value processhandle, INT.EXT:ref:

44 Procedure Calls Summary (A-C) BINSEM_LOCK_ Locks a binary semaphore. status := BINSEM_LOCK_ ( semid,timeout ); status, INT 0 No error. The binary semaphore becomes locked Operation timed out. The time-out value was reached before the binary semaphore could be locked. The corresponding OSS errno value is EAGAIN Invalid parameter. The semid parameter does not identify a binary semaphore that is opened by the calling process. The corresponding OSS errno value is EINVAL Deadlock. The binary semaphore was forsaken before the procedure call, and it is now locked. The corresponding OSS errno value is EDEADLK. semid, INT(32):value timeout, INT(32):value BINSEM_OPEN_ Opens a binary semaphore. error := BINSEM_OPEN_ ( semid,processhandle,proc-semid ); error, INT 0 No error. 22 Bounds error. The semid parameter cannot be written by the calling process, or the processhandle parameter cannot be read from the calling process. 29 Required parameter missing. The semid, processhandle, and procsemid parameters must be specified No entry. The proc-semid and processhandle parameters do not identify a binary semaphore in the processor. The corresponding OSS errno value is ENOENT. 4-12

45 Procedure Calls Summary (A-C) 4013 Invalid access. The calling process does not have access to the binary semaphore because of its security. The security for a binary semaphore is set by the BINSEM_CREATE_ procedure. The corresponding OSS errno value is EACCESS Invalid parameter. The processhandle parameter does not specify a process. A process that is being created or is terminating is treated as though it does not exist. The corresponding OSS errno value is EINVAL Process cannot open the binary semaphore. The process has reached the maximum number of binary semaphores it can open, or the process file segment (PFS) has reached the maximum limit of available space. The corresponding OSS errno value is EMFILE. semid, INT(32).EXT:ref:1 processhandle, INT.EXT:ref:10 proc-semid, INT(32):value BINSEM_UNLOCK_ Unlocks a binary semaphore. error := BINSEM_UNLOCK_ ( semid ); error, INT 0 No error Cannot lock. The semid parameter is not locked by the calling process. The corresponding OSS errno value is EPERM Invalid parameter. The semid parameter does not identify a binary semaphore that is opened by the calling process. The corresponding OSS errno value is EINVAL. semid, INT(32):value BREAKMESSAGE_SEND_ Sends a break-on-device message to a specified process. error := BREAKMESSAGE_SEND_ ( processhandle,receiver-filenum,[ breaktag ] ); 4-13

46 Procedure Calls Summary (A-C) error, INT processhandle, INT.EXT:ref:10 receiver-filenum, INT:value breaktag, INT.EXT:ref:2 CANCEL Cancels the oldest incomplete operation on a file opened for nowait I/O. CALL CANCEL ( filenum ); filenum, INT:value < (CCL) An error occurred (call FILEINFO). = (CCE) The operation was canceled. CANCELPROCESSTIMEOUT Cancels a timer set by SIGNALPROCESSTIMEOUT. CALL CANCELPROCESSTIMEOUT ( tag ); tag, INT:value = (CCE) CANCELPROCESSTIMEOUT was successful. > (CCG) The value of tag was invalid. CANCELREQ Cancels an incomplete operation on a file opened for nowait I/O. CALL CANCELREQ ( filenum,[ tag ] ); filenum, INT:value tag, INT(32):value 4-14