OSI/AS SCF Reference Manual Abstract This manual describes the Subsystem Control Facility (SCF) commands that are specific to the Compaq OSI/AS data communications subsystem. These commands are used to configure and control the OSI/AS subsystem. This manual also describes the SCF commands used to display OSI/AS configuration and status information and the OSI/AS subsystem-specific PTrace commands used to format and display trace records. Product Version OSI/AS D43 and G06.
Document History Part Number Product Version Published 424121-001 OSI/AS D43 OSI/AS G06.07 December 1999 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; 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.
OSI/AS SCF Reference Manual Glossary Index Figures What’s New in This Manual xiii xiii Manual Information New and Changed Information About This Manual Tables xiii xv Manual Audience xv Manual Contents xvi xvii OSI/AS Manual Set xviii Related Manuals OSI/AS and OSI/TS Supported Standards xix Your Comments Invited xix Notation Conventions xx 1.
Contents 2. OSI/AS SCF Commands (continued) 2.
Contents 2. OSI/AS SCF Commands (continued) 2.
Contents 2. OSI/AS SCF Commands (continued) 2.
Contents 2. OSI/AS SCF Commands (continued) 2.
Contents 2. OSI/AS SCF Commands (continued) 2. OSI/AS SCF Commands (continued) VERSION Command Syntax 2-235 VERSION null Command 2-235 VERSION PROCESS Command 2-246 VERSION SUBSYS Command 2-236 Examples of the VERSION Command 2-237 3.
Contents 3. OSI/AS Trace Facility (continued) 3. OSI/AS Trace Facility (continued) OPEN Request 3-33 System Message 3-33 ASN.1 Trace Records 3-34 3-34 ASN.1-ACSE Decode 3-35 ASN.1—ACSE Encode ASN.1—L6 Decode 3-36 ASN.
Contents 3. OSI/AS Trace Facility (continued) 3.
Contents A. OSI/AS SCF Command Syntax Summary A.
Contents A. OSI/AS SCF Command Syntax Summary (continued) A.
Contents C. OSI/AS SCF Examples of Configuration Command Files C. OSI/AS SCF Examples of Configuration Command Files OSI/AS on an X.25 Network C-2 OSI/AS on an X.25 Network With SNDCF and Full-IP C-6 OSI/AS on a LAN With Full-IP and No ES-IS C-8 OSI/AS on a LAN With Full-IP and ES-IS C-10 C-12 OSI/AS on a LAN With Null-IP OSI/AS, Large Application, on an X.25 Network C-14 D.
Contents Figures (continued) Figures (continued) Figure 1-4. G-Series OSI Stack Communicating With a D-Series OSI Stack Figure 3-1. Structure of the OSI/AS Processes Figure 3-2. TAPS Process Structure Figure 3-3. How Trace Records Cross the OSI Layers 3-3 3-4 3-5 Tables Table i. Manual Contents (page 1 of 2) xvi Table 2-1. OSI/AS Commands and Object Types Table 2-2. Sensitive and Nonsensitive OSI/AS SCF Commands Table 2-3. OSI/AS Object Specifications 2-4 Table 2-4.
What’s New in This Manual Manual Information OSI/AS SCF Reference Manual Abstract This manual describes the Subsystem Control Facility (SCF) commands that are specific to the Compaq OSI/AS data communications subsystem. These commands are used to configure and control the OSI/AS subsystem. This manual also describes the SCF commands used to display OSI/AS configuration and status information and the OSI/AS subsystem-specific PTrace commands used to format and display trace records.
What’s New in This Manual New and Changed Information OSI/AS SCF Reference Manual—424121-001 xiv
About This Manual This manual describes the Subsystem Control Facility (SCF) commands that are specific to the Compaq OSI/AS data communications subsystem. These commands are used to configure and control the OSI/AS subsystem. This manual also describes the SCF commands used to display OSI/AS configuration and status information and the OSI/AS subsystem-specific PTrace commands used to format and display trace records.
About This Manual Manual Contents Manual Contents Table i lists the contents of each section and appendix in this manual. Table i. Manual Contents (page 1 of 2) Section or Appendix Contents Section 1, Introduction This section provides an overview of the OSI/AS product and describes the subsystem objects. The section also discusses D- to G-series compatibility. Section 2, OSI/AS SCF Commands This section discusses the SCF commands that are specific to the OSI/AS subsystem.
About This Manual OSI/AS Manual Set Table i. Manual Contents (page 2 of 2) Section or Appendix Contents Appendix D, OSI/AS SCF Attribute Name Changes Some attribute names have been changed to improve product usability. All changes maintain backward compatibility: existing programs or command files will still work with the original names. This appendix lists the terms that have changed.
About This Manual Related Manuals Related Manuals The following manuals contain helpful information on OSI/AS and related products. These manuals provide information on underlying OSI subsystems: • • • • • • The OSI/TS Configuration and Management Manual is intended for programmers, system managers, and system operators. It describes how to write Transport Layer applications that use the Compaq OSI/Transport Services (OSI/TS) software to communicate with remote transport users across an OSI network.
About This Manual OSI/AS and OSI/TS Supported Standards The following manuals contain background information on the Compaq environment: • • • • The Introduction to Networking and Data Communications for Himalaya S-Series Servers provides an overview of Compaq networking and data communications products for G-series systems. The Introduction to Distributed Systems Management (DSM) introduces the products and components collectively known as Distributed Systems Management.
About This Manual Notation Conventions 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 manuals are a result of suggestions from our customers. Please take this opportunity to help us improve future manuals.
About This Manual General Syntax Notation [ ] 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: FC [ num ] [ -num] [ text] K [ X | D ] address-1 { } Braces.
About This Manual Notation for Messages 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.
About This Manual Change-Bar Notation [ ] 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.
About This Manual Change-Bar Notation OSI/AS SCF Reference Manual—424121-001 xxiv
1 Introduction This section contains the following topics: • • • • Overview on this page Object Types on this page G-Series and D-Series Compatibility on page 1-3 Communication Between D-Series and G-Series Systems on page 1-5 Overview This manual describes the subsystem-specific details for using SCF to configure, control, and inquire about the Compaq OSI/AS subsystem through the OSI manager process and the Tandem application, presentation, and session (TAPS) processes.
Introduction Object Types Object Types Figure 1-1 shows the OSI/AS object types supported by SCF and their hierarchical order. Figure 1-1. OSI/AS Subsystem Object Hierarchy SUBSYS or null For an OSI Manager Process: PROCESS ENTRY SERVICE PROFILE PROCESS or null For a TAPS Process: SU SERVICE CDT 010.CDD As shown, the SUBSYS (subsystem) object is at the highest point of the hierarchy, with all other objects subordinate to it.
Introduction G-Series and D-Series Compatibility However, it is recommended that these SERVICE objects be altered only through the OSI manager process. To issue commands directly to TSP processes, see the OSI/TS SCF Reference Manual. The LINE object is not supported by the OSI/AS subsystem. However, you can direct commands to LINE objects in the X25AM and TLAM subsystems in D-series releases (or PAM subsystem in G06 and later releases) that are in use by the OSI/AS subsystem.
Introduction G-Series and D-Series Compatibility Figure 1-3 shows OSI/TS running on a G-series system communicating with an NSP running on a D-series system through Expand lines. The NSP on D-series releases can be X25AM, TCP/IP, or TLAM or PAM. Figure 1-3. OSI/TS on a G-Series System Communicating With an NSP on a D-Series System G-Series D-Series OSI/TS OSI/TS NSP NSP CDT 015.
Introduction Communication Between D-Series and G-Series Systems Communication Between D-Series and G-Series Systems Figure 1-4 shows an OSI stack running on a G-series system communicating with another OSI stack running on a D-series system. The NSP on G-series can be X25AM, TCP/IP, or PAM; the NSP on the D-series can be X25AM, TCP/IP, or TLAM. Figure 1-4. G-Series OSI Stack Communicating With a D-Series OSI Stack G-Series OSI/AS D-Series OSI/AS OSI/TS OSI/TS NSP NSP CDT 016.
Introduction Communication Between D-Series and G-Series Systems OSI/AS SCF Reference Manual—424121-001 1-6
2 OSI/AS SCF Commands This section contains the following main topics: • • • • Supported Commands and Object Types on this page Object Specification on page 2-4 Attribute Default Values on page 2-16 The following detailed information about each SCF command: ° A description of the command function ° The command syntax ° The object specification, which shows the supported object types and object names ° Descriptions, by object type, of attribute-spec, if any ° Considerations to be aware of before using
OSI/AS SCF Commands Supported Commands and Object Types Table 2-1.
OSI/AS SCF Commands Sensitive and Nonsensitive Commands Sensitive and Nonsensitive Commands Because some SCF commands can have detrimental effects if improperly used, special qualification is required to use them. These commands are called sensitive commands. Commands that request information or status but do not affect operation are available to all users. These commands are called nonsensitive commands. Users that have a supergroup ID can issue sensitive commands.
OSI/AS SCF Commands Object Specification Object Specification This section describes the syntax rules for object specification (object-spec). An object specification is a combination of an object-type and object-name. The syntax for each SCF command contains the variable object-spec. Some commands may have exceptions to some of the syntax rules presented here. These exceptions are documented in the considerations for the command.
OSI/AS SCF Commands null Objects null Objects Use the null object to obtain version information or to identify all objects supported by the OSI/AS subsystem. The object-name for the null object is process-name, and it has the following format: $process-name $process-name is the name of the OSI manager or TAPS process as follows: The OSI manager name is a valid Guardian process name. Local TAPS process names can be up to six characters (the $ sign followed by five characters).
OSI/AS SCF Commands ENTRY Objects ENTRY Objects Use the ENTRY object to identify an entry in the Management Information Base (MIB). ENTRY objects allows the user to register local and remote addresses, application entity titles, and locally defined application names with the OSI manager process (that is, to enter them into the MIB). In addition, the OSI manager uses the information in the ENTRY objects to select protocol processes and to set connection attributes at different protocol layers.
OSI/AS SCF Commands ENTRY Objects #SNPA.entry-name #SNPA defines the local subnetwork point of attachment that corresponds to the given NSAP for the subnetwork to which the OSI end system is attached. Use it to configure an NSP server process and Layer 3 profile for a specific local SNPA. An SNPA entry-name is a string of up to 14 hexadecimal digits. The string must contain an even number of hexadecimal digits. #TSEL.entry-name #TSEL defines the transport service selector.
OSI/AS SCF Commands PROCESS Objects ENTRY Object-Name Examples The following are valid object-names for the ENTRY object: $OSIM.#APPL.GLOBAL_DSA $OSIM.#APPL.FILE_SERVER* $OSIM.#TSEL.000? $OSIM.#TSEL.0002 $OSIM.#NSAP.9A* $OSIM.#NSAP.9A0002 $OSIM.#SNPA.FE08008E000013 $OSIM.#SNPA.* (for LAN) (for X.25) PROCESS Objects A PROCESS object identifies a specific process. Use the PROCESS object to define processes that provide data communications and subsystem-management services.
OSI/AS SCF Commands PROCESS Objects The process-name format must be used in commands that operate on the OSI manager process. When both name formats are available, it is preferable to use indirect-process-name. The object-name for the PROCESS object for indirect-process-name has the following format: $osi-mgr-name.#process-type.internal-name $osi-mgr-name is the name of the OSI manager process. The OSI manager name is a valid Guardian process name.
OSI/AS SCF Commands PROCESS Objects PROCESS Object Wildcard Support Wildcards are supported for indirect-process-name for the following commands: ABORT PROCESS, ACTIVATE PROCESS, ALLOWOPENS PROCESS, DELETE PROCESS, INFO PROCESS, NAMES PROCESS, START PROCESS, STATUS PROCESS, STOP PROCESS, STOPOPENS PROCESS, and SUSPEND PROCESS. Specify wildcards in the #process-type or internal-name fields. Examples of the #process-type and internal-name fields with wildcards are .*.E* .#*.E* .#TA*.* .#NSP.N* .#TSP.
OSI/AS SCF Commands PROFILE Objects STOPPING The process is in transition to the STOPPED state because the STOP command was issued. The process is running but does not accept new user requests. SUSPENDED The process is running but does not accept new user requests. If the OSI manager process is in the SUSPENDED state, it does not communicate with other OSI processes and the Management Information Base (MIB) is closed.
OSI/AS SCF Commands SERVICE Objects PROFILE Object Wildcard Support Wildcards are supported for the DELETE PROFILE, INFO PROFILE, and NAMES PROFILE commands. Specify wildcards in the #profile-type or profile-name fields. Examples of the #profile-type and profile-name fields with wildcards are .*.R* .#*.R* .#L3.* .#L4.LOCAL? .#L5.L* Note. For the NAMES command, see NAMES Command Syntax on page 2-174, as wildcard support for this command does not follow the above rules.
OSI/AS SCF Commands SERVICE Objects #service-name is one of the following qualifiers: #L3 OSI manager process #L4 OSI manager process #L5 OSI manager or TAPS process #L6 OSI manager or TAPS process #ACSE OSI manager or TAPS process SERVICE Object Wildcard Support Wildcards are supported for the DELETE SERVICE, INFO SERVICE, NAMES SERVICE, and STATS SERVICE commands. Specify wildcards in the service-name field. Examples of the service-name field with wildcards are .* .#* .#? .#L* Note.
OSI/AS SCF Commands SU Objects SU Objects Use the SU (subdevice) object to define a data communications subdevice to a process. There are two types of SUs: static and dynamic. A dynamic SU object is temporary, it is added dynamically by a TAPS, TSP, or NSP process and lasts only as long as the connection exists.
OSI/AS SCF Commands SUBSYS Object SU Object-Name Examples The following are valid object-names for the SU object: $TAPS1.#Z000003 $TAPS1.#* $TAPS1.#Z000AB? SUBSYS Object Use the SUBSYS object to query and control the configuration of the OSI/AS subsystem. The object-name for the SUBSYS object is osi-mgr-name, and it has the following format: $osi-mgr-name $osi-mgr-name is the name of the OSI manager process. The OSI manager name is a valid Guardian process name.
OSI/AS SCF Commands Attribute Default Values Attribute Default Values In the following command descriptions, two terms are used to indicate default values for the attributes under the ADD and ALTER commands: • DEFAULT. When an ENTRY, PROCESS, or PROFILE object is added without an attribute specified, that attribute is configured with the indicated default value. The attribute can subsequently be altered with the ALTER command.
OSI/AS SCF Commands Attribute Default Values Table 2-4. SERVICE Default Values Set by the OSI Manager Process— Layer 3 (page 2 of 2) SERVICE Attribute Default Value Set by OSI Manager Process IPDISCARDCONGTHLD 0 IPDISCARDGENTHLD 0 IPDISCARDLIFETHLD 0 IPDISCARDREASMTHLD 0 IPDISCARDUNSUPTHLD 0 IPLIFETIME 15.000 (15 seconds) IPNULLLAYER OFF IPX25SNDCF OFF IPX25SNDCF1980ADDR ON X25ACCEPTCHG OFF X25BCUG NA* X25CUGTYPE NA* X25DESTADDR Initialized with blanks X25DISCONNECTDELAY 5.
OSI/AS SCF Commands Attribute Default Values The SERVICE object attributes in Layer 4 that have an OSIMGR default are shown in Table 2-5. Table 2-5. SERVICE Default Values Set by the OSI Manager Process— Layer 4 (page 1 of 2) SERVICE Attribute Default Value Set by OSI Manager Process ALTCLASS NA1 CHECKSUM OFF CHECKTSEL OFF CLASS NA2 CONNECTTIMEOUT 120.000 (120 seconds) DISCONNTIMEOUT 120.000 (120 seconds) EXPEDITED OFF EXTENDEDFORMAT OFF INACTIVETIMEOUT 30.
OSI/AS SCF Commands Attribute Default Values Table 2-5. SERVICE Default Values Set by the OSI Manager Process— Layer 4 (page 2 of 2) SERVICE Attribute Default Value Set by OSI Manager Process TCONPRI 0 TPDUSIZE 512 TTRTIMEOUT 90.000 (90 seconds) TWRTIMEOUT 120.000 (120 seconds) WINDOWTIMEOUT 10.000 (10 SECONDS) 1. The OSI manager process does not set a default value for this attribute; it defaults to the value of the ALTCLASS attribute in the OSI/TS subsystem. 2.
OSI/AS SCF Commands Attribute Default Values The SERVICE object attributes in Layer 7 that have an OSIMGR default are shown in Table 2-8. Table 2-8.
OSI/AS SCF Commands ABORT Command ABORT Command Use the ABORT command to terminate the operation of objects as quickly as possible— only enough processing is done to ensure the integrity of the OSI/AS subsystem. Upon successful completion of the ABORT command, configured objects (PROCESS objects) are left in the STOPPED state but are still configured in the Management Information Base (MIB), and nonconfigured objects (SU objects) are deleted. ABORT is a sensitive command.
OSI/AS SCF Commands Examples of the ABORT Command Examples of the ABORT Command The examples are designed to show correct ways of specifying command syntax. PROCESS Object ABORT PROCESS $TAPS ABORT PROCESS $OSIM.#TAPS.TAPS1 ABORT PROCESS $OSIM.#TAPS.TAPS* SU Object ABORT SU $TAPS.#Z000003 ABORT SU $TAPS.
OSI/AS SCF Commands ACTIVATE Command ACTIVATE Command Use the ACTIVATE command to return a suspended object to the STARTED state. ACTIVATE is a sensitive command. ACTIVATE Command Syntax ACTIVATE [ /OUT file-spec/ ] [ object-spec ] The object-spec is object-type object-name PROCESS PROCESS process-name indirect-process-name Considerations for the ACTIVATE Command The considerations contain information about command use that should be read before studying the command syntax in too much detail.
OSI/AS SCF Commands ADD Command ADD Command Use the ADD command to define an object to the OSI/AS subsystem. The ADD command adds objects to the Management Information Base (MIB). ADD is a sensitive command. ADD Command Syntax ADD [ /OUT file-spec/ ] [ object-spec ] [ , attribute-spec ] ...
OSI/AS SCF Commands ADD ENTRY #APPL Command Value: A hexadecimal string (0-9 and A-F) up to 8 digits long. This string must contain an even number of hexadecimal digits. Default: No default value is provided. APTITLE defines the AP title for the #APPL entry being added. AP title values are locally administered. Value: An APTITLE must be a valid ASN.1 object identifier. It must contain at least two integers, up to a maximum of 16 integers. The first integer must be between 0 and 2, inclusive.
OSI/AS SCF Commands ADD ENTRY #APPL Command L4PROFILE identifies the name of the Layer 4 profile which might be used when configuring a TSP subdevice. Value: A Layer 4 profile name in the following format: $osi-mgr-name.#L4.profile-name Default: No default value is provided. L5PROFILE identifies the name of the Layer 5 profile which might be used when configuring a TAPS subdevice. Value: A Layer 5 profile name in the following format: $osi-mgr-name.#L5.
OSI/AS SCF Commands ADD ENTRY #APPL Command L5SERVER defines the name of the TAPS process established through the use of this #APPL entry. This attribute is used only if this application name describes a connection endpoint on the local system. Value: A TAPS process name in the following format: osi-mgr-name.#TAPS.internal-name Default: No default value is provided. LOOPBACK determines whether or not a connection made with this #APPL entry will run in loopback mode at the Session Layer.
OSI/AS SCF Commands ADD ENTRY #APPL Command PSEL defines the presentation service selector for the #APPL entry being added. PSEL values are locally administered. Value: A hexadecimal string (0-9 and A-F) up to 32 digits long. This string must contain an even number of hexadecimal digits. Default: No default value is provided. SSEL defines the session service selector for the #APPL entry being added. SSEL values are locally administered.
OSI/AS SCF Commands ADD ENTRY #NSAP Command ADD ENTRY #NSAP Command An attribute-spec for the ADD ENTRY #NSAP command is one of the following attribute name and value combinations: [ [ [ [ [ L3PROFILE profile-name ] L4PROFILE profile-name ] L4SERVER indirect-process-name ] NETADDR-MODE { NORMAL | X25-1980 } ] SNPA string ] L3PROFILE identifies the name of the Layer 3 profile which might be used when configuring a TSP subdevice. Value: A Layer 3 profile name in the following format: osi-mgr-name.#L3.
OSI/AS SCF Commands ADD ENTRY #NSAP Command NETADDR-MODE identifies the addressing mode of the X.25 network service. For networks that support 1984 addressing, NORMAL specifies that the configured NSAPs will be applied within the calling and called address-extension facilities in the call request packets. For networks that support 1980 addressing, X25-1980 specifies that the NSAP address will be left out of the call request packets; instead, the DTEADDRESS and the SOURCEADDR fields will be used.
OSI/AS SCF Commands ADD ENTRY #SNPA Command ADD ENTRY #SNPA Command An attribute-spec for the ADD ENTRY #SNPA command is one of the following attribute name and value combinations: [ L3PROFILE profile-name ] [ L3SERVER indirect-process-name ] L3PROFILE identifies the name of the Layer 3 profile which might be used when configuring a TSP subdevice. Value: A Layer 3 profile name in the following format: $osi-mgr-name.#L3.profile-name Default: No default value is provided.
OSI/AS SCF Commands ADD PROCESS Command L4PROFILE identifies the name of the Layer 4 profile which might be used when configuring a TSP subdevice. Value: A Layer 4 profile name in the following format: $osi-mgr-name.#L4.profile-name Default: No default value is provided. L5PROFILE identifies the name of a Layer 5 profile which might be used when configuring a TAPS subdevice. Value: A Layer 5 profile name in the following format: $osi-mgr-name.#L5.
OSI/AS SCF Commands ADD PROCESS Command BACKUPCPU specifies the CPU where the backup process is to run when it is started by the OSI manager process. Value: 0 through 15 Default: If a value is specified for CPU, no default is provided for BACKUPCPU. If a value is not specified for CPU, the default for BACKUPCPU is the same backup CPU as the one for the OSI manager process.
OSI/AS SCF Commands ADD PROCESS Command MAXCONNECTIONS specifies the maximum number of concurrent connections allowed within a TAPS process and can also allow large-sized messages to be divided into smaller segments when sending messages to TSP processes. Value: 1 through 128 Default: 128 Smaller values allow the TAPS process to send messages in large-sized segments, resulting in greater throughput. Larger values allow the TAPS process to send messages in smaller segments. Note.
OSI/AS SCF Commands Value: ADD PROCESS Command A TAPS, TSP, or NSP process name in the following format: $process-name Local TAPS and TSP process names can be up to six characters (the $ sign followed by five characters). For example: $TAPS1 $TSP10 Remote TAPS and TSP process names can be up to five characters (the $ sign followed by four characters).
OSI/AS SCF Commands ADD PROCESS Command PRIMARYCPU specifies the CPU where the primary process is to run when it is started by the OSI manager process. Value: 0 through 15 Default: The same CPU as the OSI manager process. PRIORITY specifies the execution priority to be used when the OSI manager process starts the process. Value: 1 through 199 Default: The same priority as the OSI manager process.
OSI/AS SCF Commands ADD PROFILE #L3 Command ADD PROFILE #L3 Command An attribute-spec for the ADD PROFILE #L3 command is one of the following attribute name and value combinations: [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ IPNULLLAYER { ON | OFF } ] IPX25SNDCF { ON | OFF } ] X25ACCEPTCHG { ON | OFF } ] X25BCUG integer ] X25CUG integer ] X25CUGTYPE { BASIC | EXT | BASICOA | EXTOA } ] X25DESTADDR “address” ] X25NEGOTIATE { value | “(” value [ , value ] ...“)” } ] X25NONEGOTIATE { value | “(” value [ , value ] ...
OSI/AS SCF Commands ADD PROFILE #L3 Command X25ACCEPTCHG specifies whether an incoming call request that contains a request for the recipient to pay the charge is accepted. ON means that collect calls are accepted. OFF means that collect calls are not accepted. This attribute is used only for X.25 networks. Value: ON | OFF Default: Defaults to the value of the X25ACCEPTCHG attribute in the ALTER #L3 SERVICE command.
OSI/AS SCF Commands ADD PROFILE #L3 Command X25DESTADDR specifies the network address that is used as the called address in an outgoing callrequest packet. This attribute is used only for X.25 networks. This attribute is required when the SU initiates connections. Value: A decimal string (0-9) up to 15 digits long. Default: Defaults to the value of the X25DESTADDR attribute in the ALTER #L3 SERVICE command.
OSI/AS SCF Commands ADD PROFILE #L3 Command X25PORT specifies the logical port number to be used by the subdevice. This attribute is used only for X.25 networks. Value: 0 through 9999 Default: Defaults to the value of the X25PORT attribute in the ALTER #L3 SERVICE command. X25PRICALL enables or disables the capability of making priority calls. This attribute is used only for the DATAPAC network; it must be OFF if the network is other than DATAPAC. This attribute is used only for X.25 networks.
OSI/AS SCF Commands ADD PROFILE #L3 Command X25REMOTENET specifies the addressing conventions to be used when building the called address in a call-request packet. This attribute is used only for X.25 networks. Value: DATANET | DATAPAC | DATEXP | DDXP | PSS | TELENET | TRANSPAC | TYMNET | UNINET | X25NP | X25SA | X25UD | X25XA Default: Defaults to the value of the X25REMOTENET attribute in the ALTER #L3 SERVICE command.
OSI/AS SCF Commands ADD PROFILE #L3 Command X25THRUPUT specifies the throughput class limit for calls received (data transmission from the called DTE) (integer1) and the throughput class limit for calls initiated (data transmission from the calling DTE) (integer2). This attribute is used only for X.25 networks. Value: 3 through 12 (for both integer1 and integer2 Default: Defaults to the value of the X25THRUPUT attribute in the ALTER #L3 SERVICE command. Note that these values are based on the CCITT X.
OSI/AS SCF Commands ADD PROFILE #L4 Command ADD PROFILE #L4 Command An attribute-spec for the ADD PROFILE #L4 command is one of the following attribute name and value combinations: [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ ALTCLASS { 0 | 1 | 2 | 3 | 4 } ] CHECKSUM { ON | OFF } ] CLASS { 0 | 1 | 2 | 3 | 4 } ] CONNECTTIMEOUT time ] DISCONNTIMEOUT time ] EXPEDITED { ON | OFF } ] EXTENDEDFORMAT { ON | OFF } ] INACTIVETIMEOUT time ] L4WINDOW integer ] MAXREXMIT integer ] MULTIPLEX { ON | OFF } ] NETTYPE { A | B | C
OSI/AS SCF Commands ADD PROFILE #L4 Command CLASS specifies the preferred transport protocol class. See Considerations for the ADD Command on page 2-50 for a discussion of the relationship between the ALTCLASS, CLASS, MULTIPLEX, and NETTYPE attributes. For LANs, the transport protocol class must be 4. For X.25 networks, when IPX25SNDCF is OFF, the transport protocol class can be 0, 1, 2, 3, or 4. For X.25 networks, when IPX25SNDCF is ON, the transport protocol class must be 4.
OSI/AS SCF Commands ADD PROFILE #L4 Command EXTENDEDFORMAT specifies whether the credit and sequence numbers of TPDUs should be in extended format (ON) or normal format (OFF). This attribute is valid only when the transport protocol class is 2, 3, or 4. Value: ON | OFF Default: Defaults to the value of the EXTENDEDFORMAT attribute in the ALTER #L4 SERVICE command. INACTIVETIMEOUT specifies that if no TPDU is received within the specified time, the transport connection is aborted.
OSI/AS SCF Commands ADD PROFILE #L4 Command MULTIPLEX specifies whether more than one outgoing transport connection is mapped to one network connection (ON) or not (OFF). To be able to multiplex, two or more subdevices must have MULTIPLEX ON and have the same local NSAP and remote NSAP (for outgoing connection requests).
OSI/AS SCF Commands ADD PROFILE #L4 Command REFTIMEOUT specifies the amount of time before which no reference or sequence numbers are reused. Value: 3.000 through 180.000 (3 through 180 seconds) Default: Defaults to the value of the REFTIMEOUT attribute in the ALTER #L4 SERVICE command. REXMITTIMEOUT specifies the amount of time before which an unacknowledged TPDU is retransmitted. This attribute is valid only when the transport protocol class is 4. Value: 1.000 through 30.
OSI/AS SCF Commands ADD PROFILE #L4 Command TPDUSIZE specifies, in bytes, the maximum length of a TPDU. Value: 128 | 256 | 512 | 1024 | 2048 | 4096 | 8192. The values 4096 and 8192 are valid only when the transport protocol class is 1, 2, 3, or 4. For X.25 subnetworks: OSI/TS will adjust the value of TPDUSIZE to not exceed the value of the X25AM SYSGEN attribute MAXIOSIZE. Use the OSI/TS STATUS SU command (in the CHECK SU DISPLAY) to see the actual TPDUSIZE used when the connection was established.
OSI/AS SCF Commands ADD PROFILE #L5 Command ADD PROFILE #L5 Command An attribute-spec for the ADD PROFILE #L5 command is one of the following attribute name and value combinations: [ DISCONNTIMER time ] [ VSN1 { ON | OFF } ] [ VSN2 { ON | OFF } ] DISCONNTIMER specifies the timeout for the session disconnection and abort timer (TIM). It specifies the time the session service provider waits for a T-DISCONNECT indication after issuing a session release or abort service request.
OSI/AS SCF Commands Considerations for the ADD Command VSN2 specifies whether the application using this profile can operate over a session protocol version 2 connection. VSN1 and VSN2 can be ON at the same time, but they cannot be OFF at the same time. Just one of them can be ON, however, if only VSN2 is ON, do not specify a value for VSN1; the default for VSN1 automatically becomes OFF. The version is negotiated between the session entities at each end of the connection.
OSI/AS SCF Commands Considerations for the ADD Command Note. The following discussion explains how the OSI manager process selects information from the MIB. In the tables that accompany this discussion, the OSI manager process uses a hierarchical approach in selecting one item from each of the tables below. The OSI manager process begins at the top of each list and moves downward, selecting the first existing item.
OSI/AS SCF Commands Considerations for the ADD Command TAPS subdevice protocol-related attributes are selected: #L5 (Session) Values 1. #L5 PROFILE in local #APPL ENTRY 2. #L5 PROFILE in local #TSEL ENTRY 3. Local #L5 SERVICE TSP and NSP subdevice protocol-related attributes are selected: #L4 (Transport) Values 1. 2. 3. 4. 5. 6. 7.
OSI/AS SCF Commands Server L5SERVER (TAPS L4SERVER (TSP) L3SERVER (NSP) L5PROFILE L4PROFILE L3PROFILE Considerations for the ADD Command ADD ENTRY #APPL ADD ENTRY #TSEL X X X ADD ENTRY #NSAP ADD ENTRY #SNPA X X X X X X X X X X X Multiple sets of TAPS, TSP, and NSP processes or profiles can be assigned to one OSI address. To do this, configure multiple #APPL entries for the same OSI address and assign different servers and/or profiles as desired to each #APPL entry.
OSI/AS SCF Commands Considerations for the ADD Command PROCESS Object For the ADD PROCESS command, NAME is the only attribute that is used for NSP processes all other attributes are ignored. Both OSI/AS and OSI/TS support the MAXCONNECTIONS attribute; however, larger values can be specified (up to 1024) to a TSP process directly by issuing the SCF/TS ALTER PROCESS command. See the OSI/TS SCF Reference Manual.
OSI/AS SCF Commands Examples of the ADD Command Examples of the ADD Command The examples are designed to show correct ways of specifying command syntax. ENTRY Object ADD ENTRY $OSIM.#APPL.BB1 & , AEQUALIFIER ABCDEF01 & , APTITLE { 0, 1, 2, 39, 38, 37, 36 } & , L5SERVER $OSIM.#TAPS.TAP1 & , L4SERVER $OSIM.#TSP.TSP1 & , L4PROFILE $OSIM.#L4.MYL4P1 & , NSAP 02 & , TSEL 0001 & , SSEL 0001 & , PSEL 0002 & , DELETETIME -1 ADD ENTRY $OSIM.#APPL.
OSI/AS SCF Commands ALLOWOPENS Command ALLOWOPENS Command Use the ALLOWOPENS command to permit file-system opens to be issued to an object. This command reverses the effect of the STOPOPENS command. ALLOWOPENS is a sensitive command.
OSI/AS SCF Commands ALTER Command ALTER Command Use the ALTER command to change the values of the attributes of an existing object. The ALTER command changes only the specified attributes of the target object. ALTER is a sensitive command. Command Syntax ALTER [ /OUT file-spec/ ] [ object-spec ] { , attribute-spec [ , attribute-spec ] ...
OSI/AS SCF Commands ALTER ENTRY #APPL Command AEQUALIFIER defines the AE qualifier for the #APPL entry. AE qualifier values are locally administered. RESET: returns this attribute to the default value (no AE qualifier specified). Value: A hexadecimal string (0-9 and A-F) up to 8 digits long. This string must contain an even number of hexadecimal digits. APTITLE defines the AP title for the #APPL entry. AP title values are locally administered. Value: An APTITLE must be a valid ASN.
OSI/AS SCF Commands ALTER ENTRY #APPL Command L4PROFILE identifies the name of the Layer 4 profile which might be used when configuring a TSP subdevice. Value: A Layer 4 profile name in the following format: $osi-mgr-name.#L4.profile-name L5PROFILE identifies the name of the Layer 5 profile which might be used when configuring a TSP subdevice. Value: A Layer 5 profile name in the following format: $osi-mgr-name.#L5.
OSI/AS SCF Commands ALTER ENTRY #APPL Command LOOPBACK determines whether or not a connection made with this #APPL entry will be run loopback at the Session Layer. If LOOPBACK is ON for the called (remote) application entry, the connection can ONLY operate in loopback mode. The loopback value of a calling application entry is ignored. To achieve loopback, both connection endpoints must be local to this subsystem, although a subsystem may span several EXPAND nodes.
OSI/AS SCF Commands ALTER ENTRY #NSAP Command TSEL defines the transport service selector for the #APPL entry. TSEL values are locally administered. RESET returns this attribute to the default value (no TSEL specified). Value: A hexadecimal string (0-9 and A-F) up to 64 digits long. This string must contain an even number of hexadecimal digits.
OSI/AS SCF Commands ALTER ENTRY #NSAP Command NETADDR-MODE identifies the addressing mode of the network service. For 1980 X.25 networks, specify X25-1980. For other types of networks, specify NORMAL. Value: NORMAL | X25-1980 SNPA defines the local or remote subnetwork point of attachment (SNPA) that corresponds to the given NSAP for the LAN or X.25 network to which the OSI end system is attached. SNPA values are administered by an authority of the subnetwork.
OSI/AS SCF Commands ALTER ENTRY #SNPA Command ALTER ENTRY #SNPA Command An attribute-spec for the ALTER ENTRY #SNPA command is one of the following attribute name and value combinations: [ L3PROFILE profile-name ] [ L3SERVER indirect-process-name ] L3PROFILE identifies the name of the Layer 3 profile which might be used when configuring a TSP subdevice. Value: A Layer 3 profile name in the following format: $osi-mgr-name.#L3.
OSI/AS SCF Commands ALTER PROCESS Command L5PROFILE identifies the name of the Layer 5 profile which might be used when configuring a TAPS subdevice. Value: A Layer 5 profile name in the following format: $osi-mgr-name.#L5.profile-name L5SERVER defines the name of the TAPS process that might service connections for this TSEL. This attribute is used only for local entry names. Value: An TAPS process name in the following format: $osi-mgr-name.#TAPS.
OSI/AS SCF Commands ALTER PROCESS Command CODEFILE specifies the location of the code file (the program that the OSI manager process will run) to be executed when the OSI manager process starts the process. Value: Specify a fully qualified Guardian filename ($volume.subvolume.filename). If the filename specified is not a fully qualified filename, then the subvolume specified in the SCF program environment is used to expand the filename (from SCF, use the ENV command to examine the $volume.
OSI/AS SCF Commands ALTER PROCESS Command NAME specifies a TAPS, a TSP, or an NSP Guardian process name of the server. It is used to run a process or to try to establish communication with a process that is already running. NAME is the only attribute that is used for NSP processes; all other attributes are ignored. Value: A TAPS, TSP, or NSP process name in the following format: $process-name Local TAPS and TSP process names can be up to six characters (the $ sign followed by five characters).
OSI/AS SCF Commands ALTER PROFILE #L3 Command PRIORITY specifies the execution priority to be used when the OSI manager process starts the process. Value: 1 through 199 SWAP specifies the disk volume ($volume) to be used as a swap disk when the OSI manager process starts the process. Value: A valid Guardian volume name ($volume) indicating the desired volume.
OSI/AS SCF Commands ALTER PROFILE #L3 Command IPX25SNDCF specifies whether the subnetwork dependent convergence function (SNDCF) is used. This attribute is used only for X.25 networks. Value: ON | OFF X25ACCEPTCHG specifies whether an incoming call request that contains a request for the recipient to pay the charge is accepted. ON means that collect calls are accepted. OFF means that collect calls are not accepted. This attribute is used only for X.25 networks.
OSI/AS SCF Commands ALTER PROFILE #L3 Command X25DESTADDR specifies the network address that is used as the called address in an outgoing callrequest packet. This attribute is used only for X.25 networks. This attribute is required when the SU initiates connections. RESET returns this attribute to the#L3 SERVICE X25DESTADDR value. Value: A decimal string (0-9) up to 15 digits long.
OSI/AS SCF Commands ALTER PROFILE #L3 Command X25PRICALL enables or disables the capability of making priority calls. This attribute is used only for the DATAPAC network; it must be OFF if the network is other than DATAPAC. This attribute is used only for X.25 networks. Value: ON | OFF X25PVC specifies the channel number of the permanent virtual circuit (PVC) with which the X25AM subdevice to be created is bound. This attribute is used only for X.25 networks.
OSI/AS SCF Commands ALTER PROFILE #L3 Command X25RPOA specifies the Recognized Private Operating Agency (RPOA) transit network(s) in the facility field of a call-request packet. This attribute is used only for X.25 networks. RESET returns this attribute to the #L3 SERVICE X25RPOA value. Value: 0 through 9999 An RPOA transit network is indicated by the Data Network Identification Code (DNIC), which is an integer within the range 0 through 9999. There can be 0 through 7 DNIC's in the X25RPOA integer list.
OSI/AS SCF Commands ALTER PROFILE #L4 Command X25TRANSITDELAY specifies the transit delay in the facility field of a call-request packet. This attribute is used only for X.25 networks. RESET returns this attribute to the #L3 SERVICE X25TRANSITDELAY value. Value: 0.000 through 65.530 (0 through 65.
OSI/AS SCF Commands ALTER PROFILE #L4 Command CHECKSUM specifies whether checksum fields are added to TPDUs. This attribute is valid only when the transport protocol class is 4. Value: ON | OFF CLASS specifies the preferred transport protocol class. See Considerations for the ADD Command on page 2-50 for a discussion of the relationship between the ALTCLASS, CLASS, MULTIPLEX, and NETTYPE attributes. For LANs, the transport protocol class must be 4. For X.
OSI/AS SCF Commands ALTER PROFILE #L4 Command INACTIVETIMEOUT specifies that if no TPDU is received within the specified time, the transport connection is aborted. This attribute is valid only when the transport protocol class is 4. Value: 1.000 through 500.000 (1 through 500 seconds) L4WINDOW specifies the maximum credit allocation to the remote transport entity. This is the number of TPDUs that can be sent by the remote transport entity without acknowledgment.
OSI/AS SCF Commands ALTER PROFILE #L4 Command NETTYPE specifies the quality of the network services. Value: A|B|C Type Quality of Network Service A Acceptable rates of unsignaled and signaled errors B Acceptable rate of unsignaled errors but unacceptable rate of signaled errors C Unacceptable rate of unsignaled errors RECVSECURITY specifies whether security checking is performed on incoming CR-TPDUs.
OSI/AS SCF Commands ALTER PROFILE #L4 Command SENDSECURITY specifies the content of the protection field for CR-TPDUs and CC-TPDUs. If a value is not provided, the protection field is omitted. This attribute is valid only when the transport protocol class is 1, 2, 3, or 4. Note. Not all transport protocol implementations support this attribute. RESET returns this attribute to the #L4 SERVICE SENDSECURITY value. Value: An ASCII string up to 16 characters long.
OSI/AS SCF Commands ALTER PROFILE #L5 Command TWRTIMEOUT specifies the amount of time to wait for reassignment after network connection failures. If the value is 0 seconds, no reassignment is performed. Only nonzero values are transmitted in the CR-TPDU. This attribute is valid only when the transport protocol class is 1 or 3. Value: 0.000 through 180.000 (0 through 180 seconds) WINDOWTIMEOUT specifies the amount of time to wait before retransmitting up-to-date window information.
OSI/AS SCF Commands ALTER PROFILE #L5 Command VSN1 specifies whether the application using this profile can operate over a session protocol version 1 connection. VSN1 and VSN2 can be ON at the same time, but they cannot be OFF at the same time. Just one of them can be ON, however, if only VSN2 is ON, do not specify a value for VSN1; the default for VSN1 automatically becomes OFF. The version is negotiated between the session entities at each end of the connection.
OSI/AS SCF Commands ALTER SERVICE #L3 Command ALTER SERVICE #L3 Command An attribute-spec for the ALTER SERVICE #L3 command is one of the following attribute name and value combinations: [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ ESISCHECKSUM { ON | OFF } ] ESISENABLE { ON | OFF } ] ESISESCONFTIME time ] ESISESGROUPMACADDR { “address” | RESET } ] ESISHOLDTIME time ] ESISISGROUPMACADDR { “address” | RESET } ] ESISNOTIFYIS { ON | OFF } ] ESISQUERYRETRY integer ] ESISQUERYTIM
OSI/AS SCF Commands ALTER SERVICE #L3 Command ESISCHECKSUM specifies whether the end system to intermediate system (ES-IS) protocol entity includes a checksum in the outgoing ES-IS protocol data units (ES-IS PDUs). This attribute is valid only when ESISENABLE is ON. Value: ON | OFF OSIMGR Default: OFF ESISENABLE enables and disables the ES-IS protocol. Value: ON | OFF OSIMGR Default: ON ESISESCONFTIME specifies the interval at which the protocol reports its configuration to the subnetwork.
OSI/AS SCF Commands ALTER SERVICE #L3 Command ESISISGROUPMACADDR specifies the station group MAC address that all OSI intermediate systems listen to. This attribute is valid only when ESISENABLE is ON. Altering this attribute is normally unnecessary, but where required, the new value must be consistent with the value configured with the OSI routers (in the intermediate system). RESET returns this attribute to the default value provided by OSIMGR.
OSI/AS SCF Commands ALTER SERVICE #L3 Command IPDISCARDADDRTHLD is the threshold value that the internet protocol (IP) entity compares to the counter IPDISCARDADDR. IPDISCARDADDR is the number of times the IP discarded an IPPDU because of an address error. This attribute is valid only when IPNULLLAYER is OFF. Value: Value: 0 through 65535 If the threshold is 0, threshold events are never generated for this counter.
OSI/AS SCF Commands ALTER SERVICE #L3 Command IPDISCARDLIFETHLD is the threshold value that the IP entity compares to the counter IPDISCARDLIFE. IPDISCARDLIFE is the number of times the IP discarded an IPPDU because the lifetime of the PDU expired. This attribute is valid only when IPNULLLAYER is OFF. Value: Value: 0 through 65535 If the threshold is 0, threshold events are never generated for this counter.
OSI/AS SCF Commands ALTER SERVICE #L3 Command IPLIFETIME specifies the interval that an IPDU can exist before being discarded during its transit through the subnetwork(s). This attribute is valid only when IPNULLLAYER is OFF. Value: 1.000 through 300.000 (1 through 300 seconds OSIMGR Default: 15.000 (15 seconds) IPNULLLAYER enables or disables the use of the null (inactive subset) of the internet protocol in the Network Layer. This attribute is valid only when the transport protocol class is 4.
OSI/AS SCF Commands ALTER SERVICE #L3 Command X25BCUG specifies the bilateral closed user group ID sent in every call-request packet. This attribute is used only for X.25 networks. RESET returns this attribute to the value of the BCUG attribute in X25AM. Value: 0 through 9999 OSIMGR Default: Defaults to the value of the BCUG attribute in the X25AM subsystem. X25CUG specifies the closed user group ID (CUG ID) that is sent in every call-request packet. This attribute is used only for X.25 networks.
OSI/AS SCF Commands ALTER SERVICE #L3 Command X25DESTADDR specifies the network address that is used as the called address in an outgoing callrequest packet. This attribute is used only for X.25 networks. This attribute is required when the SU initiates connections. RESET returns this attribute to the default value provided by OSIMGR. Value: A decimal string (0-9) up to 15 digits long. OSIMGR Default: No default value is provided; the field is initialized with blanks.
OSI/AS SCF Commands ALTER SERVICE #L3 Command X25NEGOTIATE specifies the network interface characteristics that are negotiable when a connection is offered with unacceptable values for those characteristics. If X25AM receives a call-request packet that contains an unacceptable value for L3WINDOW, PKTSIZE, or THRUPUT and that characteristic has been defined as negotiable, it sends a callaccept packet containing an acceptable value for that characteristic.
OSI/AS SCF Commands ALTER SERVICE #L3 Command X25PVC specifies the channel number of the permanent virtual circuit (PVC) with which the X25AM subdevice to be created is bound. This attribute is used only for X.25 networks. If a TSP subdevice is configured to use X25PVC, all other subdevices with the same X25PVC must use transport protocol class 2, 3 or 4. They will be multiplexed to use the same X25PVC and no additional X25AM subdevices are created for either connect or attach requests.
OSI/AS SCF Commands ALTER SERVICE #L3 Command X25RPOA specifies the Recognized Private Operating Agency (RPOA) transit network(s) in the facility field of a call-request packet. This attribute is used only for X.25 networks. RESET returns this attribute to the value of the RPOA attribute in X25AM. Value: 0 through 9999 An RPOA transit network is indicated by the Data Network Identification Code (DNIC), which is an integer within the range 0 through 9999.
OSI/AS SCF Commands ALTER SERVICE #L4 Command X25TRANSITDELAY specifies the transit delay in the facility field of a call-request packet. This attribute is used only for X.25 networks. RESET returns this attribute to the value of the TRANSITDELAY attribute in X25AM. Value: 0.000 through 65.530 (0 through 65.53 seconds) OSIMGR Default: Defaults to the value of the TRANSITDELAY attribute in the X25AM subsystem.
OSI/AS SCF Commands ALTER SERVICE #L4 Command ALTCLASS specifies the protocol class to be used as an alternative to the preferred protocol class. See Considerations for the ADD Command on page 2-50 for a discussion of the relationship between the ALTCLASS, CLASS, MULTIPLEX, and NETTYPE attributes. This attribute is valid only when the transport protocol class is 1, 2, 3, or 4.
OSI/AS SCF Commands ALTER SERVICE #L4 Command CONNECTTIMEOUT specifies the amount of time to wait for responses to CR-TPDUs. Value: 3.000 through 180.000 (3 through 180 seconds) OSIMGR Default: 120.000 (120 seconds) DISCONNTIMEOUT specifies the amount of time to wait for responses to DR-TPDUs. Value: 3.000 through 180.000 (3 through 180 seconds) OSIMGR Default: 120.000 (120 seconds) EXPEDITED specifies whether the transport expedited data transfer service is supported.
OSI/AS SCF Commands ALTER SERVICE #L4 Command INBOUNDCRCONFERRTHLD is the threshold value that the Transport Layer compares to the counter INBOUNDCRCONFERR. INBOUNDCRCONFERR is the number of times the subsystem refused a CR-TPDU due to negotiation failure, duplicate source reference, mismatched references, reference overflow, refused on the network connection, session entity not attached to TSAP, or address unknown.
OSI/AS SCF Commands ALTER SERVICE #L4 Command INBOUNDTPDUXSUMERRTHLD is the threshold value that the Transport Layer compares to the counter INBOUNDTPDUXSUMERR. INBOUNDTPDUXSUMERR is the number of times the subsystem discarded a TPDU due to checksum failure. Value: 0 through 65535 If the threshold is 0, threshold events are never generated for this counter. OSIMGR Default: 0 L4TIMEOUTTHLD is the threshold value that the Transport Layer compares to the counter L4TIMEOUT.
OSI/AS SCF Commands ALTER SERVICE #L4 Command MULTIPLEX specifies whether more than one outgoing transport connection is mapped to one network connection (ON) or not (OFF). To be able to multiplex, two or more subdevices must have MULTIPLEX ON and have the same local NSAP and remote NSAP (for outgoing connection requests).
OSI/AS SCF Commands ALTER SERVICE #L4 Command OUTBOUNDCRERRTHLD is the threshold value that the Transport Layer compares to the counter OUTBOUNDCRERR. OUTBOUNDCRERR is the number of times the subsystem timed out waiting for a response to a CR-TPDU or receives a DR-TPDU refusing a connection request due to protocol error, invalid header, parameter not specified, or reason not specified. Value: 0 through 65535 If the threshold is 0, threshold events are never generated for this counter.
OSI/AS SCF Commands ALTER SERVICE #L4 Command Note. Not all transport protocol implementations support this attribute. RESET returns this attribute to the default value provided by OSIMGR (no security checking). Value: An ASCII string up to 16 characters long. OSIMGR Default: No default value is provided; the field is initialized with blanks. REFTIMEOUT specifies the amount of time before which no reference or sequence numbers are reused. Value: 3.000 through 180.
OSI/AS SCF Commands ALTER SERVICE #L4 Command TCONPRI specifies the priority of the transport connection. This attribute is used to reassign transport connections after errors have occurred. Because an agreement has not yet been reached among the implementors concerning this attribute, Compaq OSI does not currently process this field. Value: 0 through 32767 (0 being the highest priority) OSIMGR Default: 0 TPDUSIZE specifies, in bytes, the maximum length of a TPDU.
OSI/AS SCF Commands ALTER SERVICE #L5 Command WINDOWTIMEOUT specifies the amount of time to wait before retransmitting up-to-date window information. This attribute is valid only when the transport protocol class is 4. Value: 1.000 through 250.000 (1 through 250 seconds) OSIMGR Default: 10.
OSI/AS SCF Commands ALTER SERVICE #L5 Command RFSPDURECVPERMANENTTHLD (RF-SPDU received permanent threshold) specifies a threshold value that the Session Layer compares to the counter “RF SPDU Recv Permanent.” RF SPDU Recv Permanent is the number of times the Session Layer received an RF-SPDU with a reason code PV field of “SSAP identifier unknown (129)” or “proposed protocol versions not supported (132).” This counter wraps around upon overflow.
OSI/AS SCF Commands ALTER SERVICE #L5 Command VSN1 specifies whether the application using this profile can operate over a session protocol version 1 connection. VSN1 and VSN2 can be ON at the same time, but they cannot be OFF at the same time. Just one of them can be ON, however, if only VSN2 is ON, do not specify a value for VSN1; the default for VSN1 automatically becomes OFF. The version is negotiated between the session entities at each end of the connection.
OSI/AS SCF Commands ALTER SERVICE #L6 Command ALTER SERVICE #L6 Command An attribute-spec for the ALTER SERVICE #L6 command is one of the following attribute name and value combinations: [ [ [ [ ARPPPDUSENTPROTERRORGROUPTHLD CPRPPDURECVPERMANENTGROUPTHLD CPRPPDURECVTRANSIENTGROUPTHLD CPRPPDUSENTPERMANENTGROUPTHLD number number number number ] ] ] ] ARPPPDUSENTPROTERRORGROUPTHLD (ARP-PPDU sent protocol error group threshold) specifies a threshold value that the Presentation Layer compares to the count
OSI/AS SCF Commands ALTER SERVICE #ACSE Command CPRPPDURECVTRANSIENTGROUPTHLD (CPR-PPDU received transient group threshold) specifies a threshold value that the Presentation Layer compares to the counter “CPR PPDU Recv Transient Group.” CPR PPDU Recv Transient Group is the number of times the Presentation Layer received a CPR-PPDU with a provider reason field of “temporary congestion (1),” or “no PSAP available (7).” This counter wraps around upon overflow.
OSI/AS SCF Commands ALTER SERVICE #ACSE Command ACPMABORTSRECVTHLD (ACPM aborts received threshold) specifies a threshold value that the ACSE code compares to the counter “ACPM Aborts Recv.” ACPM Aborts Recv is the number of times the ACSE service received an ABRTAPDU in which the abort-source field has a value of “ACSE-service-provider (1).” This counter wraps around upon overflow. Value: 0 through 65535 If the threshold is 0, threshold events are never generated for this counter.
OSI/AS SCF Commands ALTER SERVICE #ACSE Command ACPMREJECTSRECVTHLD (ACPM rejects received threshold) specifies a threshold value that the ACSE code compares to the counter “ACPM Rejects Recv.” ACPM Rejects Recv is the number of times the ACSE service received an AAREAPDU with a result field of “rejected permanent (1),” or “rejected temporary (2),” regardless of source. This counter wraps around upon overflow.
OSI/AS SCF Commands ALTER SUBSYS Command ALTER SUBSYS Command An attribute-spec for the ALTER SUBSYS command is one of the following attribute name and value combinations: [ [ [ [ [ [ MAXNSP integer ] MAXTAPS integer ] MAXTSP integer ] MIB filename ] TAPSCODEFILE filename ] TSPCODEFILE filename ] MAXNSP specifies the maximum number of NSP processes that can be configured. Value: 1 through 32767 OSIMGR Default: 128 MAXTAPS specifies the maximum number of TAPS processes that can be configured.
OSI/AS SCF Commands Considerations for the ALTER Command TAPSCODEFILE specifies the default location of the code file for a TAPS process. Value: Specify a fully qualified Guardian filename ($volume.subvolume.filename). If the filename specified is not a fully qualified filename, then the subvolume specified in the SCF program environment is used to expand the filename (from SCF, use the ENV command to examine the $volume.subvolume definition).
OSI/AS SCF Commands • Considerations for the ALTER Command The following information applies to the Layer 5 attributes that set threshold values for Session Layer counters, the Layer 6 attributes that set threshold values for Presentation Layer counters and the ACSE attributes that set threshold values for ACSE Services: ° An EMS event message is generated whenever a counter value is nonzero and dividing the counter value by the threshold value leaves a remainder of zero.
OSI/AS SCF Commands Examples of the ALTER Command SERVICE Object • • • The ALTER SERVICE command can only be used for the OSI manager process. For ALTER SERVICE commands, the changed values for any changed attributes only apply to new connections and new profiles. Existing connections and profiles are not affected. The transport protocol class and alternate transport protocol class are determined by the ALTCLASS, CLASS, MULTIPLEX, and NETTYPE attributes. See the PROFILE Object discussion above.
OSI/AS SCF Commands Examples of the ALTER Command SERVICE Object ALTER SERVICE $OSIM.#L3, ESISCHECKSUM ON & , X25TRANSITDELAY RESET ALTER SERVICE $OSIM.#L4, ALTCLASS 1 ALTER SERVICE $OSIM.#L5, ABSPDUSENTPROTERRORTHLD 50 ALTER SERVICE $OSIM.#L6, ARPPPDUSENTPROTERRORGROUPTHLD 200 ALTER SERVICE $OSIM.#ACSE, ACPMREJECTSRECVTHLD 3000 ALTER SERVICE $OSIM.#L3.PF3, X25CUG 8, X25CUGTYPE BASIC & , X25RPOA (3,5,4,2,6) ALTER SERVICE $OSIM.#L3.
OSI/AS SCF Commands CHECK Command CHECK Command The CHECK command provides either configuration or connection information about the specified object and produces a display that summarizes the relevant information. Use the CHECK ENTRY command before starting a connection for the first time as a pre-diagnostic tool to determine whether all the necessary components have been configured and to determine what servers and protocol related attributes will be used in the connection.
OSI/AS SCF Commands CHECK ENTRY Command CHECK ENTRY Command Use the CHECK ENTRY command with the CONNECT option, to simulate a connect request between two applications that are using the same OSI manager process. Specify the calling #APPL name as the entry-name in the object-spec. Specify the called #APPL name as the entry-name in the CONNECT attribute-spec. When the command executes, it determines the configuration information that will be used when a connection is made.
OSI/AS SCF Commands CHECK ENTRY Command CONNECT Select this option to simulate a connect request between the two specified #APPLs as described on the previous page. Value: The called application entry name in the following format: $osi-mgr-name.#APPL.entry-name (Specify the calling #APPL name as the entry-name in the object-spec.) OSIMGR Default: No default value is provided. PROFILES Select this option to simulate an attach request as described on the previous page.
OSI/AS SCF Commands CHECK ENTRY Command OSIAS Detailed Check ENTRY $M250.#APPL.MYNAME #APPL entry values: *AEQualifier.. 12345678 *APTitle...... { 1 3 6 9} *PSel......... F001 *SSel......... F002 *TSel......... F003 *NSAP......... F004 *LoopBack..... OFF *DeleteTime... -1 (Static SU) *L5Profile.... *L4Profile.... \MARS.$M250.#L4.L4PFILE *L3Profile.... *L5Server..... \MARS.$M250.#TAPS.M255A *L4Server..... \MARS.$M250.#TSP.M254A *L3Server..... \MARS.$M250.#NSP.M253A #TSEL entry values: *L5Profile....
OSI/AS SCF Commands CHECK ENTRY Command L5 Profile: none specified L4 Service *AltClass................ *CheckTSel............... *ConnectTimeout.......... *Expedited............... *InactiveTimeout......... *InboundCRCongestionThld. *InboundTPDUProtoErrThld. *L4TimeoutThld........... *MaxRexmit............... *NetType................. *OutboundCRErrThld....... *PassiveMUX.............. *RecvSecurity............ *RefTimeout.............. *SendSecurity............ *TConPri................. *TTRTimeout.
OSI/AS SCF Commands CHECK ENTRY Command *IPDiscardUnsupThld.. 0 *IPLifeTime.......... *IPNullLayer......... OFF *IPX25SNDCF.......... *IPX25SNDCF1980ADDR.. ON *X25AcceptChg........ OFF *X25BCUG............. *X25CUG.............. 5 *X25CUGType.......... *X25DestAddr: 00149611234 *X25DisconnectDelay.. *X25NConMultiplex.... 512 *X25Negotiate........ L3WINDOW PKTSIZE THRUPUT *X25Port............. 10 *X25PriCall.......... *X25PVC.............. 010 *X25RemoteNet........ *X25ReverseChg....... OFF *X25RPOA.......
OSI/AS SCF Commands CHECK ENTRY Command TSP server detail shows detailed information about the TSP server that will be used if this #APPL entry is used. Source shows from which MIB entry (#APPL or #NSAP) the TSP server was selected. Codefile shows the location of the code file that will be used to create the TSP server process. Process name shows the Guardian process name that will be given to the TSP server when it is created.
OSI/AS SCF Commands CHECK ENTRY Command Service Values the last section of this display shows all of the service values for Layer 5, Layer 4, and Layer 3. For Layer 3 and Layer 4, the service entries are displayed and if a profile has been specified, the profile entries are displayed. (Profile entries, if specified, take priority over values in the service entry when a connection is made.
OSI/AS SCF Commands CHECK ENTRY Command The format of the display for the CHECK ENTRY $TMGR.#APPL.CALLING, CONNECT $TMGR.#APPL.CALLED command is OSIAS Detailed Check ENTRY $TMGR.#APPL.CALLING Local #APPL: $M250.#APPL.CALLING Remote #APPL: $M250.#APPL.CALLED #APPL entry values: *AEQualifier... Local: Remote: *APTitle....... Local: Remote: *PSel.......... Local: Remote: *SSel.......... Local: Remote: *TSel.......... Local: Remote: *NSAP.......... Local: Remote: *Loopback...... Local: Remote: *DeleteTime....
OSI/AS SCF Commands CHECK ENTRY Command #SNPA entry values: *L3Profile..... Local: Remote: *L3Server...... Local: Remote: Detail of Servers that would be used: $TMGR.#TAPS.L5SERVER Source: $TMGR.#APPL.CALLING Codefile: $PILS.T9570PH3.TAPSOBJ Process Name: \MARS.$TAS0 State: STOPPED $TMGR.#TSP.L4SERVER Source: $TMGR.#APPL.CALLING Codefile: $PILS.T9083PH3.TSPOBJ Process Name: \MARS.$TTS0 State: STOPPED $TMGR.#NSP.L3SERVER Source: $TMGR.#APPL.CALLING Process Name: \MARS.
OSI/AS SCF Commands L3 CHECK ENTRY Command Service: *ESISEnable........ *ESISESConfTime.... *ESISHoldTime...... *ESISNotifyIS...... *ESISQueryTime..... ON 0:01:00.00 0:01:00.00 OFF 0:00:01.00 *ESISChecksum...... *ESISESGroupMACAddr *ESISISGroupMACAddr *ESISQueryRetry.... OFF 09002B000004 09002B000005 3 *IPChecksum........ *IPDiscardCongThld. *IPDiscardLifeThld. *IPDiscardUnsupThld *IPNullLayer....... *IPX25SNDCF1980Addr OFF 0 0 0 OFF ON *IPDiscardAddrThld. *IPDiscardGenThld..
OSI/AS SCF Commands CHECK ENTRY Command TAPS server detail shows detailed information about the TAPS server that will be used if these #APPL entries are used. Source shows from which MIB entry (#APPL or #TSEL and called or calling) the TAPS server was selected. Codefile shows the location of the code file that will be used to create the TAPS server process. Process name shows the Guardian process name that will be given to the TAPS server when it is created.
OSI/AS SCF Commands CHECK ENTRY Command Source shows from which MIB entry (#APPL or #SNPA) the NSP server was selected. Process name shows the Guardian process name of the NSP server that will be used. State shows the state of the NSP server process as returned by STATUS PROCESS. Service values the last section of this display shows all of the service values for Layer 5, Layer 4, and Layer 3.
OSI/AS SCF Commands CHECK ENTRY Command The format of the display for the CHECK ENTRY $M250.#APPL.L, CONNECT $M250.#APPL.LOOPBK command is OSIAS Detailed Check ENTRY $TMGR.#APPL.L Local #APPL: $TMGR.#APPL.L Remote #APPL: $TMGR.#APPL.LOOPBK #APPL entry values: *AEQualifier... Local: Remote: *APTitle....... Local: Remote: *PSel.......... Local: Remote: *SSel.......... Local: Remote: *TSel.......... Local: Remote: *NSAP.......... Local: Remote: *Loopback...... Local: Remote: *DeleteTime....
OSI/AS SCF Commands CHECK ENTRY Command Applications Checked shows the names of the local and remote application entry names. INFO ENTRY Displays the first section of this display shows the following INFO ENTRY displays for the local and remote application entry names: INFO ENTRY #APPL INFO ENTRY #TSEL (detailed) Server Detail this section provides the detail of the servers for the local and remote application entry names that would be used in the connection.
OSI/AS SCF Commands CHECK ENTRY Command The format of the display for the CHECK ENTRY $MGR.#APPL, PROFILES, SERVERS command without the DETAIL option is OSIAS Check ENTRY Name Config TAPS State TSP State Verified $MGR.#APPL.A000000000000000000000000000001 YES STARTED STARTED $MGR.#APPL.A001 YES STOPPED STARTED $MGR.#APPL.A002 YES STOPPED STARTED $MGR.#APPL.A003 YES STARTED STARTED OSIAS E-00017 Object $MGR.#TSP.TSP1 Not Found OSIAS E-00017 Object $MGR.#NSP.X25A Not Found $MGR.#APPL.
OSI/AS SCF Commands CHECK ENTRY Command The format of the display for the CHECK ENTRY $M250.#APPL.CALLED, PROFILES, SERVERS command with the detail option is OSIAS Detailed Check ENTRY $TMGR.#APPL.CALLED #APPL entry values: *AEQualifier... 12345678 *APTitle....... { 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 *PSel.......... 123456789012345678901234567890AA *SSel.......... 123456789012345678901234567890BB *TSel.......... AABB123456789012345678901234567890123456789012345678901234567890 *NSAP..........
OSI/AS SCF Commands CHECK ENTRY Command L5 Service: values are superseded by the following L5 profile L5 Profile: $TMGR.#L5.L5PROFIL Source: $TMGR.#APPL.CALLED Name $TMGR.#L5.L5PROFIL L4 *Vsn1 ON OFF 0:02:00.00 *Checksum................ OFF *Class................... *Disconntimeout.......... OFF 0:00:30.00 0 0 0 3 A 0 OFF *Extendedformat.......... *InboundCRConfErrThld.... *InboundCRProtoErrThld... *InboundTPDUXsumErrThld.. *L4window................ *Multiplex...............
OSI/AS SCF Commands CHECK ENTRY Command *X25AcceptChg...... *X25CUG............ *X25DestAddr....... *X25NConMultiplex.. *X25Negotiate...... *X25Port........... *X25PVC............ *X25ReverseChg..... X25RPOA .......... *X25Thruput........ L3 OFF *X25BCUG........... *X25CUGType........ *X25DisconnectDelay 0:00:05.00 512 0 *X25PriCall........ OFF *X25RemoteNet...... OFF *X25TransitDelay... Profile: $TMGR.#L3.L3PROFIL Source: $TMGR.#APPL.CALLED *IPNullLayer...... OFF *X25AcceptChg..... *X25CUG........
OSI/AS SCF Commands CHECK ENTRY Command Codefile shows the location of the code file that will be used to create the TAPS server process. Process name shows the Guardian process name that will be given to the TAPS server when it is created. State shows the state of the TAPS server process as returned by STATUS PROCESS. TSP server detail shows detailed information about the TSP server that will be used if this #APPL entry is used.
OSI/AS SCF Commands CHECK SU Command State shows the state of the NSP server process as returned by STATUS PROCESS. Service Values the last section of this display shows all of the service values for Layer 5, Layer 4, and Layer 3. For Layer 3 and Layer 4, the service entries are displayed and if a profile has been specified, the profile entries are displayed. (Profile entries, if specified, take priority over values in the service entry when a connection is made.
OSI/AS SCF Commands CHECK SU Command DISPLAY displays the information for the SU levels specified. This option is useful in limiting the response time delay of this command. The fewer number of layers for which information is requested, the faster the response time and the smaller the impact on the servers.
OSI/AS SCF Commands CHECK SU Command LOCALNSAP displays only those SUs that establish connections with this NSAP address in their local application entry and connection. Value: A hexadecimal string (0-9 and A-F) up to 40 digits long. For LANs only: This string must contain an even number of hexadecimal digits. Note that for LANs, when using the Null-IP protocol, specify the NSAP value in the SNPA format (“FE+MACaddress”). See the SNPA attribute description for a full explanation of the SNPA value.
OSI/AS SCF Commands CHECK SU Command Value: A process name in the following format: [ \node-name.]$process-name Default: No default value is provided. USER displays only those SUs that are being used by the specified user account. Only TAPS users may be specified here. Value: a valid Guardian group-id and user-id in the following format: nn,nn Default: No default values are provided. The format of the display for the CHECK SU $TAP1.
OSI/AS SCF Commands CHECK SU Command TAP: Error Source shows the source of the last error reported on the selected SU at the TAPS level. It indicates the service layer within TAPS that generated the error in the previous column. Possible values are “ACSE”, “L6”, or “L5”. The field is blank if the TAP: Last Error field is 0. TAP: State shows the state that the Session Layer of the TAPS process is in. This is the same value displayed in the “L5 Protocol State” field in the OSI/AS STATUS SU command.
OSI/AS SCF Commands CHECK SU Command NSP: Error Source shows the source of the last error reported to OSI/TS on the selected SU at the NSP level. Possible values are blank (if no error occurred), TLAM (for D-series releases) X25AM, or PAM (for G06 and above releases). NSP: State shows the state at the NSP level. For X25AM, the possible values are Started/Ready Started/Not Ready Stopped/Ready Stopped/Not Ready The first column shows the summary state of the X25AM line object.
OSI/AS SCF Commands CHECK SU Command The format of the display for the CHECK SU $TAS0.* command with the DETAIL option is OSIAS Detailed Check SU $TAS0.#ZBT0002 -------------------------------------------------------------------ASU: -------------------------------------------------------------------TAP: OSIAS Detailed Status SU $TAS0.#ZBT0002 State............... Opens............... Opener.............. Opener Id........... Loopback............ DeleteTime.......... L4 or Loopback SU... Last Error........
OSI/AS SCF Commands CHECK SU Command AETitle AETitle Format.. 0 AEQualifier..... APTitle......... PSel.............. SSel.............. B3AA TSel.............. B3BB NSAP.............. B3CC Responding Address: (REMOTE) Application Name.. AETitle: AETitle Format.. 0 AEQualifier..... APTitle......... PSel.............. SSel.............. TSel.............. NSAP.............. -------------------------------------------------------------------TSP: OSITS Detailed Status SU $TTS0.#ZBT0002 State........ TC-State.
OSI/AS SCF Commands Considerations for the CHECK Command Note. If loopback is in effect, the “TSP:” and “NSP:” lines will be replaced by the following line: “Loopback: su-name.” Depending on the state of the TSP SU and the error situation, the NSP LINE information might or might not be available for display. If the information is not available, the following line will be displayed: “NSP: Not Available” OSI/AS Detailed Status SU display this is the detailed display for the OSI/AS STATUS SU command.
OSI/AS SCF Commands Considerations for the CHECK Command SU Object • • • The CHECK SU command can only be used for TAPS processes. See the OSI/TS SCF Reference Manual for information on using the CHECK SU command for TSP processes. Wildcards are supported for the CHECK SU command. There are a number of options to this command that can help find the particular SU in question: ° If the SU name is not known, wildcards can be used: specify the su-name (in the object-spec) with a wildcard character.
OSI/AS SCF Commands • Examples of the CHECK Command The CHECK SU command can be used to investigate active connections or completed (successful or failed) connections, but the use of this command can depend on the type of SU used in the connection: ° A static SU (where the DELETETIME attribute for ADD #ENTRY objects is set to -1) can be examined at any time during the life of the connection or after the connection has completed.
OSI/AS SCF Commands DELETE Command DELETE Command Use the DELETE command to remove objects from the OSI/AS subsystem. Only objects that were added with the ADD command can be deleted. The DELETE command removes objects from the Management Information Base (MIB). DELETE is a sensitive command.
OSI/AS SCF Commands Examples of the DELETE Command Examples of the DELETE Command The examples are designed to show correct ways of specifying command syntax. ENTRY Object DELETE ENTRY $OSIM.#NSAP.9A0001 DELETE ENTRY $OSIM.#NSAP.9A* PROCESS Object DELETE PROCESS $OSIM.#TAPS.TAPS1 DELETE PROCESS $OSIM.#TAPS.* PROFILE Object DELETE DELETE DELETE DELETE PROFILE PROFILE PROFILE PROFILE $OSIM.#L3.PROF1 $OSIM.#L4.PROF2 $OSIM.#L5.PROF3 $OSIM.#L4.
OSI/AS SCF Commands INFO Command INFO Command Use the INFO command to display configuration information, such as the current attribute values for the specified object. INFO is a nonsensitive command. INFO Command Syntax INFO [ /OUT file-spec/ ] [ object-spec ] [ , DETAIL ] The object-spec is object-type object-name ENTRY PROCESS PROCESS PROFILE SERVICE SUBSYS entry-name process-name indirect-process-name profile-name service-name osi-mgr-name Note.
OSI/AS SCF Commands INFO ENTRY #APPL Command AEQualifier shows the application entity qualifier for the #APPL entry name. APTitle shows the AP title for the #APPL entry name. PSEL shows the presentation service selector for the #APPL entry name. SSEL shows the session service selector for the #APPL entry name. TSEL shows the transport service selector for the #APPL entry name. NSAP shows the NSAP address for the #APPL entry name.
OSI/AS SCF Commands INFO ENTRY #NSAP Command L4Server shows the L4 server that was specified when the #APPL entry name was configured. L3Server shows the L3 server that was specified when the #APPL entry name was configured. INFO ENTRY #NSAP Command The format of the display for the INFO ENTRY #NSAP command without the DETAIL option is OSIAS Info ENTRY Name $OSIM.#NSAP.9A0002 *L4Profile $OSIM.#L4.PROF1 Name shows the name of the ENTRY object.
OSI/AS SCF Commands INFO ENTRY #SNPA Command L4Server shows the L4 server that was specified when the NSAP entry was configured. INFO ENTRY #SNPA Command The format of the display for the INFO ENTRY #SNPA command without the DETAIL option is OSIAS Info ENTRY Name $OSIM.#SNPA.123456 *L3Profile $OSIM.#L3.PROF1 Name shows the name of the ENTRY object. L3Profile shows the L3 profile that was specified when the SNPA entry was configured.
OSI/AS SCF Commands INFO ENTRY #TSEL Command INFO ENTRY #TSEL Command The format of the display for the INFO ENTRY #TSEL command without the DETAIL option is OSIAS Info ENTRY Name $OSIM.#TSEL.0002 *L5Profile $OSIM.#L5.P1 Name shows the name of the ENTRY object. L5Profile shows the L5 profile that was specified when the TSEL entry was configured. The format of the display for the INFO ENTRY #TSEL command with the DETAIL option is OSIAS Detailed Info ENTRY \MARS.$OSIM.#TSEL.0002 *L5Profile..... $OSIM.
OSI/AS SCF Commands INFO PROCESS Command INFO PROCESS Command The format of the display for the INFO PROCESS command without the DETAIL option is OSIAS Info PROCESS *Name $TAPS *Primary *Backup *Priority *Codefile CPU CPU 2 3 150 $MARS.OSI.TAPS Name shows the name of the PROCESS object. This is the only field in the display for NSP processes. PrimaryCPU shows the CPU number of the primary CPU. BackupCPU shows the CPU number of the backup CPU.
OSI/AS SCF Commands INFO PROCESS Command The format of the display for the INFO PROCESS command with the DETAIL option is OSIAS Detailed Info PROCESS \MARS.$TMGR.#TAPS.TAPY *PrimaryCPU....... 6 *BackupCPU........ NONE *Priority......... 139 *Codefile......... $PILS.T9570PH3.TAPSOBJ *HighPIN.......... ON *MaxConnections... 128 *Swap............. $KNOZ *Name........... \MARS.$TAPY PrimaryCPU shows the CPU number of the primary CPU. BackupCPU shows the CPU number of the backup CPU.
OSI/AS SCF Commands INFO PROFILE #L3 Command INFO PROFILE #L3 Command The format of the display for the INFO PROFILE #L3 command without the DETAIL option is OSIAS Info PROFILE Name $OSIM.#L3.PROF1 *IPNullLayer OFF *IPX25SNDCF OFF Name shows the name of the profile object. IPNullLayer shows whether the null (inactive subset) of the internet protocol in the Network Layer is enabled or disabled. IPX25SNDCF shows whether the subnetwork dependent convergence function is used.
OSI/AS SCF Commands INFO PROFILE #L3 Command X25BCUG shows the bilateral closed user group ID that is sent in every call-request packet. X25CUG shows the closed user group ID that is sent in every call-request packet. X25CUGType shows the type of closed user group (CUG) facility. X25DestAddr shows the called address for outgoing call-request packets. X25Negotiate shows the names of the negotiable network interface characteristics. X25Port shows the logical port number used by the subdevice.
OSI/AS SCF Commands INFO PROFILE #L4 Command INFO PROFILE #L4 Command The format of the display for the INFO PROFILE #L4 command without the DETAIL option is OSIAS Info PROFILE Name $OSIM.#L4.P1 *Class *TPDUSize *Checksum *NetType *Expedited 2 1024 OFF A OFF Name shows the name of the profile object. Class shows the preferred transport protocol class value. TPDUSize shows the maximum length of a TPDU. Checksum shows whether checksum fields are added to TPDUs.
OSI/AS SCF Commands INFO PROFILE #L4 Command Checksum shows whether checksum fields are added to TPDUs. Class shows the preferred transport protocol class value. ConnectTimeout shows the amount of time to wait for responses to CR-TPDUs. DisconnTimeout shows the amount of time to wait for responses to DR-TPDUs. Expedited shows whether the transport expedited data transfer service is supported.
OSI/AS SCF Commands INFO PROFILE #L5 Command RexmitTimeout shows the amount of time before which an unacknowledged TPDU is retransmitted. SendSecurity shows the content of the protection field for CR-TPDUs and CC-TPDUs. TConPri shows the priority of the transport connection. TPDUSize shows the maximum length of a TPDU. TTRTimeout shows the maximum amount of time to try reassignments after network connection failures.
OSI/AS SCF Commands INFO SERVICE #L3 Command DisconnTimer shows the session disconnection and abort timer (TIM). The format of the display for the INFO PROFILE #L5 command with the DETAIL option is OSIAS Detailed Info PROFILE \MARS.$OSIM.#L5.PROF1 *DisconnTimer...... 0:02:00.000 *Vsn1.............. ON *Vsn2............ OFF DisconnTimer shows the session disconnection and abort timer (TIM).
OSI/AS SCF Commands INFO SERVICE #L3 Command The format of the display for the INFO SERVICE #L3 command with the DETAIL option is OSIAS Detailed Info SERVICE \MARS.$TMGR.#L3 *ESISEnable........ *ESISESConfTime.... *ESISHoldTime...... *ESISNotifyIS...... *ESISQueryTime..... ON 0:01:00.00 0:01:00.00 OFF 0:00:01.00 *ESISChecksum...... *ESISESGroupMACAddr *ESISISGroupMACAddr *ESISQueryRetry.... OFF 09002B000004 09002B000005 3 *IPChecksum........ *IPDiscardCongThld. *IPDiscardLifeThld.
OSI/AS SCF Commands INFO SERVICE #L3 Command ESISQueryRetry shows the number of times the ES-IS protocol entity retries to obtain the NSAPSNPA before giving up. ESISQueryTime show the interval during which the ES-IS protocol waits for a reply to its query of NSAP-SNPA mapping before retrying or giving up. IPChecksum shows whether checksums are generated for outgoing IPDUs. IPDiscardAddrThld shows the threshold value that the IP entity compares to the counter “IP Discard Addr.
OSI/AS SCF Commands INFO SERVICE #L3 Command IPX25SNDCF shows whether the subnetwork dependent convergence function (SNDCF) is used. IPX25SNDCF1980Addr shows whether the subnetwork dependent convergence function (SNDCF) is used. X25AcceptChg shows whether incoming collect calls are accepted. X25BCUG shows the bilateral closed user group ID that is sent in every call-request packet. X25CUG shows the closed user group ID that is sent in every call-request packet.
OSI/AS SCF Commands INFO SERVICE #L4 Command X25RemoteNet shows the type of addressing conventions used when building the called address in a call request packet. X25ReverseChg shows whether an outgoing call request asks the recipient to pay the charges. X25RPOA shows the Recognized Private Operating Agency (RPOA) transit network(s) value specified in the facility field of a call-request packet. X25Thruput shows the throughput class limit for calls received and calls initiated.
OSI/AS SCF Commands INFO SERVICE #L4 Command OSIAS Detailed Info SERVICE \MARS.$OSIM.#L4 *AltClass................ *CheckTSEL............... *ConnectTimeout.......... *Expedited............... *InactiveTimeout......... *InboundCRCongestionThld. *InboundTPDUProtoErrThld. *L4TimeoutThld........... *MaxRexmit............... *NetType................. *OutboundCRErrThld....... *PassiveMUX.............. *RecvSecurity............ *RefTimeout.............. *SendSecurity............ *TConPri.................
OSI/AS SCF Commands INFO SERVICE #L4 Command InactiveTimeout shows the amount of time after which the transport connection is aborted if no TPDU is received. InboundCRConfErrThld shows the threshold value that the Transport Layer compares to the counter “Inbound CR Conf Err.” InboundCRCongestionThld shows the threshold value that the Transport Layer compares to the counter “Inbound CR Congestion.
OSI/AS SCF Commands INFO SERVICE #L4 Command OutboundCRConfErrThld shows the threshold value that the Transport Layer compares to the counter “Outbound CR Conf Err.” OutboundCRErrThld shows the threshold value that the Transport Layer compares to the counter “Outbound CR Err.” OutboundTPDUProtoErrThld shows the threshold value that the Transport Layer compares to the counter “Outbound TPDU Proto Err.
OSI/AS SCF Commands INFO SERVICE #L5 Command WindowTimeout shows the amount of time to wait before retransmitting up-to-date window information. INFO SERVICE #L5 Command The format of the display for the INFO SERVICE #L5 command without the DETAIL option is OSIAS Info SERVICE Name $OSIM.#L5 *Vsn1 ON *Vsn2 OFF *DisconnTimer 0:01:00.000 Name shows the name of the SERVICE object.
OSI/AS SCF Commands INFO SERVICE #L6 Command RFSPDURecvPermanentThld shows the threshold value that the Session Layer compares to the counter “RF SPDU Recv Permanent.” RFSPDURecvTemporaryThld shows the threshold value that the Session Layer compares to the counter “RF SPDU Recv Temporary.” RFSPDUSentPermanentThld shows the threshold value that the Session Layer compares to the counter “RF SPDU Sent Permanent.
OSI/AS SCF Commands INFO SERVICE #ACSE Command OSIAS Detailed Info SERVICE \MARS.$OSIM.#L6 *ARPPPDUSentProtErrorGroupThld.. *CPRPPDURecvPermanentGroupThld.. *CPRPPDURecvTransientGroupThld.. *CPRPPDUSentPermanentGroupThld.. 0 25 0 0 ARPPPDUSentProtErrorGroupThld shows the threshold value that the Presentation Layer compares to the counter “ARP PPDU Sent Prot Error Group.
OSI/AS SCF Commands INFO SERVICE #ACSE Command ACPMRejectsRecvThld shows the threshold value that the ACSE code compares to the counter “ACPM Rejects Recv.” ACPMRejectsSentThld shows the threshold value that the ACSE code compares to the counter “ACPM Rejects Sent.” The format of the display for the INFO SERVICE #ACSE command with the DETAIL option is OSIAS Detailed Info SERVICE \MARS.$OSIM.#ACSE *ACPMAbortsRecvThld............. *ACPMAbortsSentThld............. *ACPMAssocPRejectsThld..........
OSI/AS SCF Commands INFO SUBSYS Command INFO SUBSYS Command The format of the display for the INFO SUBSYS command without the DETAIL option is OSIAS Info SUBSYS Name $OSIM *MaxNSP 12 *MaxTSP 24 *MaxTAPS 27 *MIB $MARS.OSI.MIB Name shows the name of the OSI manager process. MaxNSP shows the maximum number of NSP processes that can be configured. MaxTSP shows the maximum number of TSP processes that can be configured. MaxTAPS shows the maximum number of TAPS processes that can be configured.
OSI/AS SCF Commands Considerations for the INFO Command Current TSPs shows the current number of TSP processes. MaxTAPS shows the maximum number of TAPS processes that can be configured. Current TAPSs shows the current number of TAPS processes. MIB shows the location of the Management Information Base. TSPCodeFile shows the default location of the TSP process code (program) file. TAPSCodeFile shows the default location of the TAPS process code (program) file.
OSI/AS SCF Commands Examples of the INFO Command SERVICE Object • • The INFO SERVICE command can only be used for the OSI manager process. Wildcards are supported for the INFO SERVICE command. Examples of the INFO Command The examples are designed to show correct ways of specifying command syntax. ENTRY Object INFO INFO INFO INFO INFO ENTRY ENTRY ENTRY ENTRY ENTRY $OSIM.#APPL.BB2, DETAIL $OSIM.#TSEL.0002 $OSIM.#NSAP.9A0002 $OSIM.#SNPA.123456 $OSIM.#APPL.
OSI/AS SCF Commands LISTOPENS Command LISTOPENS Command Use the LISTOPENS command to display information about file-system opens that apply to the specified object. LISTOPENS is a nonsensitive command. LISTOPENS Command Syntax LISTOPENS [ /OUT file-spec/ ] [ object-spec ] The object-spec is object-type object-name PROCESS SU process-name su-name LISTOPENS PROCESS Command The format of the display for the LISTOPENS PROCESS command is OSIAS Listopens PROCESS \MARS.
OSI/AS SCF Commands LISTOPENS SU Command Reqs shows the number of current requests outstanding for the opener. LISTOPENS SU Command The format of the display for the LISTOPENS SU command is OSI/AS Listopens SU \MARS.$TAPS.#Z000003 Primary Openers \PLUTO.$APPL1 Backup FNUM Reqs Opener PID Opener PID 6,325 5,400 5 0 Openers lists the names (system name and process name) of processes that have opened the specified SU object.
OSI/AS SCF Commands Examples of the LISTOPENS Command Examples of the LISTOPENS Command The examples are designed to show correct ways of specifying command syntax. PROCESS Object LISTOPENS PROCESS $OSIM LISTOPENS PROCESS $TAPS SU Object LISTOPENS SU $TAPS.#Z000003 LISTOPENS SU $TAPS.
OSI/AS SCF Commands NAMES Command NAMES Command Use the NAMES command to display a list of the subordinate object types and names for the specified object. The SUB option is supported in only two cases; see the object-spec below. NAMES is a nonsensitive command. NAMES Command Syntax NAMES [ /OUT file-spec/ ] [ object-spec ] The object-spec is object-type object-name null ENTRY ENTRY ENTRY PROCESS PROCESS PROCESS PROCESS PROFILE PROFILE PROFILE SERVICE SERVICE SU SU SUBSYS $process-name $osi-mgr-name.
OSI/AS SCF Commands NAMES null Command NAMES null Command The format of the display for the NAMES null command when issued to the OSI manager process is OSIAS Names \MARS.$OSIM SUBSYS $OSIM PROCESS $OSIM $OSIM.#TSP.PSP0 SERVICE $OSIM.#L3 $OSIM.#NSP.PMX7 $OSIM.#TAPS.PAP1 $OSIM.#L4 PROFILE $OSIM.#L3.P3 $OSIM.#L5 $OSIM.#L4.P2 ENTRY $OSIM.#APPL.BB2 $OSIM.#SNPA.0001 $OSIM.#TSEL.0001 $OSIM.#NSP.PMX8 $OSIM.#TAPS.PAP0 $OSIM.#L6 $OSIM.#ACSE $OSIM.#L5.P3 $OSIM.#APPL.BB4 $OSIM.#SNPA.0000 $OSIM.#TSEL.
OSI/AS SCF Commands NAMES ENTRY Command The format of the display for the NAMES null command when issued to a TAPS process is OSIAS Names \MARS.$TAPS PROCESS $TAPS SERVICE $TAPS.#L5 $TAPS.#L6 $TAPS.#ACSE SU $TAPS.#Z000000 PROCESS shows the name of the TAPS process. SERVICE shows a list of the SERVICE objects associated with the TAPS process. SU shows a list of the SU objects associated with the TAPS process.
OSI/AS SCF Commands NAMES PROCESS Command NAMES PROCESS Command The format of the display for the NAMES PROCESS command when issued to the OSI manager process is OSIAS Names PROCESS \MARS.$OSIM.*.* PROCESS $OSIM $OSIM.#TSP.PSP0 $OSIM.#NSP.PMX7 $OSIM.#TAPS.PAP1 $OSIM.#NSP.PMX8 $OSIM.#TAPS.PAP0 PROCESS shows a list of the PROCESS objects associated with the OSI manager process. The format of the display for the NAMES PROCESS command when issued to a TAPS process is OSIAS Names PROCESS \MARS.
OSI/AS SCF Commands NAMES SERVICE Command NAMES SERVICE Command The format of the display for the NAMES SERVICE command when issued to the OSI manager process is OSIAS Names SERVICE \MARS.$OSIM.* SERVICE $OSIM.#L3 $OSIM.#L4 $OSIM.#L5 $OSIM.#L6 $OSIM.#ACSE SERVICE shows a list of the SERVICE objects associated with the OSI manager process. The format of the display for the NAMES SERVICE command when issued to a TAPS process is OSIAS Names SERVICE \MARS.$TAPS.* SERVICE $TAPS.#L5 $TAPS.#L6 $TAPS.
OSI/AS SCF Commands NAMES SUBSYS Command NAMES SUBSYS Command The format of the display for the NAMES SUBSYS command when issued to the OSI manager process is OSIAS Names SUBSYS \MARS.$OSIM SUBSYS $OSIM PROCESS $OSIM $OSIM.#TSP.PSP0 SERVICE $OSIM.#L3 $OSIM.#NSP.PMX7 $OSIM.#TAPS.PAP1 $OSIM.#L4 PROFILE $OSIM.#L3.P1 $OSIM.#L5 $OSIM.#L4.P2 ENTRY $OSIM.#APPL.BB2 $OSIM.#SNPA.0001 $OSIM.#TSEL.0001 $OSIM.#NSP.PMX8 $OSIM.#TAPS.PAP0 $OSIM.#L6 $OSIM.#ACSE $OSIM.#L5.P3 $OSIM.#APPL.BB4 $OSIM.#SNPA.
OSI/AS SCF Commands Considerations for the NAMES Command Considerations for the NAMES Command The considerations contain information about command use that should be read before studying the command syntax in too much detail. All Objects • See NAMES Command Syntax on page 2-174 for the wildcard support. Examples of the NAMES Command The examples are designed to show correct ways of specifying command syntax.
OSI/AS SCF Commands Examples of the NAMES Command PROFILE Object NAMES NAMES NAMES NAMES PROFILE PROFILE PROFILE PROFILE $OSIM.*.* $OSIM.#L3.* $OSIM.#L4.* $OSIM.#L5.* SERVICE Object NAMES SERVICE $OSIM.* NAMES SERVICE $TAPS.* SU Object NAMES SU $TAPS.#Z000003 NAMES SU $TAPS.
OSI/AS SCF Commands START Command START Command Use the START command to initiate the operation of an object. Successful completion of the START command leaves the object in the STARTED state. START is a sensitive command.
OSI/AS SCF Commands Examples of the START Command Examples of the START Command The examples are designed to show correct ways of specifying command syntax. PROCESS Object START PROCESS $TAPS START PROCESS $OSIM.#TAPS.TAPS1 START PROCESS $OSIM.*.
OSI/AS SCF Commands STATS Command STATS Command Use the STATS command to display statistical information for the specified object. STATS is a sensitive command when the RESET option is specified. STATS Command Syntax STATS [ /OUT file-spec/ ] [ object-spec ] [ , RESET ] The object-spec is object-type object-name PROCESS SERVICE SU SUBSYS process-name service-name su-name osi-mgr-name STATS PROCESS Command The format of the display for the STATS PROCESS command is OSIAS Stats PROCESS \MARS.
OSI/AS SCF Commands STATS SERVICE #L5 Command Request Control Blocks shows the number of request control block table entries currently in use and the maximum number of request control block table entries ever in use. File System Requests shows the number of various file-system requests encountered by the PROCESS object. STATS SERVICE #L5 Command The format of the display for the STATS SERVICE #L5 command is OSIAS Stats SERVICE \MARS.$TAS0.#L5 Reset Time.... 20 Jun 1991, 18:23:18.823 Sample Time...
OSI/AS SCF Commands STATS SERVICE #L5 Command Refuse SPDUs: Received No reason shows the number of times the Session Layer received an RF-SPDU with a reason code parameter value parameter value (PV) field of “reason not specified (0).” This counter wraps around upon overflow. Value 0 through 65535 Refuse SPDUs: Sent No reason shows the number of times the Session Layer sent or attempted to send an RF-SPDU with a reason code parameter value (PV) field of “reason not specified (0).
OSI/AS SCF Commands STATS SERVICE #L5 Command Refuse SPDUs: Received Temporary shows the number of times the Session Layer received an RF-SPDU with a reason code parameter value (PV) field of “SS User not attached to SSAP (130)” or “SPM congestion at connect time (131).” This counter wraps around upon overflow. Value 0 through 65535 Refuse SPDUs: Received Temporary Threshold shows a threshold value that the Session Layer compares to the counter RF SPDU RECV TEMPORARY.
OSI/AS SCF Commands STATS SERVICE #L5 Command Abort SPDUs: Sent No reason shows the number of times the Session Layer sent or attempted to send an ABSPDU with a reason code portion of the transport disconnect parameter value (PV) field of “no reason (bit 4 = 1).” This counter wraps around upon overflow.
OSI/AS SCF Commands STATS SERVICE #L5 Command Total Refuse/Abort SPDUs Received shows the total number of Refuse and Abort SPDUs that were received by this service. This counter wraps around upon overflow. Value 0 through 2147483647 Total Refuse/Abort SPDUs Sent shows the total number of Refuse and Abort SPDUs that this service sent or attempted to send. This counter wraps around upon overflow. Value 0 through 2147483647 Total SPDUs Received shows the number of SPDUs received by this TAPS process.
OSI/AS SCF Commands STATS SERVICE #L5 Command Total Data Bytes Sent shows the total number of user data bytes sent by the service. This counter wraps around upon overflow. Value 0 through 2147483647 Connect SPDUs Received shows the number of times the Session Layer received a Connect (CN) SPDU. This counter wraps around upon overflow. Value 0 through 65535 Connect SPDUs Sent shows the number of times the Session Layer sent, or attempted to send, a Connect (CN) SPDU.
OSI/AS SCF Commands STATS SERVICE #L5 Command Not Finished SPDUs Received shows the number of times the Session Layer received a Not Finished (NF) SPDU. This counter wraps around upon overflow. Value 0 through 65535 Not Finished SPDUs Sent shows the number of times the Session Layer sent, or attempted to send, a Not Finished (NF) SPDU. This counter wraps around upon overflow. Value 0 through 65535 Finish SPDUs Received shows the number of times the Session Layer received a Finish (FN) SPDU.
OSI/AS SCF Commands STATS SERVICE #L6 Command Available SUs shows the total number of SUs that are available for use at the present time in the specified TAPS process. It indicates how many more connections can be made. It ranges from MAXCONNECTIONS to 0. When zero is reached, no more connections will be accepted by this TAPS process. This value will not change when RESET is specified. STATS SERVICE #L6 Command The format of the display for the STATS SERVICE #L6 command is OSIAS Stats SERVICE \MARS.
OSI/AS SCF Commands STATS SERVICE #L6 Command CPR PPDUs: Sent No reason shows the number of times the Presentation Layer sent or attempted to send a CPRPPDU with a provider reason field of “Reason not specified (0).” This counter wraps around upon overflow.
OSI/AS SCF Commands STATS SERVICE #L6 Command CPR PPDUs: Received Transient Threshold shows a threshold value that the Presentation Layer compares to the counter CPR PPDU RECV TRANSIENT GROUP. Value 0 through 65535 CPR PPDUs: Sent Transient shows the number of times the Presentation Layer sent or attempted to send a CPRPPDU with a provider reason field of “temporary congestion (1)” or “no PSAP available (7).” This counter wraps around upon overflow.
OSI/AS SCF Commands STATS SERVICE #L6 Command ARP PPDUs: Received Protocol Error shows the number of times the Presentation Layer received an ARP-PPDU with a provider reason field of “unrecognized PPDU (1),” “unexpected PPDU (2),” “unexpected session service parameter (3),” “unrecognized PPDU parameter (4),” “unexpected PPDU parameter (5),” or “invalid PPDU parameter value (6).” This counter wraps around upon overflow.
OSI/AS SCF Commands STATS SERVICE #L6 Command Total CPR/ARP PPDUs Received shows the total number of CPR-PPDUs and ARP-PPDUs that were received by this service. This counter wraps around upon overflow. Value 0 through 2147483647 Total CPR/ARP PPDUs Sent shows the total number of CPR-PPDUs and ARP-PPDUs that this service sent or attempted to send. This counter wraps around upon overflow.
OSI/AS SCF Commands STATS SERVICE #ACSE Command CPA PPDU Received shows the number of times the Presentation layer received a Connect Presentation Accept (CPA) PPDU. This counter wraps around upon overflow. Value 0 through 65535 STATS SERVICE #ACSE Command The format of the display for the STATS SERVICE #ACSE command is OSIAS Stats SERVICE \MARS.$TAS0.#ACSE Reset Time.... 20 Jun 1991, 18:23:19.300 Sample Time... 20 Jun 1991, 18:27:18.
OSI/AS SCF Commands STATS SERVICE #ACSE Command AARE (Rejected,Prov) APDUs Received shows the number of times the ACSE service received an AARE-APDU with a result field of either “rejected permanent (1)” or “rejected temporary (2)” and a result source field of ACSE service provider. This counter wraps around upon overflow. Value 0 through 65535 AARE (Rejected,Prov) APDUs Received Threshold shows a threshold value that the ACSE service compares to the counter “AARE (Rejected, Prov) APDUs Recv.
OSI/AS SCF Commands STATS SERVICE #ACSE Command ABRT (Provider) APDUs Sent shows the number of times that the ACSE service sent or attempted to send an ABRT-APDU with an abort-source field value of “ACSE service provider (1).” This counter wraps around upon overflow. Value 0 through 65535 ABRT (Provider) APDUs Sent Threshold shows a threshold value that the ACSE service compares to the counter “ABRT (Provider) APDUs Sent.
OSI/AS SCF Commands STATS SERVICE #ACSE Command AARQ APDUs Received shows the number of times the ACSE service receiver an ACSE Associate Request (AARQ) APDU. This counter wraps around upon overflow. Value 0 through 65535 AARQ APDUs Sent shows the number of times the ACSE service sent, or attempted to send, an ACSE Associate Request (AARQ) APDU. This counter wraps around upon overflow.
OSI/AS SCF Commands STATS SU Command RLRE (accepted) APDUs Sent shows the number of times the ACSE service sent, or attempted to send, a Release Response Accept (RLRE+) APDU. This counter wraps around upon overflow. Value 0 through 65535 RLRE (rejected)APDUs Received shows the number of times the ACSE service received a Release Response Reject (RLRE) APDU. This counter wraps around upon overflow.
OSI/AS SCF Commands STATS SU Command Total SPDUs Received shows the number of session protocol data units received by this SU. Value 0 through 2147483647 Total SPDUs Sent shows the number of session protocol data units sent by this SU. Value 0 through 2147483647 Total SPDU Bytes Received shows the total number of bytes, both of user data and of session protocol data, received by this SU.
OSI/AS SCF Commands STATS SUBSYS Command STATS SUBSYS Command The format of the display for the STATS SUBSYS command is OSIAS Stats SUBSYS \MARS.$OSIM Reset Time..... 26 Jan 1990, 11:45:20.140 Sample Time.... 26 Jan 1990, 11:45:20.140 Configuration: TAPS Process... TSP Process.... NSP Process.... APPL Entry..... TSEL Entry..... NSAP Entry..... SNPA Entry..... L3Profile...... L4Profile...... L5Profile...... Current 0 0 0 0 0 0 0 0 0 1 MaximumEver 0 0 0 0 0 0 0 0 0 1 Register Requests: Received.......
OSI/AS SCF Commands Considerations for the STATS Command Failure Reasons shows the number of times that register requests might have failed in each of the listed categories. Considerations for the STATS Command The considerations contain information about command use that should be read before studying the command syntax in too much detail. All Objects • The RESET option instructs the process to reset all counters after returning the current values.
OSI/AS SCF Commands Examples of the STATS Command SU Object STATS SU $TAPS.* STATS SU $TAPS.#Z000003 STATS SU $TAPS.
OSI/AS SCF Commands STATUS Command STATUS Command Use the STATUS command to display current status information about an object, such as the dynamic state and the last error (SU objects only). STATUS is a nonsensitive command.
OSI/AS SCF Commands STATUS PROCESS Command OwnerID shows the owner ID for this process. StopOpens shows whether a STOPOPENS command is in effect for this process. Opens shows the total number of opens for this process. This field is not displayed for NSP processes. Trace shows whether or not a TRACE command is in effect for this process. The format of the display for the STATUS PROCESS command with the DETAIL option is OSIAS Detailed Status PROCESS \MARS.$TAP1 Creation Time...... State..............
OSI/AS SCF Commands STATUS SU Command StopOpens shows whether a STOPOPENS command is in effect for this process. Opens shows the number of opens for this process. OSI Internal Name shows the OSI internal name associated with this process. This field appears in the display only when the TAPS process is specified as process-name. Trace shows whether or not a TRACE command is in effect for this process. Trace Mask shows the current trace mask (not displayed when TRACE is OFF).
OSI/AS SCF Commands STATUS SU Command Error-Sub shows the last detected error subcode for this object. L5-PM-State shows the abbreviated name of the current-session protocol state as defined by the session standard. See ISO 8327 for the possible values.
OSI/AS SCF Commands STATUS SU Command The format of the display for the STATUS SU command with the DETAIL option is OSIAS Detailed Status SU \MARS.$TAPS.#Z000000 State............... Opens............... Opener.............. Opener Id........... Loopback............ DeleteTime.......... L4 or Loopback SU... Last Error.......... Last Error Subcode.. Last Error Source... Last TSP Error...... Last TSP State...... Last TSP SubState... STARTED 1 \SYSTEM.$PROG 165,17 OFF -1 (Static SU) \SYSTEM.$TSP.
OSI/AS SCF Commands STATUS SU Command PSel.............. SSel.............. TSel.............. NSAP.............. 0123 0123 0123 0123 4567 8901 2345 4567 89AB CDEF 4567 45 Called Address: (REMOTE) Application Name.. your-application AETitle: AETitle Format. 2 AEQualifier.... ABCD 1234 APTitle........ { 1 7 99 132 } PSel.............. SSel.............. TSel.............. NSAP.............. 0123 0123 45 1111 0143 25 Responding Address: (REMOTE) Application Name..
OSI/AS SCF Commands STATUS SU Command L4 or LoopBack Su shows either the name of the transport subdevice, or when there is a connection with loopback in effect, shows the name of the remote connection endpoint TAPS SU, which resides in the same TAPS process as the SU being displayed. Last Error shows the last detected error code for this object. Last Error Subcode shows the last detected error subcode for this object. This field is only displayed when the Last Error field is nonzero.
OSI/AS SCF Commands STATUS SU Command DisconnTimer shows the session disconnect and abort timer value. Expedited shows whether the transport expedited data transfer service is supported. InSegmentation shows whether segmentation for inbound SSDUs is selected. OutSegmentation shows whether segmentation for outbound SSDUs is selected. InMaxTSDUSize shows the negotiated maximum size of inbound TSDUs. OutMaxTSDUSize shows the negotiated maximum size of outbound TSDUs.
OSI/AS SCF Commands STATUS SU Command L6 Normal Mode shows, if True, that normal mode is being used or if False, that X.410-1984 mode is used. This field is only displayed for L6 or ASCE connections. See ISO 8323 for the possible values. ACSE Protocol State shows the current ACSE protocol state. For a list of possible values, see the ACSE protocol standard. This field is only displayed for ASCE connections. See ISO 8650 for the possible values.
OSI/AS SCF Commands STATUS SUBSYS Command SSEL shows the session service selector for the application entry name. TSEL shows the transport service selector for the application entry name. NSAP shows the NSAP address for the application entry name. Note. About this display: For token settings, the Data token information is displayed on the same line as the other token information.
OSI/AS SCF Commands STATUS SUBSYS Command State shows the state of the OSI/AS subsystem. NSPs shows the number of NSP processes configured and the number started. TSPs shows the number of TSP processes configured and the number started. TAPS shows the number of TAPS processes configured and the number started. MIB Status shows the current status of the Management Information Base. The format of the display for the STATUS SUBSYS command with the DETAIL option is OSIAS Detailed Status SUBSYS \MARS.
OSI/AS SCF Commands Considerations for the STATUS Command MIB Status shows the current status of the Management Information Base. NSPs Configured shows the number of NSP processes currently configured. NSPs Started shows the number of NSP processes currently started. TSPs Configured shows the number of TSP processes currently configured. TSPs Started shows the number of TSP processes currently started. TAPS Configured shows the number of TAPS processes currently configured.
OSI/AS SCF Commands Examples of the STATUS Command Examples of the STATUS Command The examples are designed to show correct ways of specifying command syntax. PROCESS Object STATUS STATUS STATUS STATUS PROCESS PROCESS PROCESS PROCESS $OSIM $OSIM, DETAIL $OSIM.#TAPS.TAP1 $OSIM.#TAPS.*,DETAIL SU Object STATUS SU $TAPS.#Z000003 STATUS SU $TAPS.#Z000003, DETAIL STATUS SU $TAPS.
OSI/AS SCF Commands STOP Command STOP Command Use the STOP command to terminate the activity of objects in a normal manner. The STOP command prevents the object from accepting further service requests. Upon successful completion of the STOP command, configured objects (PROCESS objects) are left in the STOPPED state (still configured in the Management Information Base). Nonconfigured objects (SU objects) are deleted. STOP is a sensitive command.
OSI/AS SCF Commands Examples of the STOP Command SU Object • • Wildcards are supported for the STOP SU command. Use the STOP SU command to remove inactive static SUs from the specified TAPS process. SUs that are open, for example, those SUs handling requests from APS applications, are not affected by STOP SU. To see which SUs have openers, use the LISTOPENS SU $process.* command. To stop all SUs, including active SUs, use the ABORT SU command. To handle TSP SUs, see the OSI/TS SCF Reference Manual.
OSI/AS SCF Commands STOPOPENS Command STOPOPENS Command Use the STOPOPENS command to prevent further file-system opens from being issued to an object without disrupting any of the current activity. STOPOPENS is a sensitive command.
OSI/AS SCF Commands Examples of the STOPOPENS Command Examples of the STOPOPENS Command The examples are designed to show correct ways of specifying command syntax. PROCESS Object STOPOPENS PROCESS $TAPS STOPOPENS PROCESS $OSIM.#TAPS.TAPS1 STOPOPENS PROCESS $OSIM.#TAPS.
OSI/AS SCF Commands SUSPEND Command SUSPEND Command Use the SUSPEND command to restrict the use of connections to and from the specified process. An application cannot use a suspended process. However, if an application is already using a process when the SUSPEND command is issued to that process, the SUSPEND command is rejected. The SUSPEND command can be used only on a process that is in the STARTED state (but not in use).
OSI/AS SCF Commands Examples of the SUSPEND Command Examples of the SUSPEND Command The examples are designed to show correct ways of specifying command syntax. PROCESS Object SUSPEND SUSPEND SUSPEND SUSPEND PROCESS PROCESS PROCESS PROCESS $TAPS $OSIM.#TAPS.TAPS1 $OSIM.#TSP.TSP1 $OSIM.*.
OSI/AS SCF Commands TRACE Command TRACE Command Use the TRACE command to collect trace information. Issue the TRACE command (without the STOP option) to specify trace options and start tracing. While tracing is on, the TRACE command can be issued (without the STOP option) to modify COUNT, RECSIZE, or any of the SELECT specifications. Issue the TRACE command with the STOP option to stop tracing. To examine trace files, use the formatter available with the PTrace program.
OSI/AS SCF Commands TRACE Command Syntax COUNT count specifies the number of trace records to be captured. count is an integer in the range -1 through 32767. If COUNT is omitted or if count equals -1, records are accumulated until the trace is stopped. The default is -1. The trace will stop when the trace file reaches EOF, unless WRAP has been specified. NOCOLL indicates that the trace collector process should not be initiated.
OSI/AS SCF Commands TRACE Command Syntax SELECT select-spec specifies which records are collected and written to the trace file. Records are identified by trace record type, using the descriptions that appear in PTrace display formats. The select-spec is one or more of the following specifications: { keyword } { ( keyword [ , keyword ]...
OSI/AS SCF Commands TRACE Command Syntax MEM specifies tracing of memory allocation and deallocation. This includes the following trace records: Allocate Deallocate This information is primarily for use by Compaq analysts in troubleshooting the Compaq OSI/AS software. MSG specifies tracing of the file-system requests and responses.
OSI/AS SCF Commands TRACE Command Syntax ACSE specifies tracing of all ACSE trace information. This includes the following trace records: ACSE USER—ACSE Reply ACSE USER—ACSE Event ACSE USER—ACSE Request ACSE PROV—L6 Event ACSE PROV—ACSE Reply ACSE PROV—L6 Request ACSE—ACSE Error Report If ASCE is specified, it includes all the information from the ACSEPROV, ACSESM, and ACSEUSER keywords. ACSEPROV specifies tracing of ACSE provider and error information.
OSI/AS SCF Commands TRACE Command Syntax L6 specifies tracing of all L6 trace information.
OSI/AS SCF Commands TRACE Command Syntax L6USER specifies tracing of L6 user primitives and error information. This includes the following trace records: L6 USER—L6 Event L6 USER—L6 Continuation Event L6 USER—L6 Abort Continuation Event L6 USER—L6 User Reply L6 USER—L6 Request L6 USER—L6 First Request L6 USER—L6 Multi Mid Request L6 USER—L6 Multi Last Request L6 USER—L6 Multi Abort Request L6—L6 Error Report L5 specifies tracing of all L5 trace information.
OSI/AS SCF Commands TRACE Command Syntax L5PROV specifies tracing of L5 provider and error information and L4 service information.
OSI/AS SCF Commands Considerations for the TRACE Command TO file-spec specifies the file to which trace information is to be written. The file might have been previously created as an unstructured file with file code 830. An old file is purged of data before the trace is initiated. If the file does not exist, SCF creates the file with an extent size of 100 pages for the primary extent and 20 pages for secondary extents. There are a maximum of 15 secondary extents for a maximum file size of 400 pages.
OSI/AS SCF Commands Examples of the TRACE Command If any of the following keywords are selected, specify a RECSIZE from 2,000 through 4,050 bytes: ALL (traces presentation and ACSE connections) ASN1 ACSE ACSEPROV ACSESM ACSEUSER L6 L6PROV L6SM L6USER Since it is not possible to specify RECSIZE greater than 4050 bytes, it may not be possible to use TRACE to unravel an ASN.1 problem involving large buffers of user data from an application.
OSI/AS SCF Commands VERSION Command VERSION Command Use the VERSION command to display the version level of the specified object. VERSION is a nonsensitive command. VERSION Command Syntax VERSION [ /OUT file-spec/ ] [ object-spec ] [ , DETAIL ] The object-spec is object-type object-name null PROCESS SUBSYS process-name process-name osi-mgr-name VERSION null Command The format of the display for the VERSION null command without the DETAIL option is VERSION \MARS.
OSI/AS SCF Commands VERSION PROCESS Command VERSION PROCESS Command The format of the display for the VERSION PROCESS command without the DETAIL option is VERSION PROCESS \MARS.$TAPS: OSI/AS - T9570C30 - 28NOV91 - 31OCT91 The format of the display for the VERSION PROCESS command with the DETAIL option is Detailed VERSION PROCESS \MARS.$TAPS SYSTEM \MARS OSI/AS - T9570C30 - 28NOV91 - 31OCT91 - 3.0.
OSI/AS SCF Commands Examples of the VERSION Command Examples of the VERSION Command The examples are designed to show correct ways of specifying command syntax.
OSI/AS SCF Commands Examples of the VERSION Command OSI/AS SCF Reference Manual—424121-001 2-238
3 OSI/AS Trace Facility This section contains the following topics: • • • • • • • • • • Introduction on this page Structure of the OSI/AS Processes on page 3-3 PTrace Commands on page 3-6 Trace Record Displays on page 3-22 Trace Record Formats on page 3-23 Shared Trace Records on page 3-25 ASN.
OSI/AS Trace Facility • Introduction OSI standards: Since OSI/AS implements several OSI International standards, the format, content and order of trace records in a trace file will reflect those standards. Depending on which trace records are being examined, knowledge of the structure and content of OSI PDUs is necessary to fully understand the contents of the trace file.
OSI/AS Trace Facility Structure of the OSI/AS Processes Structure of the OSI/AS Processes Figure 3-1 illustrates the architecture of a user application process and the OSI/AS subsystem processes (and lower layer processes) from the perspective of how tracing works. Figure 3-1.
OSI/AS Trace Facility How Trace Records Cross the OSI Layers Figure 3-2. TAPS Process Structure ACSE ASN.1 TAPS Presentation Session Support Procedures CDT 020.CDD The TAPS process consists of a set of OSI service layer code modules (ACSE, presentation, and session, and ASN.1), along with support procedures to handle I/O, shared service layer functions and routing between service layers. Each layer and some of the support procedures have their own trace capability.
OSI/AS Trace Facility How Trace Records Cross the OSI Layers Figure 3-3. How Trace Records Cross the OSI Layers ACSE User State Machine and Error ACSE ACSE Provider Presentation User State Machine and Error Presentation Presentation Provider Session User State Machine and Error Session Session Provider CDT 025.CDD Figure 3-3 shows how output from one service layer becomes the input to the service layer below.
OSI/AS Trace Facility PTrace Commands PTrace Commands This section describes the following PTrace commands that are interpreted specifically for the OSI/AS subsystem: • • • • • DETAIL Command on page 3-8 FILTER Command on page 3-8 HEX Command on page 3-15 SELECT Command on page 3-16 STATETABLES Command on page 3-21 Other commands that are generally supported by PTrace, such as the FROM and LOG commands, are not documented in this manual.
OSI/AS Trace Facility Running PTrace OUT [ filename ] designates the initial destination for PTrace display output for the session. This is the formatted file that you will be able to use for your problem diagnosis. If the OUT option is omitted, the output destination defaults to the output file of the TACL or SCF process through which PTrace is being initiated (usually a terminal). If the OUT option is specified and filename is omitted, PTrace output is discarded.
OSI/AS Trace Facility DETAIL Command DETAIL Command The DETAIL command controls the level of detail of the information displayed. Using DETAIL ON with the ACSE, L6, or L5 filters means that the display will include as much user data as is available in the trace record. Using DETAIL ON with other filter keys ensures that all the data that was saved in the trace record is displayed. If DETAIL is OFF, the display will contain only the first two lines of user data.
OSI/AS Trace Facility FILTER Command The filter-option is one or more of the following keywords: filter-option [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ HELP ] ? ] ALL ] RESET ] SU [ su-name ] ] MSGSU [ su-name ] ] [NO]BER ] [NO]ASN1DEC ] [NO]ASN1ENC ] [NO]ACSEINTERNALS ] ACSEPROV [ apdu-type [ , ... ] ] ] [NO]ACSESM ] ACSESU [ su-name ] ] [NO]ACSEUSER ] [NO]L6INTERNALS ] L6PROV [ ppdu-type [ , ... ] ] ] [NO]L6SM ] L6SU [ su-name ] ] [NO]L6USER ] [NO]L5INTERNALS ] L5PROV [ spdu-type [ , ...
OSI/AS Trace Facility FILTER Command RESET resets the filter-options to the default setting as follows: Filter ACSEPROV. L6PROV, L5PROV SU, ACSESU, L6SU, L5SU, L4SU ACSEUSER, L6USER, L5USER All other filters Value “all” “all” “on” “off” SU [ su-name ] displays the trace information for the specified SU. su-name is any valid ACSE, L6, L5, or L4 subdevice name. If you omit su-name, you select all ACSE, L6, L5, and L4 subdevices.
OSI/AS Trace Facility FILTER Command [NO]ASN1ENC specifies formatting of ASN.1 encoder trace information. This includes the following trace records: ASN.1—ACSE Encode ASN.1—L6 Encode NOASN1ENC suppresses the formatting of this information. The default is NOASN1ENC. [NO]ACSEINTERNALS specifies formatting of ACSE internal trace information. This includes the following trace record: ACSE—ACSE Error Report NOACSEINTERNALS suppresses the formatting of this information. The default is NOACSEINTERNALS.
OSI/AS Trace Facility FILTER Command [NO]ACSEUSER specifies formatting of ACSE user primitives trace information. This includes the following trace records: ACSE USER—ACSE Reply ACSE USER—ACSE Event ACSE USER—ACSE Request NOACSEUSER suppresses display of this information. The default is ACSEUSER. [NO]L6INTERNALS specifies formatting of L6 internal trace information. This includes the following trace record: L6—L6 Error Report NOL6INTERNALS suppresses the formatting of this information.
OSI/AS Trace Facility FILTER Command L6SU [ su-name ] specifies formatting of all L6 trace information for the specified SU. If you omit su-name, you select all SUs. The default is L6SU (select all presentation layer SUs). [NO]L6USER specifies formatting of L6 user primitives trace information.
OSI/AS Trace Facility FILTER Command If you omit spdu-type, you select all SPDUs. spdu-type is one of the following values: [ [ [ [ [ [ [ ACT ] CONNECT ] DATA ] ERROR ] RELEASE ] SYNC ] TOKEN ] The default is L5PROV (display all SPDUs). [NO]L5SM specifies formatting of L5 state machine trace information. This includes the following trace record: L5 SM—L5 State Machine NOL5SM suppresses the formatting of this information. The default is NOL5SM.
OSI/AS Trace Facility HEX Command Considerations for the FILTER Command The considerations contain information about command use that should be read before studying the command syntax in too much detail. • The default filter values should provide all the information you will need to debug your program. • You must select a trace file with the PTrace FROM command before setting filter options. • You cannot filter on events not included in the trace file options.
OSI/AS Trace Facility SELECT Command Considerations for the HEX Command The considerations contain information about command use that should be read before studying the command syntax in too much detail. • • • If the HEX command is not used, OFF is assumed. If HEX is specified without ON or OFF, ON is assumed. The RESET and FROM commands set HEX to OFF. SELECT Command The SELECT command establishes the selection criteria that control which trace records are to be displayed.
OSI/AS Trace Facility SELECT Command number is the numeric value that a keyword represents. The possible values are Value Corresponding keyword [7] DSM [0] MEM [9] MSG [2] NS [3] SYSMSG [29] ASN1 [28] ACSE [24] L6 [19] L5 See keyword descriptions for explanations of the values. keyword selects the information in the trace file that you want to format and display.
OSI/AS Trace Facility SELECT Command DSM specifies formatting of DSM requests. This includes the following trace records: Decode SPI Request Perform SPI Request This information is primarily for use by Compaq analysts in troubleshooting the Compaq OSI/AS software. MEM specifies formatting of memory allocation and deallocation. This includes the following trace records: Allocate Deallocate This information is primarily for use by Compaq analysts in troubleshooting the Compaq OSI/AS software.
OSI/AS Trace Facility SELECT Command ASN1 specifies formatting of Abstract Syntax Notation-1 (ASN.1) encoder and decoder trace information for both ACSE and L6 activity. This includes the following trace records: ASN.1—ACSE Decode ASN.1—ACSE Encode ASN.1—L6 Decode ASN.1—L6 Encode ACSE specifies formatting of all ACSE trace information.
OSI/AS Trace Facility SELECT Command L5 specifies formatting of all L5 trace information.
OSI/AS Trace Facility • STATETABLES Command The enumerated list of keywords (or the numeric values, if no trace file is currently open) is always displayed. Examples of the SELECT Command The examples are designed to show correct ways of specifying command syntax. Keyword Action SELECT ASCE selects all ACSE trace information. SELECT (ACSE, L6) selects all ACSE and L6 trace information. FILTER ALL selects all trace information. FILTER RESET resets the filters to the d4efault settings.
OSI/AS Trace Facility Trace Record Displays Trace Record Displays The rest of this section provides the following information: • • • Describes the format of the displays Tells you how to get help when you have problems Shows you samples of each type of trace record in the following order: ° Trace records common to both the OSI manager process and the TAPS processes: ° ° ° ° Trace records for TAPS ASN.
OSI/AS Trace Facility Getting Help Getting Help When using the SCF TRACE command to create a complete trace file that might be sent to Compaq for analysis, issue the SCF TRACE command with the default selectspec values (the default is ALL) to collect all information in the unformatted trace file. It is recommended that you send the unformatted trace file, rather than a formatted PTrace file. Follow the standard procedures at your site for contacting the appropriate support personnel.
OSI/AS Trace Facility Header Format Trace of shows the device type and subtype of the process that is traced. The device type and subtype identify the process that created the file. The following table identifies the device type and subtypes for the OSI manager and TAPS processes: Process Device Type Subtype OSI manager 55 1 TAPS 55 5 Ptrace Data File shows the file containing the trace data. Trace started shows the date and time that the trace was started.
OSI/AS Trace Facility Shared Trace Records DeltaTime shows the amount of time (in seconds) that has passed since the previous trace was captured. If the time reaches 999.999 or greater, then 999.999 is displayed. The deltatime is zero for the first record and for any record having a timestamp earlier than the previous record displayed. TraceRecordNumber shows the number of the trace record. Trace records are numbered sequentially beginning at 1.
OSI/AS Trace Facility Decode SPI Request State is an internally defined integer that represents the current step in the SPI-request decoding sequence.
OSI/AS Trace Facility Perform SPI Request Perform SPI Request This trace record is for Compaq internal use and tracks the internal processing of an SPI request and indicates that an SPI request has been received and is about to be sent to a service layer for action, for example, L5. 08:20:07.070 >000.000 #24 ADD SU $MAS0.#ZMF0020 Perform SPI Request (5003,21 ADD SU shows the SPI command that was issued. $MAS0 shows the TAPS process to which subdevice $ZMF0020 is to be added.
OSI/AS Trace Facility Deallocate Value Meaning Type of control block 64 SPI request n/a 107 Message MCB 109 Event ECB Len shows the length of memory allocation in bytes. From shows the type of memory organization from which memory has been allocated, where LIST and POOL are the possible values. Addr shows the buffer address where memory has been allocated. Count In List is the number of preallocated control blocks left in the list.
OSI/AS Trace Facility Request In Value Meaning Type of control block 3 Request RCB 4 Data DCB 5 Subdevice SUCB 64 SPI request n/a 107 Message MCB 109 Event ECB Len shows the length of memory deallocation in bytes. From shows the type of memory organization to which memory has been deallocated, where LIST and POOL are the possible values. Addr shows the buffer address where memory has been deallocated. Count In List is the number of preallocated control blocks left in the list.
OSI/AS Trace Facility Completion Read Count shows the number of bytes in the request buffer. This is the actual number of bytes received. Opener shows the ID of the process that originated the request message. Opened FN shows the file-system number associated with the request message. This is the file number that the requestor used to open this TAPS or OSI manager process.
OSI/AS Trace Facility IO Request . 08:20:07.080 >000.000 #28 Reply Receive Tag: 0 Sync ID: 46D Status: 0 Queued Reqs: 1 Length: 98 FE: 0 Receive Tag shows the message tag of the associated request message. Sync ID shows the sync ID of the associated request message. The file-system generates sync IDs. Sync IDs prevent duplication of requests in I/O operations. For further information on sync IDs, see the Guardian 90 Operating System Programmer’s Guide.
OSI/AS Trace Facility CLOSE Request Req Type shows the type of I/O request, where the following Guardian procedure values are possible: ReadUpdateX ReadX ReplyX WriteX WriteReadX Fn shows the file number on which the I/O request was initiated. Note, APS communicates with processes via file number 0. Tag shows the file-system tag associated with the I/O request. When an I/O completes, the file-system returns the tag which is then matched with list of outstanding I/Os.
OSI/AS Trace Facility OPEN Request Manual. The value of this field should always be zero. If the field contains a nonzero value, you may need to seek additional help. OPEN Request The following trace record is for Compaq internal use and is generated by the OSI manager or TAPS process immediately after it validates and processes an open systemmessage. 08:20:07.100 >000.000 #41 Reply Error: 0 OPEN Req Reply Error shows the file-system error returned to the process that issued the open systemmessage.
OSI/AS Trace Facility ASN.1 Trace Records Value Meaning Value Meaning -21 3270 device status -102 NEWPROCESS CREATE COMPLETION -22 Time signal -103 OPEN -23 Lock complete -104 CLOSE -24 Lock failed -105 BREAK -26 Process time signal -106 DEVICE INFO -28 SPI -110 NODE DOWN -30 OPEN -111 NODE UP -31‘ CLOSE -113 REMOTE CUP DOWN ASN.1 Trace Records These are the types and subtypes of TAPS ASN.1 trace records: Type Subtype ASN.1 ACSE Decode ASN.1 ACSE Encode ASN.
OSI/AS Trace Facility ASN.1—ACSE Encode Error Subcode shows either a null value or a description of the erroneous parameter. Protocol^Version shows the version number of the presentation layer protocol as specified in either the AARQ-APDU or the AARE-APDU. PCID shows the presentation context identifier. PDU Addr shows the address of the protocol data unit. PDU Len shows the length of the protocol data unit. ASN.1—ACSE Encode This trace record shows the result of encoding an ACSE PDU.
OSI/AS Trace Facility ASN.1—L6 Decode PCID shows the presentation context identifier. PDU Addr shows the address of the protocol data unit. PDU Len shows the length of the protocol data unit. ASN.1—L6 Decode This trace record shows the result of decoding an L6 PDU. A zero (0) or null error code and error subcode means that no error was detected. 08:20:07.700 >026.710 #104 TAPS ASN.1 ASN.1 L6 Decode Su Name #ZMF0020 Error = ZAPS^Err^Ok(0), Error Subcode = (0).
OSI/AS Trace Facility ASN.1—L6 Decode PDU Addr shows the address of the protocol data unit. PDU Len shows the length of the protocol data unit. Mode shows the mode parameter as specified in either the CPR-PPDU or the CPA-PPDU. Inbound Data State for DATA PDUs, indicates either “only” or “multi send.” Prov Reason shows the provider reason parameter of CPR-PPDUs. Abort Reason shows the abort reason parameter of ARP-PPDUs. Event Identifier shows the event identifier parameter of ARP-PPDUs.
OSI/AS Trace Facility ASN.1—L6 Encode Previous PCID is not applicable in this display. Residual Type shows the type of PDV list to be decoded. ASN.1—L6 Encode This trace record shows the result of encoding an L6 PDU. A zero (0) or null error code and error subcode means that no error was detected. 08:20:07.760 >000.000 #142 TAPS ASN.1 ASN.1 L6 Encode Su Name #ZMF0020 Error = ZAPS^Err^Ok(0), Error Subcode = (0).
OSI/AS Trace Facility ASN.1—L6 Encode PDU Len shows the length of the protocol data unit. Mode shows the mode parameter of CPR-PPDUs and CPA-PPDUs. Inbound Data State for DATA PDUs, indicates either “only” or “multi send.” Prov Reason shows the provider reason parameter of CPR-PPDUs. Abort Reason shows the abort reason parameter of ARP-PPDUs. Event Identifier shows the event identifier parameter of ARP-PPDUs. Nest Depth is not applicable in this display.
OSI/AS Trace Facility ACSE Trace Records Residual Type is not applicable in this display. ACSE Trace Records These are the types and subtypes of TAPS ACSE trace records: Type Subtype ACSE USER ACSE Reply ACSE USER ACSE Event ACSE USER ACSE Request ACSE PROV ACSE Reply ACSE PROV L6 Event ACSE PROV L6 Request ACSE ACSE Error Report ACSE SM ACSE State Machine ACSE USER—ACSE Reply This trace record shows the result of a previous request for ACSE service from an APS user.
OSI/AS Trace Facility ACSE USER—ACSE Event Status Code show the status code returned to the APS procedure. See the OSI/AS Programming Manual for descriptions of possible values. Error show the error returned to the APS procedure. See the OSI/AS Programming Manual for descriptions of possible values. Error Subcode show the error subcode returned to the APS procedure. See the OSI/AS Programming Manual for descriptions of possible values.
OSI/AS Trace Facility ACSE USER—ACSE Event 14:58:05.650 >000.000 #20 TAPS ACSE USER ACSE Event Su Name #Z000003 MCB Addr %H000A2DBE DCB Addr %H001B0BCE DCB Len 01490 Event Code 000002 (Connect Cnf) zcalling^ref.zlen = 0 .zval = zcalled^ref.zlen = 0 .zval = zcommon^ref.zlen = 0 .zval = zadditional^ref.zlen = 0 responding^addr: zpsap.zpsel.zlen = 2 000: D614 .zval = zpsap.zpsel.zc = V. zpsap.zssel.zlen = 2 000: D514 zpsap.zssel.zc = zpsap.ztsel.zlen = 1 000: D400 zpsap.ztsel.zc = U. T. zpsap.
OSI/AS Trace Facility ACSE USER—ACSE Event l6^context^def^result^list[1].zreason = no value l6^context^def^result^list[2].zresult = Accept l6^context^def^result^list[2].zts^name = { 2 1 1 } l6^context^def^result^list[2].zreason = no value l6^default^context^result = no value appl^context^name = { 1 0 8571 1 1 } user^data.hdr.znum^elements = 1 user^data.element[0].hdr.zlen = 50 .ztype = 1 .zpcid = 31 000: 2830 0201 03A0 2BA1 2955 0100 4501 0080 8082 0100 8302 (0... +!)U..E...........
OSI/AS Trace Facility ACSE USER—ACSE Request DCB Len an internal field that shows the length of the control block containing the event data. Event code shows which event (a primitive or error) is being queued. The possible values are Value Meaning 00001 Connect Ind 00002 Connect Cnf 00028 Release Ind 00030 User Abort Ind <..Event Detail..> shows all the parameters of the ISO indication or confirm primitive represented by the event. See the OSI/AS Programming Manual for parameter descriptions.
OSI/AS Trace Facility ACSE USER—ACSE Request 14:57:50.210 >000.000 #1 TAPS ACSE USER ACSE Request Su Name #Z000003 Request Addr %H000A2CD8 Request Tag %H0001F75C Request Len 03290 Request Code -000001 (Connect Req) zcalling^ref.zlen = 0 .zval = zcalled^ref.zlen = 0 .zval = zcommon^ref.zlen = 0 .zval = zadditional^ref.zlen = 0 calling^addr: zappl^name.zlen = 4 000: 4654 4D41 FTMA called^addr: zappl^name.zlen = 4 000: 4654 4D44 FTMD .zval = zappl^name.zc = zappl^name.
OSI/AS Trace Facility ACSE USER—ACSE Request { 1 0 8571 1 1 } user^data.hdr.znum^elements = 1 user^data.element[0].hdr.zlen = 70 .ztype = 1 000: 2844 0201 03A0 3FA0 3D80 0207 0308 8403 053F (D... ? =..............? 00C: 0085 0205 C086 0100 A707 4E05 0846 5441 4D2E ....@...'.N.(B{..V.FTAM. 018: 4A41 4544 0531 3233 3435 7107 7988 0101 JAED.12345q...jerry... ASN.
OSI/AS Trace Facility ACSE PROV—ACSE Reply Request code is one of the following requests that originated from the APS user: Value Meaning -32767 Attach Req -00001 Connect Req -00002 Connect Rsp -00028 Release Req -00029 Release Rsp -00030 User Abort Req <..Request Detail..> shows the parameters associated with an APS procedure call. See the OSI/AS Programming Manual for parameter descriptions. ACSE PROV—ACSE Reply This trace record is generated when ACSE receives a reply to an L6 Request.
OSI/AS Trace Facility ACSE PROV—L6 Event Error shows the error returned to the APS procedure. See the OSI/AS Programming Manual for descriptions of possible values. Error Subcode shows the error subcode returned to the APS procedure. See the OSI/AS Programming Manual for descriptions of possible values. ACSE PROV—L6 Event The record is generated when ACSE receives an event (incoming indication or confirm) from L6. Most events processed by L6 are queued for APS without passing through ACSE.
OSI/AS Trace Facility ACSE PROV—L6 Request SU Name shows the name by which APS knows this connection. MCB Addr an internal field that shows the address of the TAPS internal Message Control Block. The data associated with the event is in the DCB pointed to by the MCB. DCB Addr an internal field that shows the address of the buffer holding the event data. DCB Len an internal field that shows the length of the control block containing the event data.
OSI/AS Trace Facility ACSE PROV—L6 Request 08:20:07.420 >000.000 #54 TAPS ACSE PROV L6 Request Su Name #ZMF0021 MCB Addr %H000A5E9E MCB Tag %H00011268 DCB Addr %H001AE0FE Request Len 03680 Request Code -000001 (Connect Req) zcalling^ref.zlen = 2 .zval = 000: 0304 .. zcalled^ref.zlen = 4 000: 0708 090A .zval = .... zcommon^ref.zlen = 6 000: 0B0C 0D0E .zval = 0F10 zadditional^ref.zlen = 0 calling^addr: zappl^name.zlen = 4 000: 4D46 3130 zpsap.zpsel.zlen = 0 called^addr: zappl^name.
OSI/AS Trace Facility ACSE—ACSE Error Report MCB Addr an internal field that shows the address of the control block that contains the DCB address. MCB Tag an internal field that is used to match requests with corresponding replies. DCB Addr an internal field that shows the address of the Data Control Block that contains the Compaq internal request or response primitive structure and header information. Request Len an internal field that shows the length of the primitive structure.
OSI/AS Trace Facility ACSE SM—ACSE State Machine Subtype ACSE Error Report SU Name shows the name by which APS knows this connection. Status Code show the status code returned to the APS procedure. See the OSI/AS Programming Manual for descriptions of possible values. Error shows the error returned to the APS procedure. See the OSI/AS Programming Manual for descriptions of possible values. Error Subcode shows the error subcode returned to the APS procedure.
OSI/AS Trace Facility L6 Trace Records State shows either the current state machine state (possible values are described in ISO 8650), or an internal intermediate state (defined to OSI/AS). Event an internal field that shows the event that caused the state machine to be called, either an internal value or a value described in ISO 8650. Action an internal field that shows the action taken as a result of the state machine being called.
OSI/AS Trace Facility L6 USER—L6 Event L6 USER—L6 Event This trace record is generated when L6 is about to queue an event (incoming indication or confirm) for dispatch to ACSE or an APS user. 08:20:08.010 >000.000 #190 TAPS L6 USER L6 Event Su Name #ZMF0020 MCB Addr %H000A5F56 DCB Addr %H001C6312 DCB Len 00130 Event Code 00020 (Activity Start Ind) Activity id: 000: 0000 0000 0000 user^data.hdr.znum^elements = 1 user^data.element[0].hdr.zlen = 5 .ztype = 1 .zpcid = ......
OSI/AS Trace Facility L6 USER—L6 Continuation Event Value Meaning Value Meaning 00010 Control Give Ind 00026 Activity End Ind 00012 Sync Minor Ind (Ack Requested) 00027 Activity End Cnf 00013 Sync Minor Cnf 00028 Release Ind 00014 Sync Major Ind 00029 Release Cnf 00015 Sync Major Cnf 00030 User Abort Ind 00016 Resynchronize Ind <..Event Detail..> shows all the parameters of the ISO indication or confirm primitive represented by the event.
OSI/AS Trace Facility L6 USER—L6 Abort Continuation Event DCB Len an internal field that shows the length of the control block containing the event data. <..user^data..> shows an APS user data element structure. L6 USER—L6 Abort Continuation Event This record is generated when L6 is about to queue an abort continuation data event for the APS user. It indicates that the stream of continuation events is being abnormally terminated.
OSI/AS Trace Facility L6 USER—L6 Request Subtype L6 User Reply SU Name shows the name by which APS knows this connection. Reply Addr an internal field that shows the address of the buffer controlling the original user request. Request Tag an internal field that shows the Request Tag associated with the request by APS. Status Code shows the status code returned to the APS procedure. See the OSI/AS Programming Manual for descriptions of possible values.
OSI/AS Trace Facility L6 USER—L6 Request 14:57:50.210 >000.000 #5 TAPS L6 USER L6 Request Su Name #Z000003 Request Addr %H000A2CD8 Request Tag %H0001026C Request Len 03738 Request Code -00001 (Connect Req) zcalling^ref.zlen = 0 .zval = zcalled^ref.zlen = 0 .zval = zcommon^ref.zlen = 0 .zval = zadditional^ref.zlen = 0 calling^addr: zappl^name.zlen = 4 000: 4654 4D41 FTMA zpsap.zpsel.zlen = 2 000: A612 &. called^addr: zappl^name.zlen = 4 000: 4654 4D44 FTMD zpsap.zpsel.zlen = 2 000: D614 V. .
OSI/AS Trace Facility L6 USER—L6 Request { 2 1 1 } l6^context^def^list[2].zpc^id = 31 l6^context^def^list[2].zas^name = { 2 2 1 0 1 } l6^context^def^list[2].zts^name[0] = { 2 1 1 } l6^default^context^name.zas^name = { 1 0 8571 2 3 } l6^default^context^name.zts^name = { 2 1 1 } mode = normal user^data.hdr.znum^elements = 2 user^data.element[0].hdr.zlen = 17 .ztype = 1 .zpcid = 31 000: 6055 8002 0780 A107 0605 28C2 7B01 01BE 4600 `U....!...(B{..>F user^data.element[1].hdr.zlen = 70 .ztype = 1 .
OSI/AS Trace Facility L6 USER—L6 Request Subtype L6 Request SU Name shows the name by which APS knows this connection. Request Addr an internal field that shows the address of the buffer controlling the request. Request Tag an internal field that shows the Request Tag assigned to the request by APS. Request Len an internal field that shows the length of the request primitive.
OSI/AS Trace Facility L6 USER—L6 First Request L6 USER—L6 First Request This trace record is generated immediately after the first of a series of data requests (Request Code -00003) or typed data requests (Request Code -00005) is received from the APS user. A series of such records consists of: L6 First Request L6 Multi Mid Request (zero or many) L6 Multi Last Request or L6 Multi Abort Request No other L6 Requests can be handled until the series is complete or aborted.
OSI/AS Trace Facility L6 USER—L6 Multi Mid Request Value Meaning -00003 Data Req -00005 Typed Date Req <..Request Detail..> shows the parameters associated with an APS procedure call. See the OSI/AS Programming Manual for parameter descriptions. L6 USER—L6 Multi Mid Request This trace record is generated immediately after L6 receives a series of data requests (Request Code -00003) or typed data requests (Request Code -00005) from the APS user.
OSI/AS Trace Facility L6 USER—L6 Multi Last Request Value Meaning -00003 Data Req -00005 Typed Date Req <..Request Detail..> shows the parameters associated with an APS procedure call. See the OSI/AS Programming Manual for parameter descriptions. L6 USER—L6 Multi Last Request This trace record is the last of a series of data requests (Request Code -00003) or typed data requests (Request Code -00005) from the APS user. 02/06/91 12:17:14.096959 >000.
OSI/AS Trace Facility L6 USER—L6 Multi Abort Request <..Request Detail..> shows the parameters associated with an APS procedure call. See the OSI/AS Programming Manual for parameter descriptions. L6 USER—L6 Multi Abort Request This trace record is generated when a multi send sequence of L6 requests is aborted by the APS user. This record will not contain user data elements. 02/06/91 12:17:14.096959 >000.
OSI/AS Trace Facility L6 PROV—L5 Event 08:20:08.080 >000.000 #225 TAPS L6 PROV L5 Event Su Name #ZMF0020 MCB Addr %H000A5F84 DCB Addr %H001C6312 DCB Len 00088 Event Code 00022 (Activity Interrupt Ind) Reason = receiving ability jeopardized user^data.hdr.znum^elements = 1 user^data.element[0].hdr.zlen = 14 .ztype = 1 .zpcid = 0 Subtype L5 Event SU Name shows the name by which APS knows this connection. MCB Addr an internal field that shows the address of the TAPS internal Message Control Block.
OSI/AS Trace Facility L6 PROV—L5 Continue Event Value Meaning Value Meaning 00014 Sync Major Ind 00029 Release Cnf 00015 Sync Major Cnf 00030 User Abort Ind 00016 Resynchronize Ind <..Event Detail..> shows all the parameters of the ISO indication or confirm primitive represented by the event. See the OSI/AS Programming Manual for parameter descriptions. L6 PROV—L5 Continue Event This trace record is generated when L6 receives a continuation data indication event from L5.
OSI/AS Trace Facility L6 PROV—L5 Request 08:20:07.760 >000.000 #144 TAPS L6 PROV L5 Request Su Name #ZMF0020 MCB Addr %H000A5E42 MCB Tag %H000116C4 DCB Addr %H001B571A Request Len 01640 Request Code -00002 (Connect Rsp) zcalling^ref.zlen = 3 .zval = 000: 0405 0600 ... zcalled^ref.zlen = 3 000: 0607 0800 ... .zval = zcommon^ref.zlen = 11 .zval = 000: 1011 1213 1415 1617 ........... zadditional^ref.zlen = 1 .zval = 000: 0800 responding^addr: zappl^name.zlen = 3 000: 4D46 3000 1819 . zappl^name.
OSI/AS Trace Facility L6 PROV—L5 First Request Request Len an internal field that shows the length of the primitive structure.
OSI/AS Trace Facility L6 PROV—L5 First Request This example shows concatenated tokens which would not be present with a typed data request. It also shows a single user data element. 02/06/91 12:17:14.066443 >000.000789 #156 L5 First Request Su Name #ZMF000B MCB Addr %H000AD6A6 MCB Tag %H0001F324 DCB Addr %H001C51AE Request Len 00060 Request Code -00003 (Data Req) --- Concatenation Tokens --zrelease = novalue zdata = novalue zminorsync = novalue zmajorsync = novalue ---------------------------user^data.
OSI/AS Trace Facility L6 PROV—L5 Continue Mid Request L6 PROV—L5 Continue Mid Request This trace record is generated when L6 is about to make a request for L5 service. The record indicates the continuation of a series of data requests that began with an L6 PROV—L5 First Request. 02/06/91 12:17:14.097430 >000.000471 #186 L5 Continue Mid Request Su Name #ZMF000B MCB Addr %H000AD702 MCB Tag %H0001F4C8 DCB Addr %H001CCEEA Request Len 00050 Request Code -00003 (Data Req) user^data.hdr.
OSI/AS Trace Facility L6 PROV—L5 Continue Last Request L6 PROV—L5 Continue Last Request This trace record is generated when L6 is about to make a request for L5 service. The record indicates the continuation of a series of data requests that began with an L6 PROV—L5 First Request. This record will contain one or more user data elements. 02/06/91 12:17:14.097430 >000.
OSI/AS Trace Facility L6 PROV—L5 Continue Abort Request L6 PROV—L5 Continue Abort Request This trace record is generated when the user aborts a sequence of L5 requests. This record will not contain any user data elements. 02/06/91 12:17:14.097430 >000.000471 #186 L5 Continue Abort Request Su Name #ZMF000B MCB Addr %H000AD702 MCB Tag %H0001F4C8 DCB Addr %H001CCEEA Request Len 00000 Request Code -00003 (Data Req) TAPS L6 PROV Subtype L5 Continue Abort Request.
OSI/AS Trace Facility L6—L6 Error Report 08:20:07.190 >000.010 #65 TAPS L6 PROV L6 Prov Reply Su Name #ZMF0020 Reply Addr %H000A5DE6 Request Tag %H000116C4 Status Code = ZAPS^Val^Status^Ok (0) Error = ZAPS^Err^Ok(0), Error Subcode = (0). Subtype L6 Provider Reply. SU Name shows the name by which APS knows this connection. Reply Addr an internal field that shows the address of the buffer controlling the original user request.
OSI/AS Trace Facility L6 SM—L6 State Machine SU Name shows the name by which APS knows this connection. Status Code shows the status code returned to the APS procedure. See the OSI/AS Programming Manual for descriptions of possible values. Error shows the error returned to the APS procedure. See the OSI/AS Programming Manual for descriptions of possible values. Error Subcode shows the error subcode returned to the APS procedure. See the OSI/AS Programming Manual for descriptions of possible values.
OSI/AS Trace Facility L5 Trace Records Request ID an internal field that shows the address of the buffer that controls the user request that inspired the state machine call. When dealing with an event from transport, this value is often null (%H0000000). State shows either the current state machine state (possible values are described in ISO 8823), or an internal intermediate state (defined to OSI/AS).
OSI/AS Trace Facility L5 USER—L5 Event Type Subtype L5PROV L5 I/O Completion L5PROV L5 I/O Completion Continuation L5PROV L5 Send TSDU L5PROV L5 Send TSDU Continuation L5PROV L5 Start Timer L5PROV L5 Cancel Timer L5PROV L5 Discard Session Resources L5 L5 Error Report L5SM L5 State Machine L5 USER—L5 Event This trace record is generated when L5 is about to queue an event (incoming indication or confirm) for dispatch to L6 or an APS user.
OSI/AS Trace Facility L5 USER—L5 Event 08:20:07.700 >000.070 #100 TAPS L5 USER L5 Event Su Name #ZMF0020 Session ID 84 MCB Addr %H000A5E9E DCB Addr %H001C6312 DCB Len 03925 Event Code 00001 (Connect Ind) zcalling^ref.zlen = 2 .zval = 000: 0304 zcalled^ref.zlen = 0 .zval = zcommon^ref.zlen = 6 000: 0B0C 0D0E .zval = 0F10 zadditional^ref.zlen = 0 calling^addr: zpsap.zpsel.zlen = 0 zpsap.zpsel.zc = zpsap.zssel.zc = zpsap.ztsel.zlen = 0 zpsap.ztsel.zc = S 0 called^addr: zpsap.zpsel.zlen = 0 zpsap.
OSI/AS Trace Facility L5 USER—L5 Continuation Event MCB Addr an internal field that shows the address of the TAPS internal Message Control Block. The data associated with the event is in the DCB pointed to by the MCB. DCB Addr an internal field that shows the address of the buffer holding the event data. DCB Len an internal field that shows the length of the control block containing the event primitive. Event code shows which event (a primitive or error) is being sent.
OSI/AS Trace Facility L5 USER—L5 Abort Continuation Event 02/06/91 12:18:44.007639 >000.001958 #218 L5 Continuation Event Su Name #ZMF000A Session ID TAPS L5 USER 12 Subtype L5 Continuation Event SU Name shows the name by which APS knows this connection. Session ID an internal field that shows a sequence number that is assigned to the connection by this TAPS process.
OSI/AS Trace Facility L5 USER—L5 Request 08:20:07.190 >000.010 #59 TAPS L5 USER L5 Reply Su Name #ZMF0020 Session ID 84 Reply Addr %H000A5DE6 Request Tag %H000116C4 Status Code = ZAPS^Val^Status^Ok (0) Error = ZAPS^Err^Ok(0), Error Subcode = (0). Subtype L5 Reply SU Name shows the name by which APS knows this connection. Session ID an internal field that shows a sequence number that is assigned to the connection by this TAPS process.
OSI/AS Trace Facility L5 USER—L5 Request 08:20:09.350 >000.000 #984 TAPS L5 USER L5 Request Su Name #ZMF0020 Session ID 84 Request Addr %H000A67F6 Request Tag %H0001F5F4 Request Len 00524 Request Code -00017 (Resynchronize Rsp) --- Concatenation Tokens --zrelease = novalue zdata = novalue zminorsync = novalue zmajorsync = novalue ---------------------------Serial number = 3 zrelease = notavailable zdata = notavailable zminorsync = notowned zmajorsync = notowned user^data.hdr.znum^elements = 2 user^data.
OSI/AS Trace Facility L5 USER—L5 First Request Value Meaning Value Meaning -00007 Capability Data Req -00023 Activity Interrupt Rsp -00008 Token Give Rsp -00024 Activity Discard Req -00009 Token Please Req -00025 Activity Discard Rsp -00010 Control Give Req -00026 Activity End Req -00011 Sync Minor Req -00027 Activity End Rsp -00013 Sync Minor Rsp -00028 Release Req -00014 Sync Major Req -00029 Release Rsp -00015 Sync Major Rsp -00030 User Abort Req <..Request Detail..
OSI/AS Trace Facility L5 USER—L5 Multi Mid Request SU Name shows the name by which APS knows this connection. Session ID an internal field that shows a sequence number that is assigned to the connection by this TAPS process. Request Addr an internal field that shows the address of the buffer controlling the request. Request Tag an internal field that shows the Request Tag assigned to the request by APS. Request Len shows the length of the request.
OSI/AS Trace Facility L5 USER—L5 Multi Last Request SU Name shows the name by which APS knows this connection. Session ID an internal field that shows a sequence number that is assigned to the connection by this TAPS process. Request Addr an internal field that shows the address of the buffer controlling the request. Request Tag an internal field that shows the Request Tag assigned to the request by APS. Request Len shows the length of the request.
OSI/AS Trace Facility L5 USER—L5 Multi Abort Request SU Name shows the name by which APS knows this connection. Session ID an internal field that shows a sequence number that is assigned to the connection by this TAPS process. Request Addr an internal field that shows the address of the buffer controlling the request. Request Tag an internal field that shows the Request Tag assigned to the request by APS. Request Len shows the length of the request.
OSI/AS Trace Facility L5 PROV—L5 Post Transport Read Session ID an internal field that shows a sequence number that is assigned to the connection by this TAPS process. Request Addr an internal field that shows the address of the buffer controlling the request. Request Tag an internal field that shows the Request Tag assigned to the request by APS. Request Len shows the length of the request.
OSI/AS Trace Facility L5 PROV—L5 Issue Read Read Count shows the maximum number of bytes to be read from transport. Session posts an initial read of 300 bytes when it does not know whether transport has data to return. If this initial read is returned with a “more data to follow” completion, the next reads posted will be for 1,500 bytes. Reads of 1,500 bytes are repeated until the whole transport TSDU has been read.
OSI/AS Trace Facility L5 PROV—L5 Issue Transport Connect FS Error shows the Guardian file-system error returned initiating read. L5 PROV—L5 Issue Transport Connect This trace record is generated just before session issues a transport connect request. It is the result of an APS user procedure call to APS_ASSOC_CONNECTREQ_. 08:20:07.420 >000.
OSI/AS Trace Facility L5 PROV—L5 Issue Writeread SU Name shows the name by which APS knows this connection. Session ID an internal field that shows a sequence number that is assigned to the connection by this TAPS process. Request ID an internal field that shows the address of the buffer that controls the user request that inspired the attach call. MCW an internal field that shows the Message Control Word (MCW). The MCW tells OSI/TS to issue a transport attach (which is a value of %H8000).
OSI/AS Trace Facility L5 PROV—L5 Issue Transport Disconnect Subtype L5 Issue Writeread SU Name shows the name by which APS knows this connection. File ID an internal field that shows the TAPS file control block ID. Tag an internal field that shows the type of writeread being initialized. The possible values are Value Meaning 1 attach 2 connect 7 loopback connection 12 get L4 status DCB Addr an internal field that shows the address of the control block that contains the writeread buffer.
OSI/AS Trace Facility L5 PROV—L5 Issue Write Subtype L5 Issue Transport Disconnect SU Name shows the name by which APS knows this connection. Session ID an internal field that shows a sequence number that is assigned to the connection by this TAPS process. Request ID an internal field that shows the address of the buffer that controls the user request that caused the disconnect call. If the disconnect was generated by the local session service provider, this field contains a null address (%H80000000).
OSI/AS Trace Facility L5 PROV—L5 Issue Write Expedited Tag an internal field that shows the type of write being initialized. The possible values are Value Meaning 3 disconnect 6 write 9 loopback disconnect 11 loopback write DCB Addr an internal field that shows the address of the buffer containing the data being written to a transport subdevice. Write Count shows the number of bytes written. FS Error shows the Guardian file-system error returned initiating the write.
OSI/AS Trace Facility L5 PROV—L5 I/O Completion Session ID an internal field that shows a sequence number that is assigned to the connection by this TAPS process. File ID an internal field that shows the TAPS file control block ID. DCB Addr shows the address of the buffer containing the data being written to a transport subdevice. FS Error shows the Guardian file-system error returned initiating the write.
OSI/AS Trace Facility L5 PROV—L5 I/O Completion Session ID an internal field that shows a sequence number that is assigned to the connection by this TAPS process. File ID an internal field that shows the TAPS file control block ID. Tag an internal field that shows the type of I/O operation that is completing.
OSI/AS Trace Facility L5 PROV—L5 I/O Completion Continuation Value Meaning %H0001 more-data Note: If this is a read completion and if the incoming TSDU contains part of a DT or TD SPDU, the TSDU data will be sent to the session service user in fragments as it is read from transport. If the TSDU contains a different type of SPDU, the whole SPDU will be read in and assembled before being passed to the session service user. %H0001 is also set when writing part of a larger TSDU.
OSI/AS Trace Facility L5 PROV—L5 Send TSDU Value Meaning 5 read 6 write 10 loopback read 11 loopback write DCB Addr an internal field that shows the address of the I/O buffer that just completed. Count Transferred shows the number of bytes written or read. FS Error shows the Completion Guardian file-system error. MCW shows the Message Control Word (MCW). The MCW is in the first word of the data buffer returned by transport.
OSI/AS Trace Facility L5 PROV—L5 Send TSDU 08:20:07.760 >000.
OSI/AS Trace Facility L5 PROV—L5 Send TSDU Continuation Send Length shows the number of bytes in the TSDU. <..TSDU Data..> shows the contents of the TSDU. Each TSDU has a different format. Details of SPDU contents can be found in ISO 8327. Note. Session breaks TSDUs into fragments when writing to transport. The size of a fragment depends on MAXCONNECTIONS but will never be less than 1000 bytes. Lower layer processes may further fragment the original TSDU based on configuration or SYSGEN parameters.
OSI/AS Trace Facility L5 PROV—L5 Start Timer L5 PROV—L5 Start Timer This trace record indicates that the session disconnect timer has been started. The disconnect timer is started in accordance with ISO 8327 after a DN-SPDU (release/response) is sent to the remote session service provider. If the remote does not respond and disconnect transport within the given time, it is the local service provider's responsibility to disconnect.
OSI/AS Trace Facility L5 —L5 Discard Session Resources Subtype L5 Cancel Timer SU Name shows the name by which APS knows this connection. Session ID an internal field that shows a sequence number that is assigned to the connection by this TAPS process. Timer Element an internal field that shows the value returned by signaltimeout. L5 —L5 Discard Session Resources This trace record indicates that session is discarding the connection. This means that transport will be disconnected.
OSI/AS Trace Facility L5—L5 State Machine 08:20:09.610 >000.000 #1139 TAPS L5 L5 Error Report Su Name #ZMF0021 Status Code = ZAPS^Val^Status^Discard (7) Error = ZAPS^Err^Operator^Abort(-114), Error Subcode = (0). Subtype L5 Error Report SU Name shows the name by which APS knows this connection. Status Code shows the status code returned to the APS procedure. See the OSI/AS Programming Manual for descriptions of possible values. Error shows the error returned to the APS procedure.
OSI/AS Trace Facility L5—L5 State Machine SU Name shows the name by which APS knows this connection. Session ID an internal field that shows a sequence number that is assigned to the connection by this TAPS process. Request ID an internal field that shows the address of the buffer that controls the user request that caused the state machine call. When dealing with an event from transport, this value is often null (%H0000000).
A OSI/AS SCF Summary ABORT Command Use the ABORT command to terminate the operation of objects as quickly as possible. ABORT is a sensitive command.
OSI/AS SCF Summary ACTIVATE Command ACTIVATE Command Use the ACTIVATE command to return a suspended object to the STARTED state. ACTIVATE is a sensitive command.
OSI/AS SCF Summary ADD Command ADD Command Use the ADD command to define an object to the OSI/AS subsystem. ADD is a sensitive command. ADD Command Syntax ADD [ /OUT file-spec/ ] [ object-spec ] [ , attribute-spec ] ...
OSI/AS SCF Summary ADD ENTRY #NSAP Command ADD ENTRY #NSAP Command An attribute-spec for the ADD ENTRY #NSAP command is one of the following attribute name and value combinations: [ [ [ [ [ L3PROFILE profile-name ] L4PROFILE profile-name ] L4SERVER indirect-process-name ] NETADDR-MODE { NORMAL | X25-1980 } ] SNPA string ] ADD ENTRY #SNPA Command An attribute-spec for the ADD ENTRY #SNPA command is one of the following attribute name and value combinations: [ L3PROFILE profile-name ] [ L3SERVER indirect-
OSI/AS SCF Summary ADD PROFILE #L3 Command ADD PROFILE #L3 Command An attribute-spec for the ADD PROFILE #L3 command is one of the following attribute name and value combinations: [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ IPNULLLAYER { ON | OFF } ] IPX25SNDCF { ON | OFF } ] X25ACCEPTCHG { ON | OFF } ] X25BCUG integer ] X25CUG integer ] X25CUGTYPE { BASIC | EXT | BASICOA | EXTOA } ] X25DESTADDR “address” ] X25NEGOTIATE { value | “(” value [ , value ] ...“)” } ] X25NONEGOTIATE { value | “(” value [ , value ] ...
OSI/AS SCF Summary ADD PROFILE #L4 Command ADD PROFILE #L4 Command An attribute-spec for the ADD PROFILE #L4 command is one of the following attribute name and value combinations: [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ ALTCLASS { 0 | 1 | 2 | 3 | 4 } ] CHECKSUM { ON | OFF } ] CLASS { 0 | 1 | 2 | 3 | 4 } ] CONNECTTIMEOUT time ] DISCONNTIMEOUT time ] EXPEDITED { ON | OFF } ] EXTENDEDFORMAT { ON | OFF } ] INACTIVETIMEOUT time ] L4WINDOW integer ] MAXREXMIT integer ] MULTIPLEX { ON | OFF } ] NETTYPE { A | B | C
OSI/AS SCF Summary ALLOWOPENS Command ALLOWOPENS Command Use the ALLOWOPENS command to permit file-system opens to be issued to an object. ALLOWOPENS is a sensitive command.
OSI/AS SCF Summary ALTER Command ALTER Command Use the ALTER command to change the values of the attributes of an existing object. The ALTER command changes only the specified attributes of the target object. ALTER is a sensitive command. ALTER Command Syntax ALTER [ /OUT file-spec/ ] [ object-spec ] { , attribute-spec [ , attribute-spec ] ...
OSI/AS SCF Summary ALTER ENTRY #NSAP Command ALTER ENTRY #NSAP Command An attribute-spec for the ALTER ENTRY #NSAP command is one of the following attribute name and value combinations: [ [ [ [ [ L3PROFILE profile-name ] L4PROFILE profile-name ] L3SERVER indirect-process-name ] NETADDR-MODE { NORMAL | X25-1980 } ] SNPA string | RESET ] ALTER ENTRY #SNPA Command An attribute-spec for the ALTER ENTRY #SNPA command is one of the following attribute name and value combinations: [ L3PROFILE profile-name ] [
OSI/AS SCF Summary ALTER PROFILE #L3 Command ALTER PROFILE #L3 Command An attribute-spec for the ALTER PROFILE #L3 command is one of the following attribute name and value combinations: [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ } [ [ IPNULLLAYER { ON | OFF } ] IPX25SNDCF { ON | OFF } ] X25ACCEPTCHG { ON | OFF } ] X25BCUG { integer | RESET } ] X25CUG { integer | RESET } ] X25CUGTYPE { BASIC | EXT | BASICOA | EXTOA } ] X25DESTADDR { “address” | RESET } ] X25NEGOTIATE { value | “(” value [ , value ] ...
OSI/AS SCF Summary ALTER PROFILE #L4 Command ALTER PROFILE #L4 Command An attribute-spec for the ALTER PROFILE #L4 command is one of the following attribute name and value combinations: [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ ALTCLASS { 0 | 1 | 2 | 3 | 4 } ] CHECKSUM { ON | OFF } ] CLASS { 0 | 1 | 2 | 3 | 4 } ] CONNECTTIMEOUT time ] DISCONNTIMEOUT time ] EXPEDITED { ON | OFF } ] EXTENDEDFORMAT { ON | OFF } ] INACTIVETIMEOUT time ] L4WINDOW integer ] MAXREXMIT integer ] MULTIPLEX { ON | OFF } ] NETTYPE { A |
OSI/AS SCF Summary ALTER SERVICE #L3 Command ALTER SERVICE #L3 Command An attribute-spec for the ALTER SERVICE #L3 command is one of the following attribute name and value combinations: [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ } [ [ ESISCHECKSUM { ON | OFF } ] ESISENABLE { ON | OFF } ] ESISESCONFTIME time ] ESISESGROUPMACADDR { “address” | RESET } ] ESISHOLDTIME time ] ESISISGROUPMACADDR { “address” | RESET } ] ESISNOTIFYIS { ON | OFF } ] ESISQUERYRETRY integer ] ESISQUERYTI
OSI/AS SCF Summary ALTER SERVICE #L4 Command ALTER SERVICE #L4 Command An attribute-spec for the ALTER SERVICE #L4 command is one of the following attribute name and value combinations: [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ [ ALTCLASS { 0 | 1 | 2 | 3 | 4 } ] CHECKSUM { ON | OFF } ] CHECKTSEL { ON | OFF } ] CLASS { 0 | 1 | 2 | 3 | 4 } ] CONNECTTIMEOUT time ] DISCONNTIMEOUT time ] EXPEDITED { ON | OFF } ] EXTENDEDFORMAT { ON | OFF } ] INACTIVETIMEOUT time ] INBOUNDCRCONFERRTHLD number ] I
OSI/AS SCF Summary ALTER SERVICE #L6 Command ALTER SERVICE #L6 Command An attribute-spec for the ALTER SERVICE #L6 command is one of the following attribute name and value combinations: [ [ [ [ ARPPPDUSENTPROTERRORGROUPTHLD CPRPPDURECVPERMANENTGROUPTHLD CPRPPDURECVTRANSIENTGROUPTHLD CPRPPDUSENTPERMANENTGROUPTHLD number number number number ] ] ] ] ALTER SERVICE #ACSE Command An attribute-spec for the ALTER SERVICE #ACSE command is one of the following attribute name and value combinations: [ [ [ [ [ [
OSI/AS SCF Summary CHECK Command CHECK Command Use the CHECK ENTRY command before starting a connection for the first time as a prediagnostic tool to determine if the connection will be successful and to determine what servers and protocol related attributes will be used in the connection. CHECK is a nonsensitive command.
OSI/AS SCF Summary CHECK SU Command CHECK SU Command Use the CHECK SU command after experiencing problems with a connection (or a connection attempt) to obtain more detailed error information about connection problems (the SU must be static if the connection is not available).
OSI/AS SCF Summary DELETE Command DELETE Command Use the DELETE command to remove objects from the OSI/AS subsystem. Only objects that were added with the ADD command can be deleted. DELETE is a sensitive command.
OSI/AS SCF Summary INFO Command INFO Command Use the INFO command to display configuration information, such as the current attribute values for the specified object. INFO is a nonsensitive command.
OSI/AS SCF Summary LISTOPENS Command LISTOPENS Command Use the LISTOPENS command to display information about file-system opens that apply to the specified object. LISTOPENS is a nonsensitive command.
OSI/AS SCF Summary NAMES Command NAMES Command Use the NAMES command to display a list of the subordinate object types and names for the specified object. NAMES is a nonsensitive command. NAMES Command Syntax AMES [ /OUT file-spec/ ] [ object-spec ] The object-spec is object-type object-name null ENTRY ENTRY ENTRY PROCESS PROCESS PROCESS PROCESS PROFILE PROFILE PROFILE SERVICE SERVICE SU SU SUBSYS $process-name $osi-mgr-name.#entry-type.entry-name $osi-mgr-name.#entry-type.* $osi-mgr-name.*.
OSI/AS SCF Summary START Command START Command Use the START command to initiate the operation of an object. START is a sensitive command.
OSI/AS SCF Summary STATS Command STATS Command Use the STATS command to display statistical information for the specified object. STATS is a sensitive command only when the RESET option is specified.
OSI/AS SCF Summary STATUS Command STATUS Command Use the STATUS command to display current status information about an object, such as the dynamic state and the last error (SU objects only). STATUS is a nonsensitive command.
OSI/AS SCF Summary STOP Command STOP Command Use the STOP command to terminate the activity of objects in a normal manner. STOP is a sensitive command.
OSI/AS SCF Summary STOPOPENS Command STOPOPENS Command Use the STOPOPENS command to prevent further file-system opens from being issued to an object without disrupting any of the current activity. STOPOPENS is a sensitive command.
OSI/AS SCF Summary SUSPEND Command SUSPEND Command Use the SUSPEND command to restrict the use of connections to and from the specified process. SUSPEND is a sensitive command.
OSI/AS SCF Summary TRACE Command TRACE Command Use the TRACE command to collect trace information. TRACE is a sensitive command. TRACE Command Syntax TRACE [ /OUT file-spec/ ] [ object-spec ] { , STOP { [ , COUNT count [ , NOCOLL [ , PAGES pages [ , RECSIZE size [ , SELECT select-spec [ , TO file-spec [ , WRAP } ] ] ] ] ] ] ] *** } *** This attribute is required when a trace is started.
OSI/AS SCF Summary TRACE Command Syntax The select-spec is { keyword } { ( keyword [ , keyword ]...
OSI/AS SCF Summary Version Command Version Command Use the VERSION command to display the version level of the specified object. VERSION is a nonsensitive command.
OSI/AS SCF Summary VERSION Command Syntax OSI/AS SCF Reference Manual—424121-001 A-30
B OSI/SCF SCF Error Messages This appendix describes three types of SCF error messages that apply to the OSI/AS subsystem: • • • Error Messages With Positive Numbers (on page B-2) are generated by the OSI/AS subsystem. Error Messages With Negative Numbers (on page B-5) are general SCF messages, but are documented here because they have additional cause and recovery information that is specific to the OSI/AS subsystem.
OSI/SCF SCF Error Messages Error Messages With Positive Numbers Error Messages With Positive Numbers Messages with positive error numbers are generated by the OSI/AS subsystem. OSI/AS Error 00001 Guardian Procedure error. %herror-number Call procedure-name, Error Cause. An error occurred after a call was made to a Guardian 90 procedure. Recovery. Contact your service representative immediately. OSI/AS Error 00002I OSI/AS 00002 Internal CASE statement range error. Cause.
OSI/SCF SCF Error Messages Error Messages With Positive Numbers OSI/AS Error 00502I OSI/AS 00502 INVALID ATTRIBUTE VALUE Cause. The value entered is not valid for the indicated attribute. Recovery. Check the attribute for a valid value and reissue the command with a valid value. OSI/AS Error 00503 OSI/AS 00503 MISSING REQUIRED ATTRIBUTE: attribute-name Cause. A required attribute is missing for the command that was entered. Recovery. Check that all required attributes are entered for this command.
OSI/SCF SCF Error Messages Error Messages With Positive Numbers OSI/AS Error 00508 OSI/AS 00508 Missing type specification Cause. The CHECK ENTRY command has determined that you are missing a required configuration component. Recovery. Your configuration must include the missing type specification. OSI/AS Error 00509 OSI/AS 00509 Unable to process this response Cause. The CHECK ENTRY PROFILES command encountered an internal error during the processing of a local #APPL name.
OSI/SCF SCF Error Messages Error Messages With Negative Numbers Error Messages With Negative Numbers Messages with negative error numbers are general SCF messages, but are documented here because they have additional cause and recovery information that is specific to the OSI/AS subsystem. OSI/AS Error -00017 OSI/AS E-00017 Object object-name not found Cause 1. The specified object name could not be found within the subsystem. Usually this means the object has not been added yet.
OSI/SCF SCF Error Messages Error Messages With Negative Numbers OSI/AS Error -00036 OSI/AS E-00036 Value of attribute attribute-name may not be used in conjunction with attribute-name for object-name. Cause 1. The particular value specified with the named attribute conflicts with one of the other attribute values for the object. Recovery 1. Specify a different value or delete the attribute and reissue the command. Cause 2.
OSI/SCF SCF Error Messages Error Messages Without Numbers Error Messages Without Numbers Messages without error numbers are generated during command parsing and are generally self explanatory. In a few cases, however, additional information needs to be provided. These cases are documented in this appendix. Expecting an existing SCF supported object name Cause.
OSI/SCF SCF Error Messages Error Messages Without Numbers OSI/AS SCF Reference Manual—424121-001 B-8
C OSI/AS SCF Examples of Configuration Command Files This appendix contains examples of command files of Guardian and SCF commands to set up particular subsystem configurations. Since each of these examples contains a mixture of SCF and non-SCF commands, use the OBEY command to invoke the appropriate file. The six example configurations are as follows: • • • • • • OSI/AS on an X.25 Network on page C-2 OSI/AS on an X.
OSI/AS SCF Examples of Configuration Command Files OSI/AS on an X.25 Network Note. To use these command files, you must change the file and process names to reflect your environment. In addition, you must first logged on as a super-group user. OSI/AS on an X.25 Network The source code file for this example is provided as part of the OSI/AS software. It resides (by default) in $SYSTEM.ZOSIAS.EXCFG1.
OSI/AS SCF Examples of Configuration Command Files OSI/AS on an X.25 Network start process $OSIM version $OSIM ============================================================= == Define NSP, TSP, and TAPS processes. ============================================================= add process $OSIM.#nsp.X251, name $X251 add process $OSIM.#tsp.TSP1, name $TSP1 & , codefile $SYSTEM.SYS01.TSPOBJ add process $OSIM.#taps.TAPS1, name $TAPS1 & , codefile $SYSTEM.SYS01.
OSI/AS SCF Examples of Configuration Command Files OSI/AS on an X.25 Network ==== add entry $OSIM.#appl.apa1, aequalifier 12345678 & , aptitle ( 1 5 99 ) & , psel 66a1, ssel 55a1 & , tsel 44a1, nsap 33a1 ==== ==== Add a name for the remote application. ==== add entry $OSIM.#appl.apb1 & , psel 66b1, ssel 55b1 & , tsel 44b1, nsap 33b1 ==== ==== Method 1 ends here ==== ============================================================ == Define entries - Method 2.
OSI/AS SCF Examples of Configuration Command Files OSI/AS on an X.25 Network start process $OSIM.#taps.TAPS1 exit ============================================================= == Define NSP, TSP, and TAPS processes. ============================================================= add process $OSIM.#nsp.X251, name $X251 add process $OSIM.#tsp.TSP1, name $TSP1 & , codefile $SYSTEM.SYS01.TSPOBJ add process $OSIM.#taps.TAPS1, name $TAPS1 & , codefile $SYSTEM.SYS01.
OSI/AS SCF Examples of Configuration Command Files OSI/AS on an X.25 Network With SNDCF and Full-IP ==== ==== Add a name for the remote application. ==== add entry $OSIM.#appl.apb1 & , psel 66b1, ssel 55b1 & , tsel 44b1, nsap 33b1 ============================================================ == Start the processes. ============================================================ start process $OSIM.#tsp.TSP1 start process $OSIM.#taps.TAPS1 exit OSI/AS on an X.
OSI/AS SCF Examples of Configuration Command Files OSI/AS on an X.25 Network With SNDCF and Full-IP ============================================================= == Configure OSI manager process. ============================================================= alter subsys $OSIM, mib ZOSIDB start process $OSIM version $OSIM ============================================================= == Define NSP, TSP, and TAPS processes. ============================================================= add process $OSIM.#nsp.
OSI/AS SCF Examples of Configuration Command Files OSI/AS on a LAN With Full-IP and No ES-IS ==== add entry $OSIM.#appl.apa1, aequalifier 12345678 & , aptitle ( 1 5 99 ) & , psel 66a1, ssel 55a1 & , tsel 44a1, nsap 33a1 === ===== Add a name for the remote application. ==== add entry $OSIM.#appl.apb1 & , psel 66b1, ssel 55b1 & , tsel 44b1, nsap 33b1 ============================================================ == Start the processes.
OSI/AS SCF Examples of Configuration Command Files OSI/AS on a LAN With Full-IP and No ES-IS ============================================================= allow all errors ============================================================= == Configure OSI manager process. ============================================================= alter subsys $OSIM, mib ZOSIDB start process $OSIM version $OSIM ============================================================= == Define NSP, TSP, and TAPS processes.
OSI/AS SCF Examples of Configuration Command Files OSI/AS on a LAN With Full-IP and ES-IS ===== Add a name for the local application. ==== add entry $OSIM.#appl.apa1, aequalifier 12345678 & , aptitle ( 1 5 99 ) & , psel 66a1, ssel 55a1 & , tsel 44a1, nsap 33a1 ==== ==== Add a name for the remote application. add entry $OSIM.#appl.apb1 & , psel 66b1, ssel 55b1 & , tsel 44b1, nsap 33b1 ============================================================= == Start the processes.
OSI/AS SCF Examples of Configuration Command Files OSI/AS on a LAN With Full-IP and ES-IS == SCF commands for configuring the subsystem: ============================================================= allow all errors ============================================================= == Configure OSI manager process.
OSI/AS SCF Examples of Configuration Command Files OSI/AS on a LAN With Null-IP ==== add entry $OSIM.#tsel.44b1 ==== ==== Add a name for the local application. ==== add entry $OSIM.#appl.apa1, aequalifier 12345678 & , aptitle ( 1 5 99 ) & , psel 66a1, ssel 55a1 & , tsel 44a1, nsap 33a1 ==== ==== Add a name for the remote application. ==== add entry $OSIM.#appl.apb1 & , psel 66b1, ssel 55b1 & , tsel 44b1, nsap 33b1 ============================================================= == Start the processes.
OSI/AS SCF Examples of Configuration Command Files OSI/AS on a LAN With Null-IP == $SYSTEM.SYS01.OSIMGR/nowait, name $OSIM, swap $DISK1 & , cpu 2/ 3 ============================================================= == SCF commands for configuring the subsystem: ============================================================= allow all errors ============================================================= == Configure OSI manager process.
OSI/AS SCF Examples of Configuration Command Files OSI/AS, Large Application, on an X.25 Network , server $OSIM.#tsp.TSP1 & , snpa fe08008e000010 & , profile $OSIM.#L4.L4p1 ==== ==== Add address information for remote NSAP. add entry $OSIM.#nsap.fe08008e000a3e, snpa fe08008e000a3e ==== ==== Add TSEL information for local TSEL. add entry $OSIM.#tsel.44a1 & , server $OSIM.#taps.TAPS1 & , profile $OSIM.#L5.L5p1 ==== ==== Add address information for remote TSEL. add entry $OSIM.#tsel.
OSI/AS SCF Examples of Configuration Command Files OSI/AS, Large Application, on an X.25 Network ============================================================= == == Clean up the OSI/AS subsystem first! == allow 7 errors stop process $OSIM stop process $TAPS1 stop process $TAPS2 stop process $TAPS3 stop process $TSP1 stop process $TSP2 stop process $TSP3 == == Create new MIB. == fup purge (ZOSIDB,ZOSIDB0) ! fup /in dbfup/ == == Create new OSI manager process. == $SYSTEM.SYS01.
OSI/AS SCF Examples of Configuration Command Files OSI/AS, Large Application, on an X.25 Network add process $OSIM.#taps.TAPS3, name $TAPS3 & , codefile $SYSTEM.SYS01.TAPSOBJ ============================================================ == Define profiles. (Set up several profiles you may want == to use.) ============================================================ add profile $OSIM.#L5.L5prof1, vsn1 off, vsn2 on add profile $OSIM.#L5.
OSI/AS SCF Examples of Configuration Command Files OSI/AS, Large Application, on an X.25 Network ==== ==== Add entry for local TSEL. ==== add entry $OSIM.#tsel.44a1 & , server $OSIM.#taps.TAPS1 & , profile $OSIM.#L5.L5prof1 ==== ==== Add optional address information for remote TSEL ==== (necessary only when special profiles need to be ==== associated with those TSELs). ==== add entry $OSIM.#tsel.44b1 ==== ==== Add a name for each local application specify servers ==== and profiles as required.
OSI/AS SCF Examples of Configuration Command Files OSI/AS, Large Application, on an X.25 Network add entry $OSIM.#appl.apa2, aequalifier 12345678 & , aptitle ( 1 5 99 ) & , psel 66a1, ssel 55a1 & , L5server $OSIM.#taps.TAPS2 & , L5profile $OSIM.#L5.L5prof2 & , tsel 44a1 & , L4server $OSIM.#tsp.TSP2 & , L4profile $OSIM.#L4.L4prof2 & , nsap 33a1 & , L3server $OSIM.#nsp.X252 & , L3profile $OSIM.#L3.L3prof2 add entry $OSIM.#appl.
OSI/AS SCF Examples of Configuration Command Files OSI/AS, Large Application, on an X.25 Network , psel 66b1, ssel 55b1 & , tsel 44b1, nsap 33b1 =================================================== ========= == Start the processes. =================================================== ========= start process $OSIM.#tsp.TSP1 start process $OSIM.#tsp.TSP2 start process $OSIM.#tsp.TSP3 start process $OSIM.#taps.TAPS1 start process $OSIM.#taps.TAPS2 start process $OSIM.#taps.
OSI/AS SCF Examples of Configuration Command Files OSI/AS, Large Application, on an X.
D OSI/AS SCF Attribute Name Changes Some attribute names have been changed to improve product usability. All changes maintain backward compatibility: existing programs or command files will still work with the original names. The following tables list the terms that were changed.
OSI/AS SCF Attribute Name Changes ADD PROFILE #L5 Command ADD PROFILE #L5 Command Original Attribute Name New Attribute Name DISCONNECTTIMEOUT DISCONNTIMER ALTER ENTRY #TSEL Command Original Attribute Name New Attribute Name PROFILE L5PROFILE SERVER L5SERVER ALTER ENTRY #NSAP Command Original Attribute Name New Attribute Name PROFILE L4PROFILE SERVER L4SERVER ALTER ENTRY #SNPA Command Original Attribute Name New Attribute Name PROFILE L3PROFILE SERVER L3SERVER ALTER PROCESS Command O
OSI/AS SCF Attribute Name Changes ALTER SERVICE #L4 Command ALTER SERVICE #L4 Command Original Attribute Name New Attribute Name DISCONNECTTIMEOUT DISCONNTIMEOUT TRANSWINDOW L4WINDOW ALTER SERVICE #L5 Command Original Attribute Name New Attribute Name DISCONNECTTIMEOUT DISCONNTIMER ALTER SUBSYS Command Original Attribute Name New Attribute Name TAPSFILE TAPSCODEFILE TSPFILE TSPCODEFILE OSI/AS SCF Reference Manual—424121-001 D-3
OSI/AS SCF Attribute Name Changes OSI/AS SCF Reference Manual—424121-001 D-4 ALTER SUBSYS Command
E OSI/AS SCF Command Support Table E-1 identifies the SCF commands that can be issued to the OSI/AS subsystem and the commands that are not supported. The SCF/AS specific supported commands are documented in Section 2, OSI/AS SCF Commands. The general SCF supported commands can be issued to the OSI/AS and are documented in the Subsystem Control Facility (SCF) Reference Manual (for D-series releases) or the SCF Reference Manual for G-Series Releases. Table E-1.
OSI/AS SCF Command Support Table E-1.
OSI/AS SCF Command Support Table E-1.
OSI/AS SCF Command Support OSI/AS SCF Reference Manual—424121-001 E-4
Glossary The following glossary defines terms used in this manual and in the other Compaq OSI product manuals. Not all terms listed here are used in this particular manual. action event. An event that requires operator intervention. Each subsystem determines which events are action events by including a unique Event Management Service (EMS) token in the event message.
Glossary Compaq OSI/FTAM address component of the Application Layer, allowing Compaq applications to communicate with other applications in a multivendor environment. Compaq OSI/FTAM. A communications subsystem that provides file transfer, access, and management (FTAM) functions across a heterogeneous network, in conformance with the International Standards Organization (ISO) FTAM standard. Compaq OSI/FTAM supports the transfer of files between Himalaya S-series servers and other kinds of computers.
Glossary data-transfer phase arrives at the next layer without any errors. OSI/TS is an example of an application that uses the Data Link Layer. data-transfer phase. The phase of an Open Systems Interconnection (OSI) connection in which data is transferred. This phase begins when the connection-establishment phase is completed. Compare connection-release phase. dialog unit. In the Session Layer, the work carried out between two major synchronization points chosen by the application.
Glossary Event Management Service (EMS) Event Management Service (EMS). A part of Distributed Systems Management (DSM) used to provide event collection, event logging, and event distribution facilities. EMS has a programmatic interface based on the Subsystem Programmatic Interface (SPI) for both reporting and retrieving events. flow control. A function that regulates the flow of data within a layer or between adjacent layers. global network address.
Glossary link access protocol - balanced (LAP-B) link access protocol - balanced (LAP-B). International Telecommunications Union– Telecommunications (ITU–T) standards that define in the Data Link Layer the requirements for X.25 connections over wide area networks (WANs). local address. The terms local address and remote address refer to the two endpoints of a connection. A local address is the address of the end system that is considered local with respect to the user. Management Information Base (MIB).
Glossary network service provider (NSP) process network service provider (NSP) process. A process in the Open Systems Interconnection (OSI) subsystem that performs service and protocol functions for the Network Layer and, for local area networks (LANs), some functions of the Data Link Layer. NSP processes are provided by these underlying subsystems: X.
Glossary OSI/FTAM OSI/FTAM. See Compaq OSI/FTAM. OSI/MHS. See Compaq OSI/MHS. OSI/TS. See Compaq OSI/TS. X25AM Physical Layer. Layer 1 in the Open Systems Interconnection (OSI) Reference Model. This layer establishes the actual physical connection between the network and the computer equipment. Protocols at the Physical Layer include rules for the transmission of bits across the physical medium and rules for connectors and wiring. Port Access Method (PAM).
Glossary service service. A set of primitives (operations) that a layer provides to the layer above it. The service defines what operations the layer can perform on behalf of its users, but not how these operations are implemented. A service relates to an interface between two layers, with the lower layer being the service provider and the upper layer being the service user. service access point (SAP). The access means by which a pair of communicating entities in adjacent layers use or provide services.
Glossary subnetwork subnetwork. One or more intermediate systems that provide relaying and through which end open systems may establish network connections. subsystem. In Distributed Systems Management (DSM), a program or set of processes that manages a cohesive set of objects. Each subsystem has a process through which applications can request services by issuing commands defined by that subsystem; in some cases, this process is the entire subsystem. Many subsystems also have an interactive interface.
Glossary token and layers below. Replaced by the Port Access Method (PAM) subsystem for G06 and later releases. token. (1) An attribute of a Session Layer connection, dynamically assigned to one session service user at a time, that confers the exclusive right to perform a given function. (2) In Distributed Systems Management (DSM) terms, a distinguishable unit in a Subsystem Programmatic Interface (SPI) message. transfer syntax.
Index A ABORT commands 2-21 Abstract Syntax Notation-1 (ASN.
Index D Commands See PTrace commands or SCF commands Configurations example command files LAN with full-IP and ES-IS C-10 LAN with full-IP and no ES-IS C-8 LAN with null-IP C-12 X.25 large application C-14 X.25 network C-2, C-6 X.
Index M L5 trace records (continued) L5 PROV-L5 Issue Write Expedited 3-92 L5 PROV-L5 Issue Writeread 3-89 L5 PROV-L5 I/O Completion 3-93 L5 PROV-L5 I/O Completion Continuation 3-95 L5 PROV-L5 Post Transport Read 3-86 L5 PROV-L5 Send TSDU 3-96 L5 PROV-L5 Send TSDU Continuation 3-98 L5 PROV-L5 Start Timer 3-99 L5 USER-L5 Abort Continuation Event 3-79 L5 USER-L5 Continuation Event 3-78 L5 USER-L5 Event 3-76 L5 USER-L5 First Request 3-82 L5 USER-L5 Multi Abort Request 3-85 L5 USER-L5 Multi Last Request 3-84
Index P Objects (continued) SUBSYS 2-15 table of name formats 2-4 table of SCF 2-1 terminating with STOP command 2-219 Object-name not found error B-5 Object-specs table of syntax 2-4 OSI manager not running error B-7 OSI manager process, table of supported SCF commands 2-1 OSI/AS subsystem relationship of processes to tracing facility 3-3 standards implemented, as related to trace facility 3-2 summary of SCF commands for 2-1 TAPS processes, as related to trace facility 3-3 OSI/TS subsystem attributes not
Index S trace record displays (continued) trace record formats 3-23, 3-25 trace records in 3-4 PTrace Ccmmands SELECT 3-16 PTrace commands 3-6/3-21 DETAIL 3-8 FILTER 3-8 HEX 3-15 RUN, starting PTrace 3-6 SELECT 3-16 STATETABLES 3-21 PTrace displays ACSE PROV-ACSE Reply 3-47 ACSE PROV-L6 Event 3-48 ACSE PROV-L6 Request 3-49 ACSE SM-ACSE State Machine 3-52 ACSE USER-ACSE Event 3-41 ACSE USER-ACSE Reply 3-40 ACSE USER-ACSE Request 3-44 ACSE-ACSE Error Report 3-51 Allocate 3-27 ASN.1-ACSE Decode 3-34 ASN.
Index S SCF commands ABORT 2-21 ACTIVATE 2-23 ADD 2-24 ALLOWOPENS 2-56 ALTER 2-57 CHECK 2-111 DELETE 2-142 INFO 2-144 LISTOPENS 2-171 NAMES 2-174 old and new attribute names D-1/D-3 START 2-182 STATS 2-184 STOP 2-219 STOPOPENS 2-221 SUSPEND 2-223 syntax summary A-1/A-29 table of sensitive and nonsensitive 2-3 table of supported 2-1 TRACE 2-225 SCF objects See Objects or individual objects SCP as interface to OSI/AS 1-1 SELECT command, PTrace 3-16 Selection criteria invalid error B-4 Sensitive commands, ta
Index T T TAPS processes as related to trace facility 3-3 table of supported SCF commands 2-1 Timers 2-25 TRACE commands 2-225 as related to trace facility 3-1 trace records in 3-4 Trace record displays See PTrace U Unable to process this response error B-4 Unknown error from server B-2 User data, translating using BER 3-10 User primitives ACSE, displaying 3-12 L5, displaying 3-14 L6, displaying 3-13 V VSN1 or VSN2 error B-3 W Wildcards 2-4 PROCESS object 2-56 Wildcards not allowed error B-3 OSI/AS SC
Index W OSI/AS SCF Reference Manual—424121-001 Index-8
