OSI/AS SCF Reference Manual
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction
- 2 OSI/AS SCF Commands
- Supported Commands and Object Types
- Object Specification
- Attribute Default Values
- ABORT Command
- ACTIVATE Command
- ADD Command
- ALLOWOPENS Command
- ALTER Command
- Command Syntax
- ALTER ENTRY #APPL Command
- ALTER ENTRY #NSAP Command
- ALTER ENTRY #SNPA Command
- ALTER ENTRY #TSEL Command
- ALTER PROCESS Command
- ALTER PROFILE #L3 Command
- ALTER PROFILE #L4 Command
- ALTER PROFILE #L5 Command
- ALTER SERVICE #L3 Command
- ALTER SERVICE #L4 Command
- ALTER SERVICE #L5 Command
- ALTER SERVICE #L6 Command
- ALTER SERVICE #ACSE Command
- ALTER SUBSYS Command
- Considerations for the ALTER Command
- Examples of the ALTER Command
- CHECK Command
- DELETE Command
- INFO Command
- INFO Command Syntax
- INFO ENTRY #APPL Command
- INFO ENTRY #NSAP Command
- INFO ENTRY #SNPA Command
- INFO ENTRY #TSEL Command
- INFO PROCESS Command
- INFO PROFILE #L3 Command
- INFO PROFILE #L4 Command
- INFO PROFILE #L5 Command
- INFO SERVICE #L3 Command
- INFO SERVICE #L4 Command
- INFO SERVICE #L5 Command
- INFO SERVICE #L6 Command
- INFO SERVICE #ACSE Command
- INFO SUBSYS Command
- Considerations for the INFO Command
- Examples of the INFO Command
- LISTOPENS Command
- NAMES Command
- START Command
- STATS Command
- STATUS Command
- STOP Command
- STOPOPENS Command
- SUSPEND Command
- TRACE Command
- VERSION Command
- 3 OSI/AS Trace Facility
- Introduction
- Structure of the OSI/AS Processes
- PTrace Commands
- Trace Record Displays
- Trace Record Formats
- Shared Trace Records
- ASN.1 Trace Records
- ACSE Trace Records
- L6 Trace Records
- L6 USER—L6 Event
- L6 USER—L6 Continuation Event
- L6 USER—L6 Abort Continuation Event
- L6 USER—L6 User Reply
- L6 USER—L6 Request
- L6 USER—L6 First Request
- L6 USER—L6 Multi Mid Request
- L6 USER—L6 Multi Last Request
- L6 USER—L6 Multi Abort Request
- L6 PROV—L5 Event
- L6 PROV—L5 Continue Event
- L6 PROV—L5 Request
- L6 PROV—L5 First Request
- L6 PROV—L5 Continue Mid Request
- L6 PROV—L5 Continue Last Request
- L6 PROV—L5 Continue Abort Request
- L6 PROV—L6 Provider Reply
- L6—L6 Error Report
- L6 SM—L6 State Machine
- L5 Trace Records
- L5 USER—L5 Event
- L5 USER—L5 Continuation Event
- L5 USER—L5 Abort Continuation Event
- L5 USER—L5 Reply
- L5 USER—L5 Request
- L5 USER—L5 First Request
- L5 USER—L5 Multi Mid Request
- L5 USER—L5 Multi Last Request
- L5 USER—L5 Multi Abort Request
- L5 PROV—L5 Post Transport Read
- L5 PROV—L5 Issue Read
- L5 PROV—L5 Issue Transport Connect
- L5 PROV—L5 Issue Transport Attach
- L5 PROV—L5 Issue Writeread
- L5 PROV—L5 Issue Transport Disconnect
- L5 PROV—L5 Issue Write
- L5 PROV—L5 Issue Write Expedited
- L5 PROV—L5 I/O Completion
- L5 PROV—L5 I/O Completion Continuation
- L5 PROV—L5 Send TSDU
- L5 PROV—L5 Send TSDU Continuation
- L5 PROV—L5 Start Timer
- L5 PROV—L5 Cancel Timer
- L5 —L5 Discard Session Resources
- L5—L5 Error Report
- L5—L5 State Machine
- A OSI/AS SCF Summary
- ABORT Command
- ACTIVATE Command
- ADD Command
- ALLOWOPENS Command
- ALTER Command
- ALTER Command Syntax
- ALTER ENTRY #APPL Command
- ALTER ENTRY #NSAP Command
- ALTER ENTRY #SNPA Command
- ALTER ENTRY #TSEL Command
- ALTER PROCESS Command
- ALTER PROFILE #L3 Command
- ALTER PROFILE #L4 Command
- ALTER PROFILE #L5 Command
- ALTER SERVICE #L3 Command
- ALTER SERVICE #L4 Command
- ALTER SERVICE #L5 Command
- ALTER SERVICE #L6 Command
- ALTER SERVICE #ACSE Command
- ALTER SUBSYS Command
- CHECK Command
- DELETE Command
- INFO Command
- LISTOPENS Command
- NAMES Command
- START Command
- STATS Command
- STATUS Command
- STOP Command
- STOPOPENS Command
- SUSPEND Command
- TRACE Command
- Version Command
- B OSI/SCF SCF Error Messages
- C OSI/AS SCF Examples of Configuration Command Files
- D OSI/AS SCF Attribute Name Changes
- ADD ENTRY #TSEL Command
- ADD ENTRY $NSAP Command
- ADD ENTRY #SNPA Command
- ADD PROCESS Command
- ADD PROFILE #L4 Command
- ADD PROFILE #L5 Command
- ALTER ENTRY #TSEL Command
- ALTER ENTRY #NSAP Command
- ALTER ENTRY #SNPA Command
- ALTER PROCESS Command
- ALTER PROFILE #L5 Command
- ALTER SERVICE #L4 Command
- ALTER SERVICE #L5 Command
- ALTER SUBSYS Command
- E OSI/AS SCF Command Support
- Glossary
- Index
About This Manual
OSI/AS SCF Reference Manual—424121-001
xxiii
Change-Bar Notation
[ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For
example:
Event number = number [ Subject = first-subject-value ]
A group of items enclosed in brackets is a list of all possible items that can be displayed,
of which one or none might actually be displayed. The items in the list might be
arranged either vertically, with aligned brackets on each side of the list, or horizontally,
enclosed in a pair of brackets and separated by vertical lines. For example:
proc-name trapped [ in SQL | in SQL file system ]
{ } Braces. A group of items enclosed in braces is a list of all possible items that can be
displayed, of which one is actually displayed. The items in the list might be arranged
either vertically, with aligned braces on each side of the list, or horizontally, enclosed in
a pair of braces and separated by vertical lines. For example:
obj-type obj-name state changed to state, caused by
{ Object | Operator | Service }
process-name State changed from old-objstate to objstate
{ Operator Request. }
{ Unknown. }
| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in
brackets or braces. For example:
Transfer status: { OK | Failed }
% Percent Sign. A percent sign precedes a number that is not in decimal notation. The
%þnotation precedes an octal number. The %Bþnotation precedes a binary number.
The %Hþnotation precedes a hexadecimal number. For example:
%005400
P=%p-register E=%e-register
Change-Bar Notation
Change bars are used to indicate substantive differences between this edition of the
manual and the preceding edition. Change bars are vertical rules placed in the right
margin of changed portions of text, figures, tables, examples, and so on. Change bars
highlight new or revised information. For example:
The message types specified in the REPORT clause are different in the COBOL85
environment and the Common Run-Time Environment (CRE).
The CRE has many new message types and some new message type codes for old
message types. In the CRE, the message type SYSTEM includes all messages
except LOGICAL-CLOSE and LOGICAL-OPEN.