OSI/FTAM and OSI/APLMGR SCF Reference Manual Abstract This manual describes the Subsystem Control Facility (SCF) commands used to configure, control, and inquire about the Tandem OSI/FTAM and OSI/APLMGR subsystems. Product Version OSI/FTAM D43 and OSI/APLMGR D43 Supported Releases This manual supports the D43 release and all subsequent D-series releases and the G06.05 release and all subsequent G-series releases until otherwise indicated in a new edition.
Document History Part Number Product Version Published 421943-001 OSI/FTAM D43 OSI/APLMGR D43 June 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/FTAM and OSI/APLMGR SCF Reference Manual Glossary Index Figures Tables What’s New in This Manual xiii Manual Information xiii New and Changed Information xiii About This Manual xiv Manual Audience xv Manual Contents xvi FTAM Manuals xvii Related Manuals xix ISO and NIST FTAM Phase 2 Standards Your Comments Invited xxi xxii Notation Conventions xxiii 1.
1. Introduction to SCF for Tandem FTAM (continued) Contents 1. Introduction to SCF for Tandem FTAM (continued) How SCF Works 1-8 Running SCF 1-9 1-9 Subsystem Control Facility (SCF) Commands SCF CONFIRM Command 1-10 SCF Product Modules for Tandem FTAM 1-10 SCF Time Values 1-10 SCF Features Not Supported 1-10 SCF Online Help 1-11 SCF Error Messages 1-11 2.
3. SCF Commands for Tandem FTAM Contents 3.
3. SCF Commands for Tandem FTAM (continued) Contents 3.
3. SCF Commands for Tandem FTAM (continued) Contents 3.
3. SCF Commands for Tandem FTAM (continued) Contents 3.
3. SCF Commands for Tandem FTAM (continued) Contents 3.
3. SCF Commands for Tandem FTAM (continued) Contents 3.
4. Attributes for Tandem FTAM Contents 4.
5. PTrace Reference for Tandem FTAM Contents 5.
5. PTrace Reference for Tandem FTAM (continued) Contents 5. PTrace Reference for Tandem FTAM (continued) Trace-Record Formats (continued) MEM Allocate 5-34 MEM Deallocate MSG Reply 5-35 5-36 MSG Completion 5-37 MSG I/O Request 5-39 SYSMSG Open Request 5-40 SYSMSG Close Request 5-41 SYSMSG System Message 5-41 A. SCF Command Syntax Summary for Tandem FTAM B. SCF Error Messages for the APLMGR Subsystem C. SCF Error Messages for the FTAM Subsystem Glossary Index Figures Figure i.
Tables Contents Tables Table i. Manual Contents xvi Table ii. ISO and NIST FTAM Phase 2 Standards xxi Table 2-1. Object Types and Object Names Table 2-2. Process States and Intermediate States Table 2-3. Process-State-Transition Commands 2-8 Table 3-1. Subsystem-Specific SCF Commands Table 3-2. Tandem FTAM SCF Commands and Object Types Table 4-1. Tandem FTAM Attribute Categories 4-1 Table 5-1. Device Type and Subtype for APLMGR, Initiator, and Responder Table 5-2.
What’s New in This Manual Manual Information OSI/FTAM and OSI/APLMGR SCF Reference Manual Abstract This manual describes the Subsystem Control Facility (SCF) commands used to configure, control, and inquire about the Tandem OSI/FTAM and OSI/APLMGR subsystems. Product Version OSI/FTAM D43 and OSI/APLMGR D43 Supported Releases This manual supports the D43 release and all subsequent D-series releases and the G06.05 release and all subsequent G-series releases until otherwise indicated in a new edition.
What’s New in This Manual New and Changed Information The following list summarizes the changes to this edition of the manual: • • • • Port Access Method (PAM) and NonStop TCP/IP. Text and figures have been modified to reflect FTAM support for the Tandem NonStop TCP/IP subsystem and for the PAM subsystem, which replaces the Tandem LAN Access Method (TLAM) subsystem for G-series releases.
About This Manual The OSI/FTAM and OSI/APLMGR SCF Reference Manual describes the Subsystem Control Facility (SCF) interactive interface that allows operators to monitor and collect information during the operation of Tandem Open Systems Interconnection/File Transfer, Access and Management (OSI/FTAM) software. Unlike most Tandem subsystems, Tandem FTAM is managed through two SCF interfaces: the interface to the FTAM processes themselves, and the interface to their manager process, APLMGR.
Manual Contents About This Manual Manual Contents Table i lists the sections and appendixes in this manual. Table i. Manual Contents Section or Appendix Contents Section 1, Introduction to SCF for Tandem FTAM Provides an overview of the Tandem FTAM architecture, the management interfaces provided by Tandem FTAM, and a brief description of how SCF is used to manage Tandem FTAM, along with the roles that SCF commands play in configuring and controlling the Tandem FTAM services.
FTAM Manuals About This Manual FTAM Manuals This manual is only one in a set of Tandem FTAM manuals. Figure i shows all the manuals in the Tandem FTAM manual set. Figure i. FTAM Manual Set Tandem OSI/FTAM Programming Guide Concepts and Programming Management Methods Management Reference for Operators Tandem OSI/FTAM Programming Reference Manual Tandem OSI/FTAM Responder Manual OSI/FTAM Config. and Mgmt. Manual Operator Messages Manual OSI/FTAM and OSI/APLMGR SCF Reference CDT 001.
FTAM Manuals About This Manual The following list describes the manuals shown in Figure i on page xvii: • • • • The Tandem OSI/FTAM Programming Guide explains important programming concepts pertaining to the Tandem FTAM application program interface (API) and describes sequences of procedure calls to use to perform common FTAM programming operations. This manual also provides an overview of FTAM concepts for those who have not recently read the ISO 8571 specification.
Related Manuals About This Manual Related Manuals These manuals contain background information on the Tandem environment: • • • The Introduction to Networking and Data Communications for Himalaya S-Series Servers provides an overview of Tandem networking and data communications products. The Introduction to Distributed Systems Management (DSM) introduces the products and components that are collectively called Distributed Systems Management. It also discusses subsystem enhancements to support DSM.
Related Manuals About This Manual • • • The SCF Reference Manual for TLAM describes the SCF commands used to configure, control, and monitor the TAndem LAN Access Method (TLAM) subsystem. The SCF Reference Manual for X25AM describes the SCF commands used to configure, control, and monitor the X.25 Access Method (X25AM) subsystem. It is written for system managers and operators.
ISO and NIST FTAM Phase 2 Standards About This Manual ISO and NIST FTAM Phase 2 Standards This manual and the other OSI/FTAM manuals are written for readers who are familiar with the ISO standards and the National Institute of Standards and Technology (NIST) FTAM Phase 2 agreements, to which Tandem FTAM and the underlying Tandem OSI products conform. These standards are shown in the following table. Table ii.
Your Comments Invited About This Manual Your Comments Invited After using this manual, please take a moment to send us your comments. You can do this by returning a Reader Comment Card or by sending an Internet mail message. A Reader Comment Card is located at the back of printed manuals and as a separate file on the User Documentation disc. You can either fax or mail the card to us. The fax number and mailing address are provided on the card.
Notation Conventions About This Manual Notation Conventions Hypertext Links Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example: This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS.
General Syntax Notation About This Manual | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}...
Change-Bar Notation About This Manual Change-Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
Change-Bar Notation About This Manual OSI/FTAM and OSI/APLMGR SCF Reference Manual—421943-001 xxvi
1 Introduction to SCF for Tandem FTAM This section provides an overview of the Subsystem Control Facility (SCF) interface to Tandem Open Systems Interconnection/File Transfer, Access, and Management (OSI/FTAM). The section also describes the subsystem architecture of Tandem FTAM and the Distributed Systems Management (DSM) interfaces and DSM functions available for Tandem FTAM. This section is intended to help you get started using SCF.
Introduction to SCF for Tandem FTAM OSI/FTAM Subsystem Architecture OSI/FTAM Subsystem Architecture The Tandem FTAM software allows you to access, transfer, and manage files on an OSI network. Tandem FTAM services allow you to create, delete, read, and modify files in addition to reading and changing file attributes. These services are accessed through the FTAM application program interface (API).
Introduction to SCF for Tandem FTAM OSI/APLMGR and OSI/FTAM Subsystems Role of APLMGR Subsystem The APLMGR subsystem manages the Tandem FTAM Application Layer components— that is, the initiator and responder processes. The APLMGR subsystem consists of the APLMGR process and the management information base (MIB), a key-sequenced Enscribe file that stores the configuration information for the APLMGR, initiator, and responder processes.
OSI/APLMGR and OSI/FTAM Subsystems Introduction to SCF for Tandem FTAM Figure 1-1. Relationship of Tandem FTAM to Other Products and Processes User application API Tandem FTAM APLMGR Subsystem DSM SCF APLMGR FTAM Subsystem Initiator Guardian File System EMS PTrace MIB Responder OSI/AS OSI/TS TLAM (or PAM), X25AM, or TCP/IP Communications Network Remote FTAM Initiator Remote FTAM Responder CDT 002.
Introduction to SCF for Tandem FTAM Subsystem Control Facility (SCF) and Other Distributed Systems Management (DSM) Tools Tandem OSI/AS manages the communication of messages between a local Tandem system and a remote system on a network, providing ACSE (in the Application Layer), Presentation Layer, and Session Layer services. OSI/AS uses the lower-layer services provided by OSI/TS along with TLAM (or PAM for G-series systems), X25AM, or TCP/IP.
Subsystem Control Facility (SCF) and Other Distributed Systems Management (DSM) Tools Introduction to SCF for Tandem FTAM Figure 1-2. Tandem FTAM and the DSM Environment User application Management Interface DSM Tools API SCF EMS Tandem FTAM Guardian File System PTrace OSI/AS OSI/TS TLAM (or PAM), X25AM, or TCP/IP Communications Network Remote Initiator Process Remote Responder Process CDT 003.
Introduction to SCF for Tandem FTAM Event Management Service (EMS) Event Management Service (EMS) EMS is a collection of processes, tools, and interfaces that provides event-collection, event-logging, and event-distribution facilities for Tandem subsystems. All Tandem OSI subsystems, including OSI/APLMGR, OSI/FTAM, OSI/AS, OSI/TS, TLAM, PAM, TCP/IP, and X25AM, report significant events in the form of event messages to the EMS collector (primary and/or alternate collector), which logs the messages.
How SCF Works Introduction to SCF for Tandem FTAM How SCF Works Figure 1-3 illustrates the SCF management interface to Tandem FTAM. Figure 1-3. SCF Management Interface SCF Commands SCF Displays Tandem FTAM SCF SCP APLMGR Initiator Responder CDT 004.CDD This figure shows that commands are entered interactively to SCF, which consists of the basic SCF product and the SCF product modules (PMs) for each subsystem.
Introduction to SCF for Tandem FTAM Running SCF Running SCF You can start SCF by using the TACL command interpreter RUN command. This command can be used interactively, included in a command (OBEY) file, or included in a TACL macro or routine. Section 3, SCF Commands for Tandem FTAM, describes the SCF commands for OSI/FTAM and OSI/APLMGR. SCF can accept input from a terminal or a disk file. You can change the input source dynamically by using the OBEY command.
SCF CONFIRM Command Introduction to SCF for Tandem FTAM Other commands make no changes, but simply allow the SCF user to view information. SCP does not perform any security checking on these commands, but allows any Guardian user to perform them. These commands are called nonsensitive commands. Object Attributes All SCF objects (except the null object) used in Tandem FTAM have attributes.
Introduction to SCF for Tandem FTAM SCF Online Help SCF Online Help SCF provides online support when you use the HELP command described in the Subsystem Control Facility (SCF) Reference Manual (for D-series releases) or the SCF Reference Manual for G-Series Releases. If the HELP command alone is entered, SCF responds with a menu that guides you through the available help options. Simply select from the options displayed in the menu for the information you need.
SCF Error Messages Introduction to SCF for Tandem FTAM Common Errors Versus Subsystem-Specific Errors SCF provides a pool of error messages that can be used by all subsystems, called common error messages. These errors always have negative error numbers. The APLMGR subsystem and the FTAM subsystem each use these common errors. The APLMGR subsystem and the FTAM subsystem also can generate error messages that pertain solely to that subsystem, called subsystem-specific error messages.
Introduction to SCF for Tandem FTAM SCF Error Messages Error Message Examples The following error can be returned by the APLMGR subsystem and is specific to the APLMGR subsystem—no other subsystem generates this same error number and text. Cause, effect, and recovery information for this error is given Appendix B, SCF Error Messages for the APLMGR Subsystem. Note that the error number is a positive number. OSIAPLMG E00003 Command not allowed while object is in use.
Introduction to SCF for Tandem FTAM OSI/FTAM and OSI/APLMGR SCF Reference Manual—421943-001 1-14 SCF Error Messages
2 Objects for Tandem FTAM This section explains the object hierarchy used in Tandem FTAM and, for each object type, gives a detailed description of how it is used, along with naming conventions, example names, and states. APLMGR and FTAM Subsystem Object Hierarchy The APLMGR subsystem supports three object types: SUBSYS (subsystem), PROCESS, and PROFILE. Figure 2-1 shows the hierarchical relationships of these three objects to one another. The SUBSYS object controls the PROCESS and PROFILE objects.
Overview of FTAM Objects Objects for Tandem FTAM Overview of FTAM Objects Table 2-1 lists the objects Tandem FTAM supports. Each object type is discussed in detail in the following subsections. Table 2-1. Object Types and Object Names Object Type Object-Name Format Description null Not applicable The absence of an object; it is not a true object type.
Objects for Tandem FTAM null Object null Object The null object type is not an actual object type: “null” is a term used to represent the absence of an object type in the command. If an SCF command supports the null object type, you can issue it without specifying an object type. For Tandem FTAM, the NAMES and VERSION commands support the null object type. The NAMES null command refers to a collection of object types, for the VERSION null command, the object type is irrelevant.
Objects for Tandem FTAM Naming Conventions for the PROCESS Object Naming Initiator and Responder Processes to Be Accessed Through APLMGR The first of the two forms used for naming initiator and responder processes is used to send SCF commands to initiator and responder processes indirectly through the APLMGR process. You can use this form by issuing the command with the following process specification: PROCESS [\system-name.
Wildcard Support for the PROCESS Object Objects for Tandem FTAM Wildcard Support for the PROCESS Object Tandem FTAM supports limited use of wildcards. The wildcard characters are the question mark (?) and the asterisk (*). The question mark denotes any single character; the asterisk denotes any number of characters. When wildcards are used in $process-name or $appl-mgr-name, the first character must be the dollar sign ($).
Object States for the PROCESS Object Objects for Tandem FTAM Object States for the PROCESS Object Tandem FTAM processes can be in, or in transition to, any of four states: UNKNOWN, STARTED, STOPPED, or SUSPENDED. Figure 2-3 illustrates the process states, the commands that cause each state transition, and the intermediate states that exist during process state transitions. State-change commands for processes can be issued only through the APLMGR process. Figure 2-3.
Object States for the PROCESS Object Objects for Tandem FTAM Table 2-2 lists the states and intermediate states for Tandem FTAM PROCESS objects and describes how a process in each state responds to requests. Any requests pending during a state transition are canceled. Table 2-2. Process States and Intermediate States Process State Description ABORTING The process is in transition to the STOPPED state because an ABORT command has been issued. The process is running but will not accept new user requests.
Object States for the PROCESS Object Objects for Tandem FTAM Table 2-3 lists the commands that produce changes in the APLMGR and FTAM process states and describes the effects of these commands on the capabilities of the processes. Any requests pending are canceled when one of these commands is issued. Table 2-3.
Attributes for the PROCESS Object Objects for Tandem FTAM Attributes for the PROCESS Object The following attributes describe and define PROCESS objects: ALLOWSU MAXATTACH SSEL BACKUPCPU NAME SWAP CODEFILE NSAP THRESHOLD COMNAME PRIORITY TSEL CPU PROFILE MAXASSOC PSEL The following TRACE command options are used to trace processes: COUNT SELECT NOCOLL TO PAGES WRAP RECSIZE For detailed information on each attribute, see Section 4, Attributes for Tandem FTAM.
Objects for Tandem FTAM Naming Conventions for the PROFILE Object Naming Conventions for the PROFILE Object You can issue an SCF command with a VFS PROFILE object by naming the profile as follows: PROFILE [\system-name.]$appl-mgr-name.#VFS.profile-name system-name identifies the system in which the APLMGR process is running. appl-mgr-name identifies the name of the APLMGR process and is a valid Guardian process name.
Object States for the PROFILE Object Objects for Tandem FTAM Object States for the PROFILE Object PROFILE objects cannot be in a state; in other words, you cannot issue a command to a PROFILE object to start, stop, suspend, and so on.
SU Object Objects for Tandem FTAM SU Object An SU (subdevice) object provides access to an FTAM association made through a Tandem initiator or responder process. SU objects are used to manage FTAM subdevices. Figure 2-4 shows the differences between initiator and responder subdevices, and their relationship to subdevices in underlying subsystems. Figure 2-4. Tandem FTAM Subdevices User Application Initiator Responder Tandem FTAM TAPS TAPS OSI/AS TSP TSP OSI/TS = subdevice CDT 009.
Objects for Tandem FTAM Wildcard Support for the SU Object Wildcard Support for the SU Object Tandem FTAM supports limited use of wildcards. The wildcard characters are the question mark (?) and the asterisk (*). The question mark denotes any single character; the asterisk denotes any number of characters. When wildcards are used in $process-name or $appl-mgr-name, the first character must be the dollar sign ($).
SUBSYS Object Objects for Tandem FTAM SUBSYS Object The SUBSYS object is used to modify and view the configuration of a subsystem. SCF commands paired with the SUBSYS object are directed to the APLMGR process. The object is identified with an APLMGR process. Naming Conventions for the SUBSYS Object To issue an SCF command to the SUBSYS object, specify the command, followed by the SUBSYS specification and the name of the APLMGR process: command SUBSYS [\system-name.
3 SCF Commands for Tandem FTAM This section describes, in detail, the syntax and considerations for each Subsystem Control Facility (SCF) command supported by Tandem FTAM. Attributes for commands and screen display fields returned by commands are described in Section 4, Attributes for Tandem FTAM. Commands and Object Types This subsection gives an overview of the subsystem-specific SCF commands and object types supported by Tandem FTAM.
Supported Commands SCF Commands for Tandem FTAM Table 3-1 does not describe commands supported by underlying subsystems such as OSI/AS or X25AM. For information on SCF messages for these and other underlying subsystems, see FTAM Manuals on page xvii and Related Manuals on page xix. Table 3-1.
Command/Object-Type Relationships SCF Commands for Tandem FTAM Command/Object-Type Relationships Table 3-2 lists the SCF commands supported by the APLMGR and FTAM subsystems, indicating the types of objects on which each command can operate.
SCF Commands for Tandem FTAM ABORT PROCESS ABORT PROCESS The ABORT PROCESS command terminates the operation of a process, placing it in the STOPPED state, whether or not its work is completed. ABORT PROCESS is a sensitive command. The ABORT PROCESS command has the following syntax: ABORT PROCESS [\system-name.]{$appl-mgr-name } {indirect-process-name } \system-name identifies the system in which the APLMGR process is running. $appl-mgr-name identifies the APLMGR process you want to abort.
ABORT PROCESS Errors SCF Commands for Tandem FTAM ABORT PROCESS Errors The following table lists the most common errors that can occur during the processing of the ABORT PROCESS command: Message Meaning Expecting an existing SCF supported object name or the character “(“ No APLMGR process by the specified name could be found.
SCF Commands for Tandem FTAM ABORT SU ABORT SU The ABORT SU command terminates the operation of an FTAM subdevice whether or not its work is completed. It aborts all pending requests for the subdevice and deletes the subdevice. ABORT SU is a sensitive command. The ABORT SU command has the following syntax: ABORT SU [\system-name.]$process-name.#su-name \system-name identifies the system in which the named process is running.
SCF Commands for Tandem FTAM ABORT SU Errors ABORT SU Errors The following table lists the most common errors that can occur during the processing of the ABORT SU command: Message Meaning OSIFTAM E-00017 Object su-name not found No subdevice by the specified name could be found. To display a list of valid SU names, use the following NAMES command: NAMES SU $process-name SCP E-00022 Security Violation for process-name You are not allowed to perform sensitive commands.
SCF Commands for Tandem FTAM ACTIVATE PROCESS ACTIVATE PROCESS The ACTIVATE PROCESS command changes the state of a process from SUSPENDED to STARTED. ACTIVATE PROCESS is a sensitive command. The ACTIVATE PROCESS command has the following syntax: ACTIVATE PROCESS [ \system-name.]{$appl-mgr-name } {indirect-process-name } \system-name identifies the system in which the APLMGR process is running. $appl-mgr-name identifies the suspended APLMGR process you are activating.
ACTIVATE PROCESS Errors SCF Commands for Tandem FTAM ACTIVATE PROCESS Errors The following table lists the most common errors that can occur during the processing of the ACTIVATE PROCESS command: Message Meaning Expecting an existing SCF supported object name or the character “(“ No APLMGR process by the specified name could be found.
ADD PROCESS SCF Commands for Tandem FTAM ADD PROCESS The ADD PROCESS command configures an initiator or a responder process. ADD PROCESS is a sensitive command. The ADD PROCESS command for an initiator process (FTAMI) has the following syntax: ADD PROCESS [\system-name.]$appl-mgr-name.#FTAMI.internal-name , NAME process-name , { COMNAME "character-string" } { address } [ , attribute-spec ]...
SCF Commands for Tandem FTAM ADD PROCESS attribute-spec is one or more of the attribute name and value specifications. See Section 4, Attributes for Tandem FTAM, for detailed descriptions of the configurable characteristics of Tandem FTAM objects. The ADD PROCESS command for a responder process (FTAMR) has the following syntax: ADD PROCESS [\system-name.]$appl-mgr-name.#FTAMR.internal-name , NAME process-name , PROFILE profile-name [ , attribute-spec ]...
ADD PROCESS Considerations SCF Commands for Tandem FTAM ADD PROCESS Considerations • • Processes that are added are not started automatically. Processes are in the STOPPED state after being added. The ADD PROCESS command defines a process and places the definition in the APLMGR management information base (MIB). The START command acts on the definition and starts the process. You can use the ADD command to configure initiator and responder processes only.
SCF Commands for Tandem FTAM ADD PROCESS Examples ADD PROCESS Examples The following command adds an initiator process named FTI1P that is managed by the APLMGR process named \MARS.$AMGR. When this initiator is started, its primary process runs in CPU 3, and its backup process runs in CPU 4. The initiator handles up to three FTAM associations at a time, and uses “FTM1E” as the default common name for its associations. ADD PROCESS \MARS.$AMGR.#FTAMI.
SCF Commands for Tandem FTAM ADD PROFILE ADD PROFILE The ADD PROFILE command configures the following two types of profiles: • • A virtual filestore (VFS) profile that can later be associated with one or more responder processes. An alternate collector (FTC) profile that specifies an alternate collector for event messages. ADD PROFILE is a sensitive command. The ADD PROFILE command for VFS profiles has the following syntax: ADD PROFILE [\system-name.]$appl-mgr-name.#VFS.
SCF Commands for Tandem FTAM Consideration for VFS Profiles The ADD PROFILE command for FTC profiles has the following syntax: ADD PROFILE [\system-name.] $appl-mgr-name.#FTC , COLLECTOR $collector-name [ , EVENTDESTINATION destination ] \system-name identifies the system in which the APLMGR process is running. $appl-mgr-name identifies the APLMGR process associated with the alternate collector profile you are adding. appl-mgr-name is a Guardian process name.
ADD PROFILE Errors SCF Commands for Tandem FTAM ADD PROFILE Errors The following table lists the most common errors that can occur during the processing of the ADD PROFILE command: Message Description Expecting an existing SCF supported object name or the character “(“ No APLMGR process by the specified name could be found.
SCF Commands for Tandem FTAM ADD PROFILE Examples ADD PROFILE Examples The following command adds a VFS profile named ACCT, associates it with the APLMGR process named \MARS.$AMGR, defines a default group ID and user ID of GUEST.USER1 (but not a default password), and defines a default common name FTM1E to identify the OSI address in the OSI manager MIB: ADD PROFILE \MARS.$AMGR.#VFS.ACCT , DEFUSER "GUEST.
SCF Commands for Tandem FTAM ALLOWOPENS PROCESS ALLOWOPENS PROCESS The ALLOWOPENS PROCESS command configures an initiator process to accept open requests from applications. This command reverses the effects of a STOPOPENS command. ALLOWOPENS PROCESS is a sensitive command. The ALLOWOPENS PROCESS command has the following syntax: ALLOWOPENS PROCESS [\system-name.]{$process-name } {indirect-process-name } \system-name identifies the system in which the APLMGR process is running.
ALLOWOPENS PROCESS Errors SCF Commands for Tandem FTAM ALLOWOPENS PROCESS Errors The following table lists the most common errors that can occur during the processing of the ALLOWOPENS PROCESS command: Message Definition Expecting an existing SCF supported object name or the character “(“ No initiator process by the specified name could be found.
ALLOWOPENS PROCESS Errors SCF Commands for Tandem FTAM Message Definition SCP E-00022 Security Violation for process-name You are not allowed to perform sensitive commands. For further information on sensitive commands, see Sensitive and Nonsensitive Commands on page 1-9. OSIFTAM E00005 Command not valid for responder process or OSIAPLMG E00005 Command not valid for responder process The specified process was an FTAM responder process, but must be an FTAM initiator process.
SCF Commands for Tandem FTAM ALLOWOPENS PROCESS Examples For more information on errors specific to APLMGR (OSIAPLMG errors having positive error numbers), see Appendix B, SCF Error Messages for the APLMGR Subsystem. For more information on errors specific to FTAM (OSIFTAM errors having positive error numbers), see Appendix C, SCF Error Messages for the FTAM Subsystem.
ALTER PROCESS SCF Commands for Tandem FTAM ALTER PROCESS The ALTER PROCESS command changes the value of one or more attributes of an initiator or a responder process in the APLMGR MIB. ALTER PROCESS is a sensitive command. The ALTER PROCESS command for an initiator process (FTAMI) has the following syntax: ALTER PROCESS [\system-name.] $appl-mgr-name.#FTAMI.internal-name , attribute-spec [ , attribute-spec ]...
ALTER PROCESS SCF Commands for Tandem FTAM The ALTER PROCESS command for a responder process (FTAMR) has the following syntax: ALTER PROCESS [\system-name.] $appl-mgr-name.#FTAMR.internal-name , attribute-spec [ , attribute-spec ]...
ALTER PROCESS Considerations SCF Commands for Tandem FTAM ALTER PROCESS Considerations You can use the ALTER PROCESS command to change attributes of initiator and responder processes only. To change attributes of the APLMGR subsystem, you must stop the APLMGR process and restart it using the TACL RUN command, specifying the values for all attributes you wish to configure. You can also change some APLMGR process attributes by using the ALTER SUBSYS command.
SCF Commands for Tandem FTAM ALTER PROCESS Examples ALTER PROCESS Examples The following command redefines the default common name of the FTAM initiator process named FTI1 to “FTM1F”: ALTER PROCESS \MARS.$AMGR.#FTAMI.FTI1, COMNAME "FTM1F" The following command changes the Guardian process name of the FTAM responder process named IFR1 to $RESP1, and changes its primary and backup CPUs to 4 and 5: ALTER PROCESS \MARS.$AMGR.#FTAMR.
ALTER PROFILE SCF Commands for Tandem FTAM ALTER PROFILE The ALTER PROFILE command changes the value of one or more attributes of a virtual filestore (VFS) profile in the APLMGR MIB. ALTER PROFILE is a sensitive command. You cannot alter an alternate collector (FTC) profile. To change an FTC profile, you must delete it and then add a new one with the desired attributes. Note. The ALTER PROFILE command has the following syntax: ALTER PROFILE [\system-name.]$appl-mgr-name.#VFS.
ALTER PROFILE Errors SCF Commands for Tandem FTAM ALTER PROFILE Errors The following table lists the most common errors that can occur during the processing of the ALTER PROFILE command: Message Description Expecting an existing SCF supported object name or the character “(“ No APLMGR process by the specified name could be found.
ALTER SUBSYS SCF Commands for Tandem FTAM ALTER SUBSYS The ALTER SUBSYS command changes the values of the attributes of the APLMGR subsystem. ALTER SUBSYS is a sensitive command. The ALTER SUBSYS command has the following syntax: ALTER SUBSYS [\system-name.]$appl-mgr-name , attribute-spec [ , attribute-spec ]...
ALTER SUBSYS Considerations SCF Commands for Tandem FTAM ALTER SUBSYS Considerations • • The APLMGR process must be in the SUSPENDED state before you can change SUBSYS attributes. When the APLMGR process is placed in the SUSPENDED state, the initiator and responder processes managed by that APLMGR continue their processing over currently existing associations. However, no new associations can be initiated. In addition, the initiators and responders cannot perform any sensitive SCF commands.
SCF Commands for Tandem FTAM ALTER SUBSYS Example For more information on errors specific to APLMGR (OSIAPLMG errors having positive error numbers), see Appendix B, SCF Error Messages for the APLMGR Subsystem. For more information on common SCF error messages (errors having negative error numbers), see the Subsystem Control Facility (SCF) Reference Manual (for D-series releases) or the SCF Reference Manual for G-Series Releases.
SCF Commands for Tandem FTAM DELETE PROCESS DELETE PROCESS The DELETE PROCESS command removes the definition of an initiator or a responder process from the APLMGR MIB. DELETE PROCESS is a sensitive command. The DELETE PROCESS command has the following syntax: DELETE PROCESS [\system-name.]indirect-process-name \system-name identifies the system in which the APLMGR process is running. indirect-process-name identifies the initiator or responder process you want to delete.
DELETE PROCESS Errors SCF Commands for Tandem FTAM DELETE PROCESS Errors The following table lists the most common errors that can occur during the processing of the DELETE PROCESS command: Message Description Expecting an existing SCF supported object name or the character “(“ No APLMGR process by the specified name could be found.
SCF Commands for Tandem FTAM DELETE PROFILE DELETE PROFILE The DELETE PROFILE command removes the definition of a virtual filestore (VFS) profile or an alternate collector (FTC) profile from the APLMGR MIB. DELETE PROFILE is a sensitive command. The DELETE PROFILE command has the following syntax: DELETE PROFILE [\system-name.]$appl-mgr-name. { #VFS.profile-name } { #FTC } \system-name identifies the system in which the APLMGR process is running.
DELETE PROFILE Errors SCF Commands for Tandem FTAM DELETE PROFILE Errors The following table lists the most common errors that can occur during the processing of the DELETE PROFILE command: Message Description Expecting an existing SCF supported object name or the character “(“ No APLMGR process by the specified name could be found.
SCF Commands for Tandem FTAM INFO PROCESS INFO PROCESS The INFO PROCESS command displays the current attribute settings for the specified APLMGR, initiator, or responder process. INFO PROCESS is a nonsensitive command. The INFO PROCESS command has the following syntax: INFO PROCESS [\system-name.]{$appl-mgr-name } {indirect-process-name } {$process-name } [ , DETAIL ] \system-name identifies the system in which the specified process is running.
SCF Commands for Tandem FTAM INFO PROCESS Display Format With DETAIL (APLMGR) For initiator and responder processes, an asterisk preceding the field name indicates that the field can be modified using the ALTER command. For the APLMGR process, however, you can only change the attribute values by first stopping the process, then restarting it using the TACL RUN command, specifying the values for all attributes you wish to configure.
SCF Commands for Tandem FTAM INFO PROCESS Display Format With DETAIL (Initiator) INFO PROCESS Display Format With DETAIL (Initiator) The INFO PROCESS command with the DETAIL option generates the following display for an initiator process specified by indirect-process-name: OSIAPLMG Detailed Info PROCESS \system.$appl-mgr-name.#FTAMI.internal-name *CPU................ *Priority........... *Swap............... *Name............... *Threshold.......... *MaxAssoc........... nn *BackupCPU....
SCF Commands for Tandem FTAM INFO PROCESS Display Format With DETAIL (Responder) INFO PROCESS Display Format With DETAIL (Responder) The INFO PROCESS command with the DETAIL option generates the following display for a responder process specified by indirect-process-name: OSIAPLMG Detailed Info PROCESS \system.$appl-mgr-name.#FTAMR.internal-name *CPU................ *Priority........... *Swap............... *Threshold.......... nn nnn \aaaaaaa.$aaaaaaa nnn *AllowSU............ aaa *MaxAssoc...........
INFO PROCESS Errors SCF Commands for Tandem FTAM INFO PROCESS Errors The following table lists the most common errors that can occur during the processing of the INFO PROCESS command: Message Definition Expecting an existing SCF supported object name or the character “(“ No process by the specified name could be found.
INFO PROCESS Examples SCF Commands for Tandem FTAM INFO PROCESS Examples The following command displays information on the APLMGR process called $AMGR running in the \MARS system: INFO PROCESS \MARS.$AMGR The following display is returned: OSIAPLMG Info PROCESS \MARS.$AMGR *Name \MARS.$AMGR *CPU 1 *BackupCPU 2 *Priority *Codefile 142 \MARS.$SYSTEM.SYS00.
INFO PROCESS Examples SCF Commands for Tandem FTAM This display shows that $FTR1 is running as a NonStop process pair in CPUs 1 and 2 on \MARS, with an execution priority of 142, and it is using the process code file \MARS.$SYSTEM.SYS00.FTAMROBJ. The following command displays detailed information on an FTAM initiator managed by the APLMGR process $AMGR and having the internal-name FTI1. This command is processed by APLMGR: INFO PROCESS \MARS.$AMGR.#FTAMI.
SCF Commands for Tandem FTAM INFO PROCESS Examples The following command displays detailed information on an FTAM responder named $FTR1. The command is processed directly by the responder process $FTR1: INFO PROCESS \MARS.$FTR1, DETAIL The following display is returned: OSIFTAM Detailed Info PROCESS \MARS.$FTR1 *CPU................ 1 *BackupCPU.... 3 *Priority........... 142 *Codefile..... \MARS.$SYSTEM.SYS00.FTAMROBJ *Swap............... \MARS.$DATA *Name......... \MARS.$FTR1 *Threshold..........
SCF Commands for Tandem FTAM INFO PROFILE INFO PROFILE The INFO PROFILE command displays the following information: • The current attribute settings configured for a virtual filestore (VFS) profile for an FTAM responder • The current information for an alternate collector (FTC) profile INFO PROFILE is a nonsensitive command. The INFO PROFILE command has the following syntax: INFO PROFILE [\system-name.]$appl-mgr-name. { #VFS.
INFO PROFILE Display Format With DETAIL (VFS Profiles) SCF Commands for Tandem FTAM If no DefUser is defined, that field displays NONE. An asterisk preceding the field name indicates that the field can be modified using the ALTER PROFILE command. See Section 4, Attributes for Tandem FTAM, for detailed descriptions of the configurable characteristics of Tandem FTAM objects.
INFO PROFILE Errors SCF Commands for Tandem FTAM INFO PROFILE Errors The following table lists the most common errors that can occur during the processing of the INFO PROFILE command: Message Definition Expecting an existing SCF supported object name or the character “(“ No APLMGR process by the specified name could be found.
INFO PROFILE Example SCF Commands for Tandem FTAM The display shows that VFS1 has a common name FTM1E, a default user ID FNET.CNFG, and no default password. The following display is returned if the OSI address components have been configured for the profile VFS1: OSIAPLMG *PSEL..... *SSEL..... *TSEL..... *NSAP..... Info PROFILE \MARS.$AMGR.#VFS.VFS1 01 0110 07 03 *ComName.. *DefUser.. FNET.
INFO SUBSYS SCF Commands for Tandem FTAM INFO SUBSYS The INFO SUBSYS command displays the current attribute values for the specified APLMGR subsystem. INFO SUBSYS is a nonsensitive command. The INFO SUBSYS command has the following syntax: INFO SUBSYS [\system-name.]$appl-mgr-name [ , DETAIL ] \system-name identifies the system in which the APLMGR process is running. $appl-mgr-name specifies the APLMGR process whose configuration you wish to view.
SCF Commands for Tandem FTAM INFO SUBSYS Display Format With DETAIL INFO SUBSYS Display Format With DETAIL The INFO SUBSYS screen display with the DETAIL option has the following format: OSIAPLMG Detailed Info SUBSYS \system.$appl-mgr-name *MaxFTAMI..... nnn *MaxFTAMR..... nnn Current FTAMI... nnn Current FTAMR... nnn *FTAMIfile...... \aaaaaaa.$aaaaaaa.aaaaaaaa.aaaaaaaa *FTAMRfile...... \aaaaaaa.$aaaaaaa.aaaaaaaa.aaaaaaaa *MIB............... \aaaaaaa.$aaaaaa.aaaaaaaa.aaaaaaaa *OMGRNAME..........
INFO SUBSYS Errors SCF Commands for Tandem FTAM INFO SUBSYS Errors The following table lists the most common errors that can occur during the processing of the INFO SUBSYS command: Message Description Expecting an existing SCF supported object name or the character “(“ No APLMGR process by the specified name could be found.
INFO SUBSYS Examples SCF Commands for Tandem FTAM The following command displays detailed information on the subsystem configuration: INFO SUBSYS \MARS.$AMGR, DETAIL The following display is returned: OSIAPLMG Detailed Info SUBSYS \MARS.$AMGR *MaxFTAMI..... 32 *MaxFTAMR..... 128 Current FTAMI... 2 Current FTAMR... 2 *FTAMIfile...... \MARS.$SYSTEM.SYS00.FTAMIOBJ *FTAMRfile...... \MARS.$SYSTEM.SYS00.FTAMROBJ *MIB............... \MARS.$DATA.FTMENV.ZOSADB *OMGRNAME.......... \NET.
LISTOPENS PROCESS SCF Commands for Tandem FTAM LISTOPENS PROCESS The LISTOPENS PROCESS command displays information on all currently existing opens to an APLMGR, initiator, or responder process. LISTOPENS PROCESS is a nonsensitive command. The LISTOPENS PROCESS command has the following syntax: LISTOPENS PROCESS [\system-name.]{$appl-mgr-name } {$process-name } \system-name identifies the system in which the specified process is running.
LISTOPENS PROCESS Display Format (Initiator or Responder) SCF Commands for Tandem FTAM Backup Opener PID is the process ID of the process that has a backup open against the process. In this version of Tandem FTAM, this field always contains NONE. FNUM is the file number associated with the opener of a process. Reqs is the number of current I/O requests outstanding for a given opener.
LISTOPENS PROCESS Errors SCF Commands for Tandem FTAM LISTOPENS PROCESS Errors The following table lists the most common errors that can occur during the processing of the LISTOPENS PROCESS command: Message Description Expecting an existing SCF supported object name or the character “(“ No process by the specified name could be found.
SCF Commands for Tandem FTAM LISTOPENS PROCESS Examples This display shows, for example, that the SCP process ($ZNET) currently has an open to $AMGR. This is the only valid open for $AMGR. The display also shows that there is one outstanding request to $AMGR. The following example requests a list of the current opens to an initiator named $FTI1: LISTOPENS PROCESS \MARS.$FTI1 This command displays the following information. A similar display is returned for a responder: OSIFTAM Listopens PROCESS \MARS.
LISTOPENS SU SCF Commands for Tandem FTAM LISTOPENS SU The LISTOPENS SU command displays information on each application process that has opened the specified initiator subdevice. LISTOPENS SU is a nonsensitive command. The LISTOPENS SU command has the following syntax: LISTOPENS SU [\system-name.]$process-name.#su-name \system-name identifies the system in which the specified process is running.
LISTOPENS SU Consideration SCF Commands for Tandem FTAM FNUM is the file number associated with the opener of a subdevice. Reqs is the number of current I/O requests outstanding for a given opener. LISTOPENS SU Consideration The LISTOPENS SU command is not valid for subdevices of an FTAM responder process. If issued for a responder subdevice, the command is rejected.
LISTOPENS SU Examples SCF Commands for Tandem FTAM For more information on errors specific to APLMGR (OSIAPLMG errors having positive error numbers), see Appendix B, SCF Error Messages for the APLMGR Subsystem. For more information on errors specific to FTAM (OSIFTAM errors having positive error numbers), see Appendix C, SCF Error Messages for the FTAM Subsystem.
SCF Commands for Tandem FTAM NAMES null NAMES null The NAMES null command displays the name of the specified object and the names of the objects controlled by it. NAMES null is a nonsensitive command. The NAMES null command does not contain null in the command string. It has the following syntax: NAMES [\system-name.]{$appl-mgr-name } {$process-name } \system-name identifies the system in which the specified process is running.
NAMES null Display Format (Initiator or Responder) SCF Commands for Tandem FTAM NAMES null Display Format (Initiator or Responder) For an initiator or a responder process, the NAMES null display shows the name of the process and the names of the subdevices associated with the process: OSIFTAM Names \system.$process-name PROCESS $process-name SU $process-name.#su-name $process-name.#su-name $process-name.
NAMES null Examples SCF Commands for Tandem FTAM For more information on errors specific to APLMGR (OSIAPLMG errors having positive error numbers), see Appendix B, SCF Error Messages for the APLMGR Subsystem. For more information on errors specific to FTAM (OSIFTAM errors having positive error numbers), see Appendix C, SCF Error Messages for the FTAM Subsystem.
SCF Commands for Tandem FTAM NAMES PROCESS NAMES PROCESS The NAMES PROCESS command displays various subsets of the processes controlled by the process that you specify. NAMES PROCESS is a nonsensitive command. The NAMES PROCESS command has the following syntax: NAMES PROCESS [\system-name.]{$appl-mgr-name {$appl-mgr-name.*[.*] {$appl-mgr-name.#proc-type.* {indirect-process-name {$process-name } } } } } \system-name identifies the system in which the specified process is running.
NAMES PROCESS Display Format SCF Commands for Tandem FTAM NAMES PROCESS Display Format The following table summarizes the information displayed when you use the above alternatives for naming the target process. NAMES PROCESS Display Returned $appl-mgr-name APLMGR name you entered $appl-mgr-name.*[.*] Names of all known initiator and responder processes controlled by the specified APLMGR process $appl-mgr-name.#proc-type.
SCF Commands for Tandem FTAM NAMES PROCESS Consideration The fourth syntax option displays only the name of the specified initiator or responder process, as follows: OSIAPLMG Names PROCESS \system.indirect-process-name PROCESS $appl-mgr-name.#FTAMI.internal-name or $appl-mgr-name.#FTAMR.internal-name Similarly, the fifth syntax option generates the following display: OSIFTAM Names PROCESS \system.
NAMES PROCESS Errors SCF Commands for Tandem FTAM NAMES PROCESS Errors The following table lists the most common errors that can occur during the processing of the NAMES PROCESS command: Message Description Expecting an existing SCF supported object name or the character “(” No process by the specified name could be found.
NAMES PROCESS Examples SCF Commands for Tandem FTAM NAMES PROCESS Examples The following example displays a list of all known processes of all process types for the APLMGR process named $AMGR on the \MARS system: NAMES PROCESS \MARS.AMGR.*.* The following display is returned: OSIAPLMG Names PROCESS \MARS.$AMGR.*.* PROCESS $AMGR $AMGR.#FTAMI.FTI2 $AMGR.#FTAMI.FTI1 $AMGR.#FTAMR.FTR1 $AMGR.#FTAMR.FTR2 The following example returns the names of all responder processes managed by $AMGR: NAMES PROCESS \MARS.
SCF Commands for Tandem FTAM NAMES PROFILE NAMES PROFILE The NAMES PROFILE command displays the name of the alternate collector (FTC) profile or the names of one or all of the virtual filestore (VFS) profiles controlled by the APLMGR subsystem. NAMES PROFILE is a nonsensitive command. The NAMES PROFILE command has the following syntax: NAMES PROFILE [\system-name.]{$appl-mgr-name.*[.*] } {$appl-mgr-name.#VFS.* } {$appl-mgr-name.#VFS.profile-name } {$appl-mgr-name.
NAMES PROFILE Display Format SCF Commands for Tandem FTAM NAMES PROFILE Display Format The first and second syntax options display all known FTC and VFS profiles controlled by the specified APLMGR process: OSIAPLMG Names PROFILE \system.$appl-mgr-name.*.* PROFILE $appl-mgr-name.#VFS.profile-name-1 $appl-mgr-name.#FTC $appl-mgr-name.#VFS.profile-name-2 OSIAPLMG Names PROFILE \system.$appl-mgr-name.#VFS.* PROFILE $appl-mgr-name.#VFS.profile-name-1 $appl-mgr-name.#VFS.
NAMES PROFILE Examples SCF Commands for Tandem FTAM For more information on errors specific to APLMGR (OSIAPLMG errors having positive error numbers), see Appendix B, SCF Error Messages for the APLMGR Subsystem. For more information on common SCF error messages (errors having negative error numbers), see the Subsystem Control Facility (SCF) Reference Manual (for D-series releases) or the SCF Reference Manual for G-Series Releases.
SCF Commands for Tandem FTAM NAMES SU NAMES SU The NAMES SU command displays the names of FTAM subdevices that are currently associated with the specified initiator or responder. NAMES SU is a nonsensitive command. The NAMES SU command has the following syntax: NAMES SU [\system-name.]{$process-name.#su-name } {$process-name.* } \system-name identifies the system in which the specified process is running.
NAMES SU Errors SCF Commands for Tandem FTAM NAMES SU Errors The following table lists the most common errors that can occur during the processing of the NAMES SU command: Message Description Expecting an existing SCF supported object name or the character “(“ No process by the specified name could be found.
NAMES SU Examples SCF Commands for Tandem FTAM NAMES SU Examples The following command returns the name of the subdevice for the responder named \MARS.FTR1. The display shows only the subdevice specified in the command: NAMES SU \MARS.$FTR1.#ZF00001 The following display is returned: OSIFTAM Names SU \MARS.$FTR1.#ZF00001 SU $FTR1.#ZF00001 The following command returns the names of all subdevices controlled by the FTAM responder \MARS.$FTR1: NAMES SU \MARS.$FTR1.
NAMES SUBSYS SCF Commands for Tandem FTAM NAMES SUBSYS The NAMES SUBSYS command displays the name of the specified APLMGR subsystem. This command is provided for conformance with SPI conventions for communications subsystems. NAMES SUBYS is a nonsensitive command. The NAMES SUBSYS command has the following syntax: NAMES SUBSYS [\system-name.]$appl-mgr-name \system-name identifies the system in which the APLMGR process is running.
SCF Commands for Tandem FTAM NAMES SUBSYS Examples NAMES SUBSYS Examples The following example illustrates how to confirm the name of the APLMGR process. NAMES SUBSYS \MARS.$AMGR The following display is returned: OSIAPLMG Names SUBSYS \MARS.$AMGR SUBSYS $AMGR This display simply echoes the name of the APLMGR process, $AMGR. It verifies that an APLMGR process by that name exists.
SCF Commands for Tandem FTAM START PROCESS START PROCESS The START PROCESS command initiates the operation of a specified process, placing it in the STARTED state. If the specified initiator or responder process does not exist, APLMGR creates the process and sends it a START PROCESS command. If the initiator or responder does exist, a START PROCESS command is routed to the specified process. START PROCESS is a sensitive command.
START PROCESS Errors SCF Commands for Tandem FTAM • • • • Before an initiator or a responder process can be started, it must first be defined in the APLMGR MIB by using the ADD PROCESS command. The START PROCESS command reads the definition in the MIB and uses that definition to create the process.
START PROCESS Examples SCF Commands for Tandem FTAM Message Description OSIFTAM E-00004 Command/object type combination is not valid for this subsystem You issued the command directly to the initiator or responder process. Use the indirect-process-name to specify the desired initiator or responder process. SCP E-00022 Security Violation for process-name You are not allowed to perform sensitive commands.
SCF Commands for Tandem FTAM STATS PROCESS STATS PROCESS The STATS PROCESS command displays accumulated statistics for the specified APLMGR, initiator, or responder process. STATS PROCESS is a sensitive command if RESET is specified. The STATS PROCESS command has the following syntax: STATS PROCESS [\system-name.]{$appl-mgr-name } [ , RESET ] {$process-name } \system-name identifies the system in which the specified process is running.
STATS PROCESS Display Format SCF Commands for Tandem FTAM . OSIFTAM Stats PROCESS \system.$process-name Reset Time.......... dd Mmm yyyy, hh:mm:ss.sss Sample Time........ dd Mmm yyyy, hh:mm:ss.sss Open Control Blocks: InUse.......... nnnn MaxInUse......... nnnn Request Control Blocks: InUse.......... nnnn MaxInUse......... nnnn File System Requests: Open.............. nnnnnnnnnnD ResetSYNC..... nnnnnnnnnnD Control........... nnnnnnnnnnD Setmode......... nnnnnnnnnnD DeviceInfo.....
STATS PROCESS Errors SCF Commands for Tandem FTAM File System Requests is the number of requests of each type received by a specified process.
STATS PROCESS Examples SCF Commands for Tandem FTAM STATS PROCESS Examples To reset the statistical counters for the APLMGR process named $AMGR on the \MARS system, you can issue the following command: STATS PROCESS \MARS.$AMGR, RESET You can request statistical information for the APLMGR process named $AMGR as follows: STATS PROCESS \MARS.$AMGR Both commands return the following display: OSIAPLMG Stats PROCESS \MARS.$AMGR Reset Time..... 22 Apr 1999, 13:57:24.493 Sample Time.... 22 Apr 1999, 14:38:08.
STATS PROCESS Examples SCF Commands for Tandem FTAM The following command displays statistical information on an initiator process named $FTI1 on the \MARS system, and then resets the statistical counters to zero: STATS PROCESS \MARS.$FTI1, RESET The following display is returned: OSIFTAM Stats PROCESS \MARS.$FTI1 Reset Time..... 22 Apr 1999, 13:57:24.493 Sample Time.... 22 Apr 1999, 14:38:08.537 Open Control Blocks: InUse.......... 4 MaxInUse....... 10 Request Control Blocks: InUse..........
STATS SU SCF Commands for Tandem FTAM STATS SU The STATS SU command displays accumulated statistics for the specified FTAM subdevice. The following information is displayed: reset time, sample time, number of application protocol data units (APDUs) sent, and number of APDUs received. STATS SU is a sensitive command if RESET is specified. The STATS SU command has the following syntax: STATS SU [\system-name.]$process-name.
SCF Commands for Tandem FTAM STATS SU Display Format The following fields display information that is not directly configurable using SCF object attributes: Reset Time is the date and time that the statistical counters were last reset. APDUs sent is the number of application protocol data units (APDUs) sent from the specified SU object to the remote entity. The count includes all ACSE and presentation protocol data units (PDUs) created to support the FTAM protocol.
STATS SU Errors SCF Commands for Tandem FTAM STATS SU Errors The following table lists the most common errors that can occur during the processing of the STATS SU command: Message Description Expecting an existing SCF supported object name or the character “(” No process by the specified name could be found.
STATS SU Examples SCF Commands for Tandem FTAM STATS SU Examples The following command displays statistics for the subdevice named #ZF00001 associated with the responder process named $FTR1 on the \MARS system: STATS SU \MARS.$FTR1.#ZF00001 The following display is returned: OSIFTAM Stats SU \MARS.$FTR1.#ZF00001 Reset Time..... 22 Apr 1999, 13:57:24.493 Sample Time.... 22 Apr 1999, 14:38:08.537 APDUs sent...... 1D APDUs rcvd......
STATS SUBSYS SCF Commands for Tandem FTAM STATS SUBSYS The STATS SUBSYS command displays accumulated statistics for the specified APLMGR subsystem. STATS SUBSYS is a sensitive command if RESET is specified. The STATS SUBSYS command has the following syntax: STATS SUBSYS [\system-name.]$appl-mgr-name [ , RESET ] \system-name identifies the system in which the APLMGR process is running. $appl-mgr-name specifies the APLMGR process about which you require statistical information.
SCF Commands for Tandem FTAM STATS SUBSYS Consideration Sample Time is the date and time that the statistics were gathered. Configuration is the current configuration information for each subcategory. Two types of configuration information are displayed: Current is the number of each type of process and profile that currently exists. MaximumEver is the maximum number of each type of process and profile that have existed simultaneously.
STATS SUBSYS Errors SCF Commands for Tandem FTAM STATS SUBSYS Errors The following table lists the most common errors that can occur during the processing of the STATS SUBSYS command: Message Description Expecting an existing SCF supported object name or the character “(” No APLMGR process by the specified name could be found.
SCF Commands for Tandem FTAM STATS SUBSYS Example This display shows, for example, that the $AMGR configuration currently includes two initiators, two responders, and one VFS profile; there have never been more than two initiators or two responders configured at the same time. It also shows that the statistics for the subsystem were reset very recently—approximately two minutes before this command was issued—using the STATS SUBSYS command with the RESET option.
SCF Commands for Tandem FTAM STATUS PROCESS STATUS PROCESS The STATUS PROCESS command displays information on the status of the specified process. STATUS PROCESS is a nonsensitive command. The STATUS PROCESS command has the following syntax: STATUS PROCESS [\system-name.]{$appl-mgr-name } {indirect-process-name } {$process-name } [ , DETAIL ] \system-name identifies the system in which the specified process is running. $appl-mgr-name identifies the APLMGR process whose status you wish to view.
STATUS PROCESS Display Format (APLMGR) SCF Commands for Tandem FTAM STATUS PROCESS Display Format (APLMGR) The screen display for the STATUS PROCESS command without the DETAIL option generates the following display for an APLMGR process: OSIAPLMG Status PROCESS \system.$appl-mgr-name Name \system.
STATUS PROCESS Display Format With DETAIL (APLMGR) SCF Commands for Tandem FTAM STATUS PROCESS Display Format With DETAIL (APLMGR) The STATUS PROCESS command with the DETAIL option generates the following display for an APLMGR process if the trace option is set to OFF: OSIAPLMG Detailed Status PROCESS \system.$appl-mgr-name State.............. PPID............... Ownerid............ Stopopens.......... aaaaaaaaaa nn,nnn nnn,nnn aaa BPID............... nn,nnn Opens.............. nnnnn Trace.............
STATUS PROCESS Display Format (Initiator or Responder) SCF Commands for Tandem FTAM STATUS PROCESS Display Format (Initiator or Responder) The STATUS PROCESS command without the DETAIL option generates the following display for either an initiator or a responder process specified by indirect-process-name: OSIAPLMG Status PROCESS \system.
SCF Commands for Tandem FTAM STATUS PROCESS Considerations STATUS PROCESS Considerations • • If you specify indirect-process-name, the command is sent to the APLMGR process, which in turn routes it to the specified initiator or responder process. If you specify $process-name, the command goes directly to the specified initiator or responder. If the command with the DETAIL option is issued directly to an initiator or a responder process, an additional field, OSIAPLMG Internal Name, is displayed.
STATUS PROCESS Examples SCF Commands for Tandem FTAM STATUS PROCESS Examples The following command displays the status of the APLMGR process named $AMGR on the \MARS system: STATUS PROCESS \MARS.$AMGR The following display is returned: OSIAPLMG Status PROCESS \MARS.$AMGR Name \MARS.
STATUS PROCESS Examples SCF Commands for Tandem FTAM The following example displays status information collected directly from a responder process named $FTR1 on the \MARS system: STATUS PROCESS \MARS.$FTR1 The following display is returned: OSIFTAM Status PROCESS \MARS.$FTR1 Name State PPID BPID OwnerID \MARS.
SCF Commands for Tandem FTAM STATUS SU STATUS SU The STATUS SU command displays the following information on an FTAM subdevice: state of the subdevice, number of requests, last error code and subcode, local PSAP and functional units, remote PSAP and functional units, and associated TAPS subdevice name. STATUS SU is a nonsensitive command. The STATUS SU command has the following syntax: STATUS SU [\system-name.]$process-name.
STATUS SU Display Format SCF Commands for Tandem FTAM STATUS SU Display Format The STATUS SU display without the DETAIL option has the following format for either an FTAM initiator or an FTAM responder subdevice: OSIFTAM Status SU \system.$process-name.#su-name Name \system.$process-name.
STATUS SU Display Format With DETAIL SCF Commands for Tandem FTAM STATUS SU Display Format With DETAIL The STATUS SU display with the DETAIL option has the following format for an FTAM initiator process. The display for an FTAM responder is similar except that the REMOTE and LOCAL designations on the addresses are changed in some cases, and the Responding Address fields are not displayed. OSIFTAM Detailed Status SU State Opens Error Error ............ ............ ............ Subcode..... CEPI ........
SCF Commands for Tandem FTAM STATUS SU Consideration FTAM Functional Units Selected are the functional units negotiated for the association between the calling and the responding addresses for an initiator subdevice, or between the calling and the called addresses for a responder subdevice. Calling Address is the OSI address of the initiator requesting the association.
Status SU Errors SCF Commands for Tandem FTAM Status SU Errors The following table lists the most common errors that can occur during the processing of the STATUS SU command: Message Description Expecting an existing SCF supported object name or the character “(” No process by the specified name could be found.
STATUS SU Examples SCF Commands for Tandem FTAM STATUS SU Examples The following command displays status information on subdevice #Z000001 associated with responder $FTR1 on the \NET system: STATUS SU \NET.$FTR1.#ZF00001 This command returns the following display: OSIFTAM Status SU \NET.$FTR1.#ZF00001 Name \NET.$FTR1.
SCF Commands for Tandem FTAM STATUS SUBSYS STATUS SUBSYS The STATUS SUBSYS command displays information on the status of the specified APLMGR subsystem; it returns the number of configured processes and started processes. STATUS SUBSYS is a nonsensitive command. The STATUS SUBSYS command has the following syntax: STATUS SUBSYS [\system-name.]$appl-mgr-name [ , DETAIL ] \system-name identifies the system in which the APLMGR process is running.
STATUS SUBSYS Display Format SCF Commands for Tandem FTAM STATUS SUBSYS Display Format The screen display returned by the STATUS SUBSYS command without the DETAIL option has the following format: OSIAPLMG Status SUBSYS \system.
STATUS SUBSYS Display Format With DETAIL SCF Commands for Tandem FTAM STATUS SUBSYS Display Format With DETAIL The screen display returned by the STATUS SUBSYS command with the DETAIL option has the following format: OSIAPLMG Detailed Status SUBSYS \system.$appl-mgr-name Primary.......... nn,nnn Subsystem Owner.. nnn,nnn Backup.......... nn,nnn MIB State........ aaaaaa FTAMIs Configured.. FTAMRs Configured.. nnn nnn FTAMIs Started..... FTAMRs Started..... nnn nnn Total Openers......
STATUS SUBSYS Errors SCF Commands for Tandem FTAM FTAMRs Started is the number of FTAM responder processes actually started. Total Openers is the current number of processes that have opened the APLMGR process. To determine which processes, issue the LISTOPENS command. For more information, see the LISTOPENS command. SUBSYS State is the state of the subsystem object. This field always contains Defined, because the APLMGR process can process the command only when the state of the subsystem is DEFINED.
STATUS SUBSYS Examples SCF Commands for Tandem FTAM STATUS SUBSYS Examples To view the status of the subsystem managed by the APLMGR process named $AMGR in the \MARS system, issue the command: STATUS SUBSYS \MARS.$AMGR The following display is returned: OSIAPLMG Status SUBSYS \MARS.$AMGR Name $AMGR FTAMI FTAMR (cfg/str) (cfg/str) SUBSYS State ( 2/2 ) ( 2/2 ) Defined The display shows that two initiators and two responders are configured for $AMGR and that all of them have been started.
SCF Commands for Tandem FTAM STOP PROCESS STOP PROCESS The STOP PROCESS command terminates the operation of a process, placing it in the STOPPED state, if no work is currently in progress using that process. STOP PROCESS is a sensitive command. The STOP PROCESS command has the following syntax: STOP PROCESS [\system-name.]{$appl-mgr-name } {indirect-process-name } \system-name identifies the system in which the APLMGR process is running. $appl-mgr-name identifies the APLMGR process you want to stop.
STOP PROCESS Considerations SCF Commands for Tandem FTAM • • • When you are using command files, you might want to follow this command with a DELAY command having a time value of approximately five to ten seconds. This procedure is necessary only if the command following the STOP PROCESS command expects the process to be in the STOPPED state.
SCF Commands for Tandem FTAM STOP PROCESS Examples STOP PROCESS Examples You can use the following command to stop an APLMGR process on the \MARS system named $AMGR: STOP PROCESS \MARS.$AMGR To stop a responder process named FTR1 that is controlled by $AMGR, issue the following command: STOP PROCESS \MARS.$AMGR.#FTAMR.
SCF Commands for Tandem FTAM STOPOPENS PROCESS STOPOPENS PROCESS The STOPOPENS PROCESS command configures an FTAM initiator process to reject open requests from applications. This is a sensitive command. The STOPOPENS PROCESS command has the following syntax: STOPOPENS PROCESS [\system-name.]{$process-name } {indirect-process-name } \system-name identifies the system in which the specified process is running.
STOPOPENS PROCESS Errors SCF Commands for Tandem FTAM STOPOPENS PROCESS Errors The following table lists the most common errors that can occur during the processing of the STOPOPENS PROCESS command: Error Message Definition Expecting an existing SCF supported object name or the character “(“ No initiator process by the specified name could be found.
STOPOPENS PROCESS Examples SCF Commands for Tandem FTAM Error Message Definition CP E-00022 Security Violation for process-name You are not allowed to perform sensitive commands. For further information on sensitive commands, see Sensitive and Nonsensitive Commands on page 1-9. OSIFTAM E00005 Command not valid for responder process or OSIAPLMG E00005 Command not valid for responder process The specified process was an FTAM responder process (but must be an FTAM initiator process).
SCF Commands for Tandem FTAM SUSPEND PROCESS SUSPEND PROCESS The SUSPEND PROCESS command places a process in the SUSPENDED state, thereby preventing it from processing information other than DSM messages. This is a sensitive command. The SUSPEND PROCESS command has the following syntax: SUSPEND PROCESS [\system-name.]{$appl-mgr-name } {indirect-process-name } \system-name identifies the system in which the specified process is running. $appl-mgr-name identifies the APLMGR process you wish to suspend.
SUSPEND PROCESS Errors SCF Commands for Tandem FTAM SUSPEND PROCESS Errors The following table lists the most common errors that can occur during the processing of the SUSPEND PROCESS command: Error Message Description Expecting an existing SCF supported object name or the character “(“ No APLMGR process by the specified name could be found.
TRACE PROCESS SCF Commands for Tandem FTAM TRACE PROCESS The TRACE PROCESS command starts, modifies, or stops the collection of trace information during the operation of the specified process. TRACE PROCESS is a sensitive command. You can use the PTrace utility to select, format, and display data collected during a trace. See Section 5, PTrace Reference for Tandem FTAM, for information on trace records of APLMGR, initiator, or responder process activity.
SCF Commands for Tandem FTAM TRACE PROCESS trace-option is one of the following trace options, which modify the trace operation: COUNT count specifies the number of trace records to be captured. If you do not specify this option, or specify it as -1, records are accumulated until the trace is stopped. This option has a value ranging between -1 and 32,767. NOCOLL indicates that you wish to trace the specified process without initiating a trace collector process.
TRACE PROCESS SCF Commands for Tandem FTAM SELECT select-spec specifies the type of activity you wish to trace; it consists of one or more keywords in the following form: { keyword } ( keyword [ , keyword ]... ) } keyword Initiator X X X X X X X X Responder X X X X X X X X APLMGR X X X X USER SYSMSG SM PROV MSG‘ MEM DSM ASN1 Process ALL is one of the following keywords.
SCF Commands for Tandem FTAM TRACE PROCESS PROV specifies tracing of all application and presentation protocol data units of the provider interface. This keyword applies only when tracing an initiator or a responder process. SM specifies tracing of protocol state-machine information. This keyword applies only when tracing an initiator or a responder process. SYSMSG specifies tracing of system messages. This keyword applies when tracing all processes—initiator, responder, and APLMGR.
SCF Commands for Tandem FTAM TRACE PROCESS Considerations TRACE PROCESS Considerations • • • To start a new trace, issue a TRACE command that includes the TO filename option. When you specify TO filename, a new trace is initiated unless the file name is invalid, the file cannot be opened, or tracing is already active for the specified process. A process can have only one trace active at a time.
TRACE PROCESS Errors SCF Commands for Tandem FTAM Error Message Description { OSIAPLMG E-00814 | OSIFTAM E-00814 } Trace is not active for $process-name You attempted to stop a trace (by specifying the STOP option) or modify a trace (by omitting both STOP and TO), but no trace was in progress. { OSIAPLMG E-00822 | OSIFTAM E-00822 } Trace is currently active for $process-name You attempted to start a trace (by specifying the TO option) while a trace was in progress.
SCF Commands for Tandem FTAM TRACE PROCESS Examples TRACE PROCESS Examples You can use the following command to trace all aspects of an APLMGR process on the \MARS system named $AMGR and store information in the file TRACE01: TRACE PROCESS \MARS.$AMGR, RECSIZE 4050 & , TO \MARS.$DATA.SYS00.TRACE01 Because no SELECT option was specified in this example, the command defaults to SELECT ALL.
SCF Commands for Tandem FTAM VERSION null VERSION null The VERSION null command displays information on product numbers and release dates for the specified APLMGR, initiator, or responder process. VERSION null is a nonsensitive command. The VERSION null command does not contain null in the command string. It has the following syntax: VERSION [\system-name.]{$appl-mgr-name } {$process-name [ , DETAIL ] } \system-name identifies the system in which the specified process is running.
SCF Commands for Tandem FTAM VERSION null Display Format With DETAIL (APLMGR) VERSION null Display Format With DETAIL (APLMGR) For an APLMGR process, the VERSION null command with the DETAIL option returns the following display: Detailed VERSION \system.
VERSION null Consideration SCF Commands for Tandem FTAM VERSION null Consideration Omit the null object specification, and omit the object type, when issuing this command. VERSION null Errors The following table lists the most common errors that can occur during the processing of the VERSION null command: Error Message Description Expecting an existing SCF supported object name or the character “(“ No process by the specified name could be found.
SCF Commands for Tandem FTAM VERSION null Examples The following example displays detailed version information for the APLMGR process named $AMGR: VERSION \MARS.$AMGR, DETAIL The following display is returned: Detailed VERSION \MARS.
SCF Commands for Tandem FTAM VERSION SUBSYS VERSION SUBSYS The VERSION SUBSYS command displays information on product codes and release dates for the specified APLMGR subsystem. VERSION SUBSYS is a nonsensitive command. The VERSION SUBSYS command has the following syntax: VERSION SUBSYS [\system-name.]$appl-mgr-name [ , DETAIL ] \system-name identifies the system in which the specified process is running. $appl-mgr-name identifies the APLMGR process for which you are requesting product information.
VERSION SUBSYS Errors SCF Commands for Tandem FTAM VERSION SUBSYS Errors The following table lists the most common errors that can occur during the processing of the VERSION SUBSYS command: Error Message Description Expecting an existing SCF supported object name or the character “(“ No APLMGR process by the specified name could be found.
4 Attributes for Tandem FTAM This section describes the attributes of Tandem FTAM objects. The section contains the following topics: • • Categories (functional groupings) of attributes are described in Attribute Categories (on this page). Each attribute is described, in alphabetical order, in Attribute Descriptions (beginning on page 4-2). Attribute Categories Table 4-1 contains functional groupings of the attributes used in the SCF commands for Tandem FTAM.
Attribute Descriptions Attributes for Tandem FTAM Attribute Descriptions Attributes are the configurable characteristics of objects—characteristics that are intentionally assigned rather than those that change outside the user’s control (such as reset time or the current number of openers). They are used in Tandem FTAM as parameters in, and display fields returned by, SCF commands.
ALLOWSU Attributes for Tandem FTAM Priority of address Over COMNAME If both a common name and an address (a PSEL, an SSEL, a TSEL, and an NSAP group) for a process exist in the APLMGR MIB, both are included in the APS register request sent to the OSI manager process. When this occurs, the OSI manager process uses the OSI address—the address components override the common name.
CODEFILE Attributes for Tandem FTAM CODEFILE Default: See description Value: Standard file-naming conventions Objects: PROCESS CODEFILE identifies the FTAM initiator code file or FTAM responder code file to be executed when APLMGR starts the process. If CODEFILE is provided but is not a fully qualified Guardian filename, the filename is expanded using the current SCF system, volume, and subvolume. The expansion also depends on the _SCF_SEARCH DEFINE of class SEARCH.
COMNAME Attributes for Tandem FTAM COMNAME Default: None Value: Maximum length of this string is 64 characters—alphanumeric plus the characters ^, _, and - Objects: PROCESS, PROFILE COMNAME identifies the default common name that the OSI manager process uses to look up, in its MIB, the address of an FTAM initiator or responder process. You must specify either COMNAME "character-string" or an address (a PSEL, an SSEL, a TSEL, and an NSAP group) for the initiator or responder process.
CPU Attributes for Tandem FTAM CPU Default: CPU in which the primary APLMGR process is running at the time the command is executed Value: Integer, 0 through 15 Objects: PROCESS CPU specifies the CPU in which the primary process of a process pair is to run when the process is started, or is currently running. The value specified must represent a valid CPU number in this Tandem system. The CPU for the APLMGR process is specified in the RUN command.
EVENTDESTINATION Attributes for Tandem FTAM If You Configure the DEFUSER Attribute To specify a default user ID and password, you use the DEFUSER attribute in your VFS PROFILE configuration. If you provide a user ID (as either groupid.userid or groupnum.usernum) and password in this attribute, remote users do not need to send user IDs and passwords across the OSI network to access a responder process using its address.
FTAMIFILE Attributes for Tandem FTAM FTAMIFILE Default: FTAMIOBJ, with the same volume and subvolume names as the APLMGR code file Value: See description Objects: SUBSYS FTAMIFILE specifies the fully qualified filename of the default FTAM initiator code file used when CODEFILE is not specified in the ADD PROCESS command. If FTAMIFILE is provided but is not a fully qualified Guardian filename, the filename is expanded using the current SCF system, volume, and subvolume.
MAXASSOC Attributes for Tandem FTAM MAXASSOC Default: 8 Value: Integer, 1 to 32 Objects: PROCESS MAXASSOC specifies the maximum number of parallel associations allowed within a process. MAXATTACH Default: 8 or the value of MAXASSOC, whichever is lower Value: Integer, 1 to the value specified for MAXASSOC Objects: PROCESS MAXATTACH specifies the maximum number of responder subdevices available at one time for new association requests.
MIB Attributes for Tandem FTAM MIB Default: ZOSADB with the same volume and subvolume names as the SCF system Value: See description Objects: SUBSYS MIB is the fully qualified filename of the APLMGR management information (configuration) database. If the MIB attribute is provided but the name is not a fully qualified Guardian filename, the filename provided is expanded using the current SCF system, volume, and subvolume.
NSAP Attributes for Tandem FTAM NSAP Default: None Value: Even number of hexadecimal characters—maximum length of 40 Objects: PROCESS, PROFILE, SU NSAP defines the network service access point (NSAP) address for an FTAM initiator process or VFS profile. See address on page 4-2. The NSAP is a binary-encoded string. It is entered as a string of an even number of hexadecimal characters—maximum length of 40 hexadecimal characters. NSAP addresses are administered by a centralized addressing authority.
PROFILE Attributes for Tandem FTAM PROFILE Default: None Value: See description Objects: PROFILE, PROCESS PROFILE specifies the name of a VFS profile associated with an FTAM responder process or an alternate event collector (FTC) profile. PSEL Default: None Value: Even number of hexadecimal characters—maximum length of 32 Objects: PROCESS, PROFILE, SU PSEL defines the presentation selector for an FTAM initiator process or VFS profile. See address on page 4-2.
SSEL Attributes for Tandem FTAM SSEL Default: None Value: Even number of hexadecimal characters—maximum length of 32 Objects: PROCESS, PROFILE, SU SSEL defines the session selector for an FTAM initiator process or VFS profile. See address on page 4-2. The SSEL is a binary-encoded string. It is entered as a string of an even number of hexadecimal characters—maximum length of 32 hexadecimal characters. Session selector values are locally administered.
THRESHOLD Attributes for Tandem FTAM THRESHOLD Default: None Value: Integer, 0 through 32,767 Objects: PROCESS THRESHOLD specifies the number of protocol errors that can occur before FTAM issues protocol-error event message 22. If the threshold is set to 0, protocol-event messages are not generated. For more information on the protocol-error threshold limit and the event-message returned, see the Operator Messages Manual.
5 PTrace Reference for Tandem FTAM This section provides information on the use of the PTrace utility to display information from the traces of APLMGR, initiator, and responder processes. PTrace formats the data that is stored in the unstructured trace files that you can create using the SCF TRACE command. These files contain records of the communications between processes.
PTrace Reference for Tandem FTAM TRACE and PTrace The order in which TRACE commands and PTrace commands are given is important. You must start and stop a trace before you use PTrace to view the collected trace records; you must start PTrace before you can issue PTrace commands. The order is as follows: 1. Start a trace using the SCF TRACE command.
Device Types and Subtypes PTrace Reference for Tandem FTAM Device Types and Subtypes When you create a trace file, the type and subtype of the device being traced are recorded in the file. PTrace displays this information in the first trace-file header record. Table 5-1 lists the device type and subtype numbers assigned to the APLMGR, initiator, and responder processes. Table 5-1.
Trace Record Types PTrace Reference for Tandem FTAM Figure 5-1. Traceable Tandem FTAM Activities 1 User Application 2 Tandem FTAM 8 Guardian operating system SCF 1 ALL 2 USER 3 PROV 4 ASN1 5 SM 6 DSM 7 MEM 8 MSG 9 SYSMSG 9 APLMGR 7 6 Responder 4 3 Initiator 5« 7 4 8 3 5 7 8 OSI/AS TAPS CDT 008.
PTrace Reference for Tandem FTAM Trace Record Size In addition, the USER records generated by initiator processes provide information on requests from the application program, which you can use to follow the flow and sequence of these requests.
PTrace Reference for Tandem FTAM PTrace Commands PTrace Commands The EBCDIC, SETTRANSLATE, and TRANSLATE commands have no effect. All other commands are implemented in the standard format. The PTrace DETAIL option is issued with PTrace commands for FTAM processes (initiators and responders) to display detailed PDU or internal-format data. The file ZFTMSMT is provided in the software release subvolume ZOSIFTAM to use as input to the STATETABLES command.
PTrace Reference for Tandem FTAM SELECT Command Table 5-2.
PTrace Reference for Tandem FTAM SELECT Command The following command collects information on all activity of the FTAM initiator $FTM1 on the \MARS system, sets a trace file record size of 2000 bytes, and stores the trace in the file named TRACE01 on the same system: TRACE PROCESS \MARS.$FTM1, SELECT ALL , RECSIZE 2000 , TO TRACE01 & & When you have collected the data you want, use the following command to stop the trace: TRACE PROCESS \MARS.
PTrace Reference for Tandem FTAM FILTER Command In the above example, only DSM records were written to the trace file. Therefore, the DSM keyword does not need to be repeated in the PTrace command. FILTER Command The PTrace FILTER command allows you to more narrowly define the trace information to be displayed from PROV, ASN1, and USER trace records generated by initiator and responder processes. It allows you to select records for display according to the content of the record.
PTrace Reference for Tandem FTAM FILTER Command Table 5-3 identifies the available FILTER options. Table 5-3. FILTER Options for Initiator and Responder Process Traces Option Description of Records Displayed SU [su-name] Records containing the specific subdevice that you named. Records containing only the ASN1 Encode subtype. Records containing all ASN1 subtypes except the ASN1 Encode subtype. ASN1ENC NOASN1ENC ASN1DEC NOASN1DEC PROV [primitive-type] Records containing only the ASN1 Decode subtype.
PTrace Reference for Tandem FTAM Trace-Record Formats To display all provider records related to associate or attach operations, use the following PTrace command: FROM TRACE01;SELECT PROV;FILTER PROV CONNECT To display messages for all ASN1 subtypes except the ASN1 Decode subtype, use the following PTrace command: FROM TRACE01;SELECT ASN1;FILTER NOASN1DEC Trace-Record Formats A trace file contains a trace file header record followed by one or more trace records.
PTrace Reference for Tandem FTAM Trace File Header Record Trace File Header Record The file header record displays identification information specific to the trace file, as shown in the following example: Trace of: \NET.$AMGR, Type (55,20). Ptrace Data File: \NET.$SYSTEM.SYS00.TRACE01 Trace started: 09/23/93 10:30:50.338127 First trace entry: 09/23/93 10:30:50.466579 Last trace entry: 09/23/93 10:31:59.
PTrace Reference for Tandem FTAM Trace Record Header Trace Record Header Each trace record displayed is preceded by a header line of the following format, as shown in the following example: DateStamp TimeStamp >DeltaTime #TraceRecordNumber Type DateStamp is the date on which this trace record was captured. TimeStamp is the time at which this trace record was captured. DeltaTime is the amount of time, in microseconds, that has passed since the previous trace record was captured.
PTrace Reference for Tandem FTAM USER Event USER Event The following trace record displays the information the initiator returns to the user application. The initiator generates this trace record immediately after it receives the event. Asterisks denote additional information that is displayed when the PTrace DETAIL option is on. 09/23/93 10:39:30.253036 >000.
PTrace Reference for Tandem FTAM USER Reply USER Reply The following trace record displays the information returned by the initiator to the user application to notify the application that the request that was issued has been completed. This record is generated immediately after the user information is sent by the initiator. 09/23/93 10:39:29.188821 >000.
PTrace Reference for Tandem FTAM USER Request USER Request The following trace record displays the request issued by the user application to the initiator process, before it is encoded as a PDU and transmitted to the remote responder. The initiator generates this trace record immediately after it receives the event. Asterisks denote additional information that is displayed when the PTrace DETAIL option is on. 09/23/93 10:39:28.119243 >000.
PTrace Reference for Tandem FTAM PROV Reply Received Note that the ASI data format is intended for Tandem internal use and is not part of the OSI standards. PROV Reply Received The following trace record displays the reply returned from OSI/AS in response to a request sent by the Tandem initiator via the API. The initiator generates this trace record immediately after it receives the reply from OSI/AS. 09/23/93 10:31:21.581434 >001.
PTrace Reference for Tandem FTAM PROV Event Received PROV Event Received The following record indicates that an event was received by the Tandem initiator from OSI/AS. The initiator generates this trace record immediately after it receives the event. Asterisks denote additional information that is displayed when the PTrace DETAIL option is on. 09/23/93 10:31:22.642045 >001.
PTrace Reference for Tandem FTAM Original: Error Code x PROV Event Received Subcode x is the error code and subcode generated at the presumed source of the error—the source can be any of the underlying subsystems. See the Tandem OSI/FTAM Programming Reference Manual, the Tandem OSI/AS Programming Manual, or the OSI/TS Configuration and Management Manual for more information on error codes and subcodes. Current: Error Code x Subcode x is the APS error code and subcode returned by OSI/AS.
PTrace Reference for Tandem FTAM PROV Assoc Request PROV Assoc Request The following trace record displays an association request to be sent by the Tandem initiator to the remote responder via the API. The initiator generates this trace record immediately before the association request is issued to OSI/AS. Asterisks denote additional information that is displayed when the PTrace DETAIL option is on. 09/23/93 10:31:20.186746 >000.
PTrace Reference for Tandem FTAM PROV Assoc Request Status Code is the APS status code returned to the initiator from OSI/AS. See the Tandem OSI/AS Programming Manual for status code values. Original: Error Code x Subcode x is the error code and subcode generated at the presumed source of the error—the source can be any of the underlying subsystems.
PTrace Reference for Tandem FTAM PROV Release/Abort PROV Release/Abort The following trace record displays a release or an abort PDU to be sent by the Tandem initiator to the remote responder. The initiator generates the trace record immediately before the release or abort is issued to OSI/AS via the API. Asterisks denote additional information that is displayed when the PTrace DETAIL option is on. 9/23/93 10:31:33.852181 >011.
PTrace Reference for Tandem FTAM ACSE release reason x PROV Data Request result x is the cause and result of the release or abort by means of a reason code and a result code. See the Tandem OSI/AS Programming Manual for values of ZAPS-VAL-RLS-xxx, ZAPS-VAL-RLS-RSN-xxx, and ZAPS-VAL-ABORTxxx. PDU Length is the length of the protocol data unit (PDU), in bytes. PDU Data is a hexadecimal dump of the PDU, which is encoded using the Basic Encoding Rules (BER) guidelines.
PTrace Reference for Tandem FTAM Original: Error Code x ASN1 Encoding Input Subcode x is the error code and subcode generated at the presumed source of the error—the source can be any of the underlying subsystems. See the Tandem OSI/FTAM Programming Reference Manual, the Tandem OSI/AS Programming Manual, or the OSI/TS Configuration and Management Manual for more information on error codes and subcodes. Current: Error Code x Subcode x is the APS error code and subcode returned by OSI/AS.
PTrace Reference for Tandem FTAM ASN1 Encoding Input Service Code is a numeric code and text string that identifies the primitive for which information is being encoded. These values are also event codes.
PTrace Reference for Tandem FTAM Value/ Event Code Meaning 930 Read indication/request 931 Write indication/request 932 Data indication 933 Data end indication 934 Transfer end response/confirm 935 Transfer end indication/request 936 Cancel response/confirm 937 Cancel indication 938 File close response/confirm 939 File close indication/request 940 File open response/confirm 941 File open indication/request 946 Beginning group response/confirm 947 End group response/confirm ASN
PTrace Reference for Tandem FTAM ASN1 Encoding Output ASN1 Encoding Output The following trace record displays the PDU that results from the ASN1 encoding performed by the initiator or responder process prior to transfer across the network. The initiator or responder generates this trace record immediately after calling the ASN1 encoding routines. Asterisks denote additional information that is displayed when the PTrace DETAIL option is on. 09/23/93 10:31:20.181087 >000.
PTrace Reference for Tandem FTAM ASN1 Decoding Input ASN1 Decoding Input The following trace record displays the PDU that has been received from the underlying services and needs to be decoded to ASI data by the initiator or responder process. The initiator or responder generates the trace record immediately prior to calling the ASN1 decoding routines. Asterisks denote additional information that is displayed when the PTrace DETAIL option is on. 09/23/93 10:31:21.918543 >000.
PTrace Reference for Tandem FTAM ASN1 Decoding Output ASN1 Decoding Output The following record displays information decoded from the PDU transferred across the network. The initiator or responder generates the trace record immediately after calling the ASN1 decoding routines. Asterisks denote additional information that is displayed when the PTrace DETAIL option is on. 09/23/93 10:31:22.652272 >000.
PTrace Reference for Tandem FTAM SM FTAM State Machine SM FTAM State Machine The following trace record is generated by an initiator or responder process immediately after a state transition is completed. A state transition can occur in any of the named Tandem FTAM state machines. 09/23/93 10:31:22.679476 >002.492482 #81 SM Name Responder CS Su Name #ZF00002 State 3 Event 3 Action 6 Previous State 2 FTAM SM SM Name is the state machine.
PTrace Reference for Tandem FTAM SM FTAM State Machine You can use the PTrace STATETABLES command to identify the states, events, actions, and previous states returned in the FTAM State Machine record. This command allows PTrace access to the state-machine tables for the initiator or responder. For example, the command ?STATETABLES \MARS.$DATA.ZOSIFTM.ZFTMSMT identifies the statetable \MARS.$DATA.ZOSIFTM.ZFTMSMT.
PTrace Reference for Tandem FTAM DSM Decode SPI Request DSM Decode SPI Request The following trace record is generated immediately after a Subsystem Programmatic Interface (SPI) request is decoded. 09/23/93 10:30:50.466579 >000.000000 #1 Decode SPI Req State: 9 SPI Error: 0 FS Error: 0 State is an internally defined integer that represents the current step in the SPI-request decoding sequence.
PTrace Reference for Tandem FTAM DSM Perform SPI Request DSM Perform SPI Request The following trace record is generated after a SPI request has been decoded and immediately prior to the performance of the SPI request. For example, when the SCF command INFO PROCESS $QFTIE is issued as the $QFTIE process is being traced, the following trace record is generated: 09/23/93 10:31:20.119070 >000.000450 #23 INFO PROCESS $QFTIE (3,17) Perform SPI Req INFO PROCESS is the SPI command that was issued.
PTrace Reference for Tandem FTAM MEM Allocate MEM Allocate The following trace record is generated immediately after the allocation of memory. 09/23/93 10:30:50.468450 >000.
PTrace Reference for Tandem FTAM MEM Deallocate Count In List is the number of preallocated control blocks left in the list. Some control blocks may be preallocated by the traced process so that fast allocation and deallocation may occur. These preallocated control blocks are placed on the list. Allocation is first attempted from the list and then from the pool. Count From Pool is the number of control blocks that have been allocated from the memory pool.
PTrace Reference for Tandem FTAM MSG Reply Addr is the address where memory has been deallocated. Count In List is the number of preallocated control blocks left in the list. Some control blocks may be preallocated by the traced process so that fast allocation and deallocation may occur. These preallocated control blocks are placed on the list. Deallocation is first attempted to the list and then to the pool.
PTrace Reference for Tandem FTAM MSG Completion Status is the status of the request message, where the only possible value is 0. 0 means OK; a normal request has been sent. Queued Reqs is the number of times the READUPDATEX procedure has been called less the number of times the REPLYX procedure has been called.
PTrace Reference for Tandem FTAM MSG Completion MSG Request The following trace record is generated by the APLMGR, initiator, or responder process when it receives a request message from another process. 09/23/93 10:31:20.113047 >000.000232 #10 Request IN Receive Tag: 0 Sync ID: 5D Read Count: 4096 Opener: $ ZNET(1,192) Opened FN: 4 Queued Reqs: 1 Receive Tag is the message tag associated with the request message. This tag is returned by the RECEIVEINFO procedure.
PTrace Reference for Tandem FTAM MSG I/O Request MSG I/O Request The following trace record is generated by the APLMGR, initiator, or responder process immediately after an I/O operation is initiated. 09/23/93 10:30:50.469151 >000.
PTrace Reference for Tandem FTAM SYSMSG Open Request SYSMSG Open Request The following trace record is generated by the APLMGR, initiator, or responder process immediately after it validates and processes an open-request message from another process. 09/23/93 10:31:20.139510 >000.001001 #39 Reply Error: 0 OPEN Req Reply Error is the file-system error returned to the process that issued the associated openrequest message. For possible values, see the Guardian Procedure Errors and Messages Manual.
PTrace Reference for Tandem FTAM SYSMSG Close Request SYSMSG Close Request This trace record is generated by the APLMGR, initiator, or responder process immediately after it validates and processes a close-request message from another process. 09/23/93 10:31:39.593624 >000.002666 #724 Reply Error: 0 CLOSE Req Reply Error is the file-system error returned to the process that issued the associated closerequest message. For possible values, see the Guardian Procedure Errors and Messages Manual.
PTrace Reference for Tandem FTAM Code Number System Message -12 NEWPROCESSNOWAIT completion -20 Break -21 3270 device status -22 Time signal -23 Lock complete -24 Lock failed -26 Process time signal -28 SPI -30 OPEN -31 CLOSE -32 CONTROL -33 SETMODE -34 RESETSYNC -35 CONTROLBUF -37 SETPARAM -38 CANCEL -40 DEVICEINFO SYSMSG System Message OSI/FTAM and OSI/APLMGR SCF Reference Manual—421943-001 5- 42
A SCF Command Syntax Summary for Tandem FTAM ABORT PROCESS [\system-name.]{$appl-mgr-name } {indirect-process-name } ABORT SU [\system-name.]$process-name.#su-name ACTIVATE PROCESS [ \system-name.]{$appl-mgr-name } {indirect-process-name } ADD PROCESS [\system-name.] $appl-mgr-name.#FTAMI.internal-name , NAME process-name , { COMNAME "character-string" } { address } [ , attribute-spec ]...
SCF Command Syntax Summary for Tandem FTAM ADD PROCESS [\system-name.] $appl-mgr-name.#FTAMR.internal-name , NAME process-name , [ , attribute-spec ]... attribute-spec is: [ [ [ [ [ [ [ [ [ [ ALLOWSU { ON | OFF } ] BACKUPCPU integer ] CODEFILE file-spec ] CPU integer ] MAXASSOC integer ] MAXATTACH integer ] PRIORITY integer ] SWAP disk-volume ] THRESHOLD integer ] HIGHPIN { ON | OFF } ] ADD PROFILE [\system-name.]$appl-mgr-name.#VFS.
SCF Command Syntax Summary for Tandem FTAM ALTER PROCESS [\system-name.] $appl-mgr-name.#FTAMI.internal-name , attribute-spec [ , attribute-spec ]...
SCF Command Syntax Summary for Tandem FTAM ALTER PROFILE [\system-name.] $appl-mgr-name.#VFS.profile-name, attribute-spec [ , attribute-spec ]... attribute-spec is: [ [ [ [ [ [ COMNAME "character-string" DEFUSER user-id-password PSEL hex-character-string SSEL hex-character-string TSEL hex-character-string NSAP hex-character-string ] ] ] ] ] ] user-id-password is: { "groupid.userid , [ password ] " } { "groupnum.usernum , [ password ] " } ALTER SUBSYS [\system-name.
SCF Command Syntax Summary for Tandem FTAM INFO PROCESS [\system-name.]{$appl-mgr-name } {indirect-process-name } {$process-name } [ , DETAIL ] INFO PROFILE [\system-name.]$appl-mgr-name. { #VFS.profile-name }[ , DETAIL ] { #FTC } INFO SUBSYS [\system-name.]$appl-mgr-name [ , DETAIL ] LISTOPENS PROCESS [\system-name.]{$appl-mgr-name } {$process-name } LISTOPENS SU [\system-name.]$process-name.#su-name NAMES [\system-name.]{$appl-mgr-name } {$process-name } NAMES PROCESS [\system-name.
SCF Command Syntax Summary for Tandem FTAM START PROCESS [\system-name.]{$appl-mgr-name } {indirect-process-name } STATS PROCESS [\system-name.]{$appl-mgr-name } [ , RESET ] {$process-name } STATS SU [\system-name.]$process-name.#su-name [ , RESET ] STATS SUBSYS [\system-name.]$appl-mgr-name [ , RESET ] STATUS PROCESS [\system-name.]{$appl-mgr-name } {indirect-process-name } {$process-name } [ , DETAIL ] STATUS SU [\system.name.]$process-name.#su-name [ , DETAIL ] STATUS SUBSYS [\system-name.
SCF Command Syntax Summary for Tandem FTAM TRACE PROCESS [\system-name.]{$appl-mgr-name } { , STOP } {$process-name } { [ , trace-option ]... } trace-option is: [ [ [ [ [ [ [ COUNT count NOCOLL PAGES pages RECSIZE size SELECT select-spec TO filename WRAP ] ] ] ] ] ] ] VERSION [\system-name.]{$appl-mgr-name } [ , DETAIL ] {$process-name } VERSION SUBSYS [\system-name.
SCF Command Syntax Summary for Tandem FTAM OSI/FTAM and OSI/APLMGR SCF Reference Manual—421943-001 A- 8
B SCF Error Messages for the APLMGR Subsystem This appendix describes all Subsystem Control Facility (SCF) error messages returned by the APLMGR subsystem. These errors all have positive error numbers. Errors returned by the APLMGR subsystem that have negative numbers are common to all subsystems. For a general description of SCF error messages, see SCF Error Messages on page 1-11.
SCF Error Messages for the APLMGR Subsystem OSIAPLMG E00001 Guardian 90 procedure error. Call procedure-name, Error error-number Cause: A call was made to the Guardian procedure indicated, and a failure error was returned. Effect: The command is not performed. Recovery: Log the error, noting the procedure name and error number. Follow the procedures described on page B-1 for collecting relevant information and contacting appropriate support personnel.
SCF Error Messages for the APLMGR Subsystem OSIAPLMG E00005 Command not valid for responder process. Cause: You attempted to perform an ALLOWOPENS or a STOPOPENS command on a responder process, but these commands are valid only for initiator processes. Effect: The command is not performed. Recovery: Reissue the command, directing it to the appropriate initiator process.
SCF Error Messages for the APLMGR Subsystem OSIAPLMG E00501 Duplicate Attribute: attribute-name Cause: While issuing the command, you specified the indicated attribute more than once. Effect: The command is not performed. Recovery: Remove the duplicate attribute and reissue the command. OSIAPLMG E00502 Invalid Value for Attribute: attribute-name Cause: The value given for the specified attribute was not valid. Effect: The command is not performed.
SCF Error Messages for the APLMGR Subsystem OSIAPLMG E00505 Invalid Syntax in DEFUSER attribute. Cause: The value specified for the DEFUSER attribute for the PROFILE object in an ADD or ALTER command was not entered in a correct form. Effect: The command is not performed. Recovery: Issue the SCF command, using the correct syntax. See ADD PROFILE on page 3-14 or ALTER PROFILE on page 3-26 for more information on the DEFUSER attribute. OSIAPLMG E00506 Invalid value for ALLOWSU attribute.
SCF Error Messages for the APLMGR Subsystem OSI/FTAM and OSI/APLMGR SCF Reference Manual—421943-001 B- 6
C SCF Error Messages for the FTAM Subsystem This appendix describes all Subsystem Control Facility (SCF) error messages returned by the FTAM subsystem. These errors all have positive error numbers. Errors returned by the FTAM subsystem that have negative numbers are common to all subsystems. For a general description of SCF error messages, see SCF Error Messages on page 1-11.
SCF Error Messages for the FTAM Subsystem OSIFTAM E00001 Guardian 90 procedure error. Call procedure-name, Error error-number Cause. A call was made to the Guardian procedure indicated, and a failure error was returned. For example, if this error occurred when a security violation on the NEWPROCESSNOWAIT call was detected, the following message would be returned: OSIFTAM E00001 Guardian procedure error. Call newprocessnowait, Error 001413 Effect. The command is not performed. Recovery.
SCF Error Messages for the FTAM Subsystem OSIFTAM E00005 Command not valid for responder process. Cause. You attempted to perform an ALLOWOPENS or a STOPOPENS command on a responder process, but these commands are valid only for initiator processes. Effect. The command is not performed. Recovery. Reissue the command, directing it to the appropriate initiator process.
SCF Error Messages for the FTAM Subsystem OSI/FTAM and OSI/APLMGR SCF Reference Manual—421943-001 C- 4
Glossary The following glossary defines terms used in this manual and in the other Tandem OSI product manuals. Not all terms listed here are used in this particular manual. abstract syntax. A representation of the way in which components of information are to be specified in a communication. It defines a set of primitive elements whose range of values is fully defined—for example, integers, characters, and Boolean values—and ways of combining these elements. action event.
Glossary Configuration Utility Program (COUP) Configuration Utility Program (COUP). An interactive program that allows system managers to make online changes to the configuration of devices and controllers. COUP is part of the Dynamic System Configuration (DSC) facility, which is not used to configure Tandem OSI subsystem objects, but which can be used to configure the underlying ViewPoint and Tandem LAN Access Method (TLAM) objects. connection-establishment phase.
Glossary DSM DSM. See Distributed Systems Management (DSM). Dynamic System Configuration (DSC). A facility that allows system managers to make online changes to the configuration of devices and controllers. Its interactive utility program is called the Configuration Utility Program (COUP). DSC is not used to configure Tandem OSI subsystem objects, but it can be used to configure the underlying X.25 Access Method (X25AM) and Tandem LAN Access Method (TLAM) objects. EMS. See Event Management Service (EMS).
Glossary initiator initiator. The entity that initiates a connect request. Initiators and responders are defined with respect to a single connection. Some entities can be both an initiator and a responder simultaneously, but not over the same connection.
Glossary network service access point (NSAP) network service access point (NSAP). The logical point at which network service provider (NSP) process services are provided by the Network Layer entity to the Transport Layer entity. See also network service access point (NSAP) address. network service access point (NSAP) address. The global, network-unique address of an end system’s network service access point (NSAP), through which network service provider (NSP) process services are provided.
Glossary Open Systems Interconnection (OSI) subsystem Open Systems Interconnection (OSI) subsystem. One Open Systems Interconnection (OSI) manager process controls one or more TAPS and TSP processes. The OSI manager processes communicates with NSP processes but do not control them. The OSI manager, TAPS, TSP, and NSP processes can be on the same or different nodes within the same Expand network. See also Open Systems Interconnection (OSI) and Open Systems Interconnection (OSI) manager process. OSI/AS.
Glossary SCF SCF. See Subsystem Control Facility (SCF). sensitive command. A Distributed Systems Management (DSM) command that can be issued only by a restricted set of users. For Tandem communications subsystems, the sensitive commands are those that can change the state or configuration of objects, start or stop tracing, or change the values of statistics counters. service. A set of primitives (operations) that a layer provides to the layer above it.
Glossary subdevice subdevice. A logical entity providing access to a physical entity (a communications line). There may be one or many subdevices associated with a given line or process. Exactly what constitutes a subdevice differs depending on the subsystem. A ViewPoint subdevice corresponds to an X.25 network virtual circuit.
Glossary SYSGEN SYSGEN. The Tandem system generation program used to configure objects such as devices, controllers, and input/output processes (IOPs) in a newly installed system or to update the system when new software is released. Objects to be configured are defined to SYSGEN in a special configuration file, which can then be coldloaded into the system. The Tandem Open Systems Interconnection (OSI) products are not configured with SYSGEN, but the underlying X.
Glossary Transmission Control Protocol/Internet Protocol (TCP/IP) Transmission Control Protocol/Internet Protocol (TCP/IP). A set of layered communications protocols for connecting workstations and larger systems. See also Tandem NonStop TCP/IP. Transport entity. A process in the Transport Layer that sends or receives a given transport protocol data unit (PDU). Transport Layer. Layer 4 in the Open Systems Interconnection (OSI) Reference Model.
Index A ABORT PROCESS command, SCF 3-4 ABORT SU command, SCF 3-6 ACTIVATE PROCESS command, SCF 3-8 ADD PROCESS command, SCF 3-10 ADD PROFILE command, SCF 3-14 address attribute (variable) 4-2 ALL keyword, PTrace SELECT command 5-6 ALLOWOPENS PROCESS command, SCF 3-18 ALLOWSU attribute 4-3 ALTER PROFILE command, SCF 3-26 ALTER SUBSYS command, SCF 3-28 APLMGR object hierarchy 2-1 SCF errors returned by B-1 APLMGR processes, sequence for tracing 3-120 Application name, OSI/AS, relationship to COMNAME 4-5 ASN1
Index C C E CODEFILE attribute 4-4 COLLECTOR attribute 4-4 Command files, using DELAY in 3-109 Command not allowed when object is in use B-2 Command not valid for APLMGR process B-3 Command not valid for responder process B-3 Commands, SCF table of 3-2 table of commands and supported object types 3-3 COMNAME attribute 4-5 CPU attribute 4-6 Errors common versus subsystemspecific 1-12 returned by APLMGR B-1 returned by FTAM C-1 EVENTDESTINATION attribute 4-7 Event Management Service (EMS), role in Distri
Index I I INFO PROCESS command, SCF 3-35 INFO PROFILE command, SCF 3-43 INFO SUBSYS command, SCF 3-47 Initiators accessing directly 2-4 accessing through APLMGR 2-4 sequence for stopping 3-109 sequence for suspending 3-114 sequence for tracing 3-120 Internal CASE statement range error B-2 Invalid syntax in DEFUSER attribute B-5 error E00505 B-5 Invalid value for ALLOWSU, error E00506 B-5 Invalid value for attribute B-4 International Standards Organization (ISO) standards supported xix K Keywords, SCF TRA
Index N N P NAME attribute 4-10 NAMES commands, SCF NAMES PROCESS 3-61 NAMES PROFILE 3-66 NAMES SU 3-69 NAMES SUBSYS 3-72 null 3-58 NIST FTAM agreements xix No attribute found, error E00507 B-5 No more elements allowed in list B-4 NOASN1DEC FILTER option, PTrace 5-10 NOASN1ENC FILTER option, PTrace 5-10 NSAP attribute 4-11 NSAP, matching NSAP in OSI manager MIB 4-11 Null object 2-3 Null object, in VERSION command 3-126 Primitives, specifying for a trace 5-10 PRIORITY attribute 4-11 PROCESS objects 2-3/
Index R R READUPDATEX procedure, Guardian 5-37 Records identifiers, SELECT keywords for 5-6 trace size 5-5 trace header 5-13 RECSIZE option, TRACE command 5-5 Responders accessing directly 2-4 accessing through APLMGR 2-4 sequence for stopping 3-109 sequence for suspending 3-114 sequence for tracing 3-120 RUN command, TACL, starting PTrace utility with 5-2 S SCF attribute descriptions for FTAM 4-2 online help 1-11 role in DSM 1-5/1-7 tasks you can perform using 1-1 SCF attribute descriptions 4-1/4-14 SC
Index S SCF errors APLMGR E00002 B-2 E00003 B-2 E00005 B-3 E00006 B-3 E00007 B-3 E00501 B-4 E00502 B-4 E00503 B-4 E00504 B-4 E00505 B-5 E00506 B-5 E00507 B-5 FTAM E00001 C-2 E00002 C-2 E00003 C-2 E00004 C-2 E00005 C-3 E00006 C-3 SELECT command, PTrace 5-6/5-9 SELECT keywords figure of 5-3 relationship to PTrace FILTER command 5-9 table of 5-6 SM trace record format 5-30 SM keyword, PTrace SELECT command 5-6 SM trace record type 5-5 SSEL attribute 4-13 SSEL, matching NSAP in OSI manager MIB 4-13 START PROC
Index T T Z THRESHOLD attribute 4-14 TRACE command, RECSIZE 5-5 TRACE PROCESS command, SCF 3-116 device type and subtype numbers 5-3 relationship of keywords to process activity 5-3 relationship to PTrace 5-1/5-2 sequence of trace facility commands 5-2 using SELECT keywords 5-6 Trace records size 5-5 trace file header 5-12 trace header 5-13 TSEL attribute 4-14 TSEL, matching NSAP in OSI manager MIB 4-14 ZFTMSMT file 5-31 U USER trace record format event 5-14 reply 5-15 request 5-16, 5-26 USER keyword,
Index Z OSI/FTAM and OSI/APLMGR SCF Reference Manual—421943-001 Index -8
