This annex specifies the values returned by the local management functions which are referenced in section 3 of this International Standard.
The requirements in relation to these functions are specified in section 4.
An implementation is required by section 3 of this International Standard to provide values for these functions. These values may be chosen by the implementor and "embedded" in the implementation. Alternatively, an implementation may choose to support a range of possible values, and to provide mechanisms for changing the values. Section 4 requires the documentation provided with the implementation to state the choices which were made, and requires that certain specified functions be configurable. (See clause 4.3.)
This function shall return the human-text (in some human language) which accompanies a JTM diagnostic code. It may provide more detail than is implied by the JTM diagnostic code, or there may be a single piece of text for each message. The JTM diagnostic codes are listed in section one, with their abstract syntax. Note that in several cases the specification of section 3 requires the implementation to include text from the work specification in the human readable diagnostic. This is the minimum required text.
An implementation is required (see 4.1.14) to support diagnostics in ISO 646. It may in addition support diagnostics in other character sets, using the CCR diagnostic code indicator to select the diagnostic text.
This function shall return the "JTM-name" assigned by the naming authority to this application-entity (as defined in 2.2.1 of section 2).
This function shall return a Basic Class "Monitoring-specification" (as defined in section 2) which is suitable for receiving reports for OSI jobs submitted to this JTM ASE. Its value may depend on the source of the J-INITIATE (see also MF6).
NOTE -- It may, for example be set to the users mail-box.
This function shall return an authenticated "Identification" representing the initiation agency or shall return "none available".
NOTE -- This may be a "User-identification", or may indicate that the agency operates on behalf of an open-system or authority - that is, that the J-INITIATE came from an operator.
This function is used to authenticate an "Identification" with a "password" "validation". It shall return "authenticated" or "not-authenticated".
This function shall return zero, one or more further authorisations which are needed to ensure that reports are deliverable to the primary monitor.
This function shall return zero, one or more additional authenticated "Identifications" when it is known that these are associated with the same human being or authority as an existing validated authentication.
This function uses calling address information provided by lower layer protocols, and any authentication procedures available at a lower layer, to determine the validity of the "JTM-name" of the caller. It shall return UNKNOWN, KNOWN, or AUTHENTICATED, as specified in 3.3.1. It may always return UNKNOWN.
This function determines whether JTM transfers from an UNKNOWN, KNOWN, or AUTHENTICATED "JTM-name" are to be accepted and progressed. A minimum provision would be to accept all calls. It shall return "progress" or "don't progress".
This shall return the time to wait during a transfer when there is no progress to the transfer and the time to wait for completion of association establishment, and the time to wait for completion of association release. The times may be unlimited, and may be subject to operator control.
This function determines whether, for a particular received transfer-element, a recognised authorisation element is require for reporting or to permit any further processing. The common cases will be either authorisation always required, or authorisation only required for remote reporting (and access to some sinks). It shall return "authorisation required for all activity", "authorisation required for reporting", or "authorisation not required".
NOTE -- Appropriate values of MF11, MF15 and MF16 can make it unnecessary for an implementation to process JTM authorisation elements. Use of such values is an implementation option.
This function shall return the names of the user identification authorities which are recognised at this open system as capable of providing authorisation data for an activity.
This function shall return the list of "JTM-name"s (unknown, known or authenticated) which are to be trusted to correctly set the "validation" in an authorisation element.
NOTES
- Where interference with the communication is possible, authentication of the sender must be combined with a tamper detect code or encryption if this mechanism is to be secure.
- In the case of "unknown", the function serves only to block an implementation which is not masquerading in the value it puts in the audit-trace (MF2).
- It is recommended that configuration mechanisms should include statements such as "ALL" and "ALL EXCEPT ...".
This function shall return the time for which the implementation is to attempt to progress the work specification with completion commitment before abandoning the attempt and taking the lowest possible commitment level. The decision would normally be based on the responses of CCR subordinates, and on the timer values returned in these responses and provided by the superior.
This function shall return the list of the agency names, their types, and any information needed to access them, that are known to this implementation. It is strongly recommended that although the actual agencies supported by an implementation may be fixed, the names to be given to them should be configurable. This function shall also return a flag saying whether authorisation is needed for access to this agency, and if so, which "User-identification-authority" it recognises.
NOTES
- Access to printers may be uncontrolled while access to files is controlled. For special devices, or where the device is remote, a "User-identification-authority" unique to the device may be established. More commonly, there will be a single authority for the entire open system.
- Appropriate values of MF11, MF15 and MF16 can make it unnecessary for an implementation to process JTM authorisation elements. Use of such values is an implementation option.
This function shall return a flag saying whether or not a particular work specification requires authorisation for an outgoing transfer. This may depend on the target, or on the subjob type, or both. The management function shall also return the "User-identification-authorities" which are recognised for this activity (see note on MF15), and any addressing information needed to establish an application-association in "ISO JTM Basic Class Application-context" or, in an extended implementation, "ISO JTM Full Application-context". Where applicable, it may also determine options such as the types of transport protocol which are offered or accepted, and the transfer syntaxes which are offered or accepted.
NOTE -- Appropriate values of MF11, MF15 and MF16 can make it unnecessary for an implementation to process JTM authorisation elements. Use of such values is an implementation option.
This function determines whether work specifications are or are not to be "visible" for status display to users who do not "own" them. It is required that this should be configurable. It shall return "visible" or "not visible".
This function either specifies that documents in an execution agency which are not collected on J-END-SIGNAL are to be deleted, or else determines the way they are to be disposed of locally. This may involve retention, local printing, or copying to some permanent filestore. It may have a different value for each agency which is supported.
This function determines whether an incoming JTM transfer can be progressed at this point in time. It shall return "progress" or "retry-later", and may also return a retry time for the C-ROLLBACK indication. It may be used to restrict the total number of JTM transfers, or the total number of incoming transfers, from one JTM ASE or a group of JTM ASEs. It may also be dynamically variable to provide local operator control.
NOTE -- It is strongly recommended that the concurrency available in the lower layers for JTM transfers should exceed the value in this function, so that RETRY-LATER responses can be generated at the CCR level.
This function determines the maximum concurrency for commitment groups issued to JTM agencies. It shall return "progress" or "wait".
This function determines whether an outgoing transfer to a particular JTM ASE can be progressed at this point in time.
It shall return "progress-Basic Class" or "progress-Full" or "wait" or "error". If it returns "progress-Basic Class", then it shall make available an application-association in "ISO JTM Basic Class Application-context". If it returns "progress-Full", then it shall make available an application-association in "ISO JTM Full Application-context". The procedures for establishing a new application association are specified in section 5. The comments in MF19 also apply. This function implements local scheduling decisions on the use of application-associations. If the function determines that progress at this time is possible, local procedures obtain an application-association in "ISO JTM Basic Class Application-context" or "ISO JTM Full Application-context" and with presentation-context negotiation completed and contexts defined for JTM and CCR, and for the document types of any documents in the work specification.
NOTE -- This may be achieved by reuse of existing connections or by a new connection, according to local scheduling decisions. The initiative in establishing the contexts is taken by the sender. The intended recipient plays a passive but cooperating role, as specified in section 5.
This function shall return the addressing information to be used by remote systems and inserted by them in the called address fields for calls to this JTM ASE. (See 4.1.6 and 4.1.8.)
This function shall return the addressing information to be used by lower layers to insert values in calling address fields for calls from this JTM ASE. (See 4.1.7 and 4.1.8.) The values returned by this function may, but need not, be the same as those returned by MF22. This function is also used for responding or recall addresses.
This function determines, on the basis of calling application-entity title, calling presentation address, and considerations of local congestion whether to process an A-ASSOCIATE indication or to reject it immediately. It determines whether the rejection has a code specifying "(permanent)" or "(transient)".
This shall return the minimum time for which a report is stored by an implementation acting as storing monitor point. After this time has elapsed from receipt of the report, it may be deleted without outside intervention.
This function shall return values for "osi-job-name", "urgency" and <CCR parameters> for "transfer-manipulation" work specifications that are created by the JTM ASE other than as a result of a J-INITIATE.
| JTM-1 |
| {iso standard 8832 document (4) text (1)} |
| "ISO JTM simple text document" |
| Parameters shall not be used. |
This document type is defined for use in JTM and FTAM transfers. It may form part of an FTAM File Access Data Unit, but is not applicable as a file content's name.
ISO 8571-3:1988, Information processing systems - Open Systems Interconnection - File Transfer, Access and Management - Part 3 : File Service definition.
7.1 character string: an ordered series of zero, one or more characters from some specified character repertoire.
7.2 graphics character: a character from any character repertoire registered for use as a G0, G1, G2, or G3 set in the ISO International Register of Character Sets, or the character space.
FTAM File Transfer, Access, and Management
The document consists of an unbounded sequence of zero one or more character strings. Each character string is of unbounded length, and contains zero one or more graphics characters.
The document consists of an indefinite number of ASN.1 datatypes, each of type
GraphicString
Each GraphicString shall carry exactly one of the character strings in the document, in order.
Datatype ::= GraphicString
asname ::=
{iso standard 8832
document-abstract-syntax (5) text (1)}
The ObjectDescriptor value shall be "ISO JTM simple text abstract syntax".
Each presentation data value shall consist of one or more instances of "Datatype", taken in order, and shall be transferred in a presentation context established for "asname".
The presentation data values shall be transferred in the order they are produced by 11.3 above.
tsname ::=
{iso standard 8832
document-transfer-syntax (6) text (1)}
The ObjectDescriptor value shall be "ISO JTM simple text basic transfer syntax".
12.2.1 The name "tsname" shall be used for that transfer syntax obtained by applying the ASN.1 Basic Encoding Rules (ISO/IEC 8825) to each "Datavalue" in the presentation data value and concatenating the resulting octets.
12.2.2 The transfer syntax "tsname" shall be supported. Other transfer syntaxes may optionally be supported, but any additional support shall be declared in the Protocol Implementation Conformance Statement.
Concatenation of this type with itself is possible, and produces a document of the same type consisting of the combined sequence of character strings.
NOTE -- The boundary of the original sequences is no longer visible.
A conforming implementation shall support all values of this document type subject to a possible implementation limit based on the total number of characters in the document. The implementation limit shall permit the use of documents containing up to 64000 characters. The limit shall be described in the protocol implementation conformance statement.
When transmitted in "JTM Basic Class application context", the entire document shall be transferred as a single presentation data value.
| JTM-2 |
| {iso standard 8832 document (4) print (2)} |
| "ISO JTM simple print document" |
| Parameters shall not be used. |
This document type is defined for use in JTM and FTAM transfers. It may form part of an FTAM File Access Data Unit, but is not applicable as a file content's name.
ISO 8571-3:1988 Information processing systems - Open Systems Interconnection - File Transfer, Access and Management - Part 3 : File Service definition.
7.1 character string: an ordered series of zero, one or more characters from some specified character repertoire.
7.2 graphics character: a character from any character repertoire registered for use as a G0, G1, G2, or G3 set in the ISO International Register of Character Sets, or the character space.
FTAM File Transfer, Access, and Management
The document consists of an unbounded sequence of zero one or more character strings. Each character string is unbounded, and contains any graphics characters. Each character string is intended for display on a display medium. It has associated with it a display-control indicator which controls the positioning of the text on the medium. The medium may, but need not, include identifiable boundaries which can be located when specifying the position of a line of text.
The strings are displayed in the order they appear in the sequence, moving from top to bottom of the medium, and left to right within the string. The treatment of lines which are too long for the medium, or which contain characters it cannot display, is not standardised.
Each display-control indicator is used to control the vertical positioning of the line of text containing the display control indicator beneath the preceding line as follows:
| "no-space" | display on top of the previous line; where a display medium cannot support this function, the line should be displayed immediately beneath, with a medium-specific indication that overprinting was intended; |
| "single-space" | display immediately beneath; |
| "double-space" | display one blank line then display the text; |
| "page-throw" | move to the line following a medium boundary if such a boundary exists (otherwise the effect is not standardised) and then display the text. |
The first display control in the sequence is treated by assuming there was a preceding line at a position immediately above a medium boundary, then applying the above rules.
The document consists of an indefinite number of ASN.1 datatypes, each of type
Line
where
Line ::= SET
{display-control CHOICE
{no-space [0] IMPLICIT NULL ,
single-space [1] IMPLICIT NULL ,
double-space [2] IMPLICIT NULL ,
page-throw [3] IMPLICIT NULL } ,
text GraphicString }
Each "Line" shall carry exactly one of the character strings in the document, together with its associated display indicator, in order.
Datatype ::= Line
asname ::=
{iso standard 8832
document-abstract-syntax (5) print (2)}
The ObjectDescriptor value shall be "ISO JTM simple print abstract syntax".
Each presentation data value shall consist of one or more instances of "Datatype", taken in order, and shall be transferred in a presentation context established for "asname".
The presentation data values shall be transferred in the order they are produced by 11.3 above.
tsname ::=
{iso standard 8832
document-transfer-syntax (6) print (2)}
The ObjectDescriptor value shall be "ISO JTM simple print basic transfer syntax".
12.2.1 The name "tsname" shall be used for that transfer syntax obtained by applying the ASN.1 Basic Encoding Rules (ISO/IEC 8825) to each "Datavalue" in the presentation data value and concatenating the resulting octets.
12.2.2 The transfer syntax "tsname" shall be supported. Other transfer syntaxes may optionally be supported, but any additional support shall be declared in the Protocol Implementation Conformance Statement.
This document type can be concatenated with itself to produce another document of the same type. The new document shall consist of a sequence of "Lines" as follows:
The "Lines" in b) above shall depend on the "display-control" in the first line of the second document according to the following list:
| no-space | A single "Line" with "display-control" set to "page-throw" and "text" copied from the original line. |
| single-space | A single "Line" with "display-control" set to "page-throw" and "text" copied from the original "Line". |
| double-space | A "line" consisting of |
{display-control page-throw NULL,
text NULL}
| followed by a "Line" with "display-control" set to "single-space" and "text" copied from the original "Line". | |
| page-throw | A "Line" identical to the original "Line". |
A conforming implementation shall support all values of this document type, subject to a possible implementation limit based on the total number of characters in the document. The implementation limit shall permit the use of documents containing up to 64000 characters. The limit shall be described in the protocol implementation conformance statement.
When transmitted in "JTM Basic Class application context", the entire document shall be transferred as a single presentation data value.
| JTM-3 |
| {iso standard 8832 document (4) binary (3)} |
| "ISO JTM simple binary document" |
Parameters shall not be used.
This document type is defined for use in JTM and FTAM transfers. It may form part of an FTAM File Access Data Unit, but is not applicable as a file content's name.
ISO 8571-3:1988 Information processing systems - Open Systems Interconnection - File Transfer, Access and Management - Part 3 : File Service definition.
No additional definitions are used for this document type.
FTAM File Transfer, Access, and Management
The document consists of a single unlimited string of zero one or more bits.
The document consists of an indefinite number of ASN.1 datatypes, each of type
BITSTRING
The string of bits in the document shall be divided into BITSTRING datatypes in a way which is determined by the sender, but the order in which they appear in the document shall be retained. Where checkpointing is not used, the entire document shall be carried as a single BITSTRING datatype.
Datatype ::= BITSTRING
asname ::=
{iso standard 8832
document-abstract-syntax (5) binary (3)}
The ObjectDescriptor value shall be "ISO JTM simple binary abstract syntax".
Each presentation data value shall consist of one or more instances of "Datatype", taken in order, and shall be transferred in a presentation context established for "asname".
The presentation data values shall be transferred in the order they are produced by 11.3 above.
tsname ::=
{iso standard 8832
document-transfer-syntax (6) binary (3)}
The ObjectDescriptor value shall be "ISO JTM simple binary basic transfer syntax".
12.2.1 The name "tsname" shall be used for that transfer syntax obtained by applying the ASN.1 Basic Encoding Rules (ISO/IEC 8825) to each "Datavalue" in the presentation data value and concatenating the resulting octets.
12.2.2 The transfer syntax "tsname" shall be supported. Other transfer syntaxes may optionally be supported, but any additional support shall be declared in the Protocol Implementation Conformance Statement.
Concatenation of this type with itself is possible, and produces a document of the same type consisting of the combined sequence of bits.
NOTE -- The boundary of the original sequences is no longer visible.
A conforming implementation shall support all values of this document type, subject to a possible implementation limit based on the total number of bits in the document. The implementation limit shall permit the use of documents containing up to 512000 bits. The limit shall be described in the protocol implementation conformance statement.
| JTM-4 |
| {iso standard 8832 document (4) work-display (4)} |
| "ISO JTM work-display document" |
Parameters shall not be used.
This document type is defined for use in JTM and FTAM transfers. It may form part of an FTAM File Access Data Unit, but is not applicable as a file content's name.
ISO 8571-3:1988 Information processing systems - Open Systems Interconnection - File Transfer, Access and Management - Part 3 : File Service definition.
ISO/IEC 8831:1991,Information technology - Open Systems Interconnection - Job Transfer and Manipulation Concepts and Services
No additional definitions are used in this register entry.
FTAM File Transfer, Access, and Management
See clause 3.5.3 of ISO/IEC 8831.
The document consists of a single instance of the ASN.1 datatype
Work-display-doc
defined in clause 2.7 of this International Standard.
Datatype ::= Work-display-doc
asname ::=
{iso standard 8832 abstract-syntax (2)}
The ObjectDescriptor value shall be "ISO JTM abstract syntax".
The single presentation data value used for transfer shall consist of a single instance of "Datatype" and shall be transferred in any presentation context established for "asname".
A single presentation data value is used.
tsname ::= {joint-iso-ccitt asn1(1) basic-encoding(1)}
The ObjectDescriptor value shall be "Basic encoding of a single ASN.1 type".
12.2.1 The transfer syntax to be used with "tsname" is specified in ISO/IEC 8825.
12.2.2 The transfer syntax "tsname" shall be supported. Other transfer syntaxes may optionally be supported, but any additional support shall be declared in the Protocol Implementation Conformance Statement.
Concatenation of this type with itself is possible, and produces a document of the same type consisting of the combined list of <work display> components.
NOTE -- The boundary of the original lists of <work display> components is no longer visible.
See 4.1.16 of this International Standard.
| JTM-5 |
| {iso standard 8832 document (4) report-display (5)} |
| "ISO JTM report-display document" |
Parameters shall not be used.
This document type is defined for use in JTM and FTAM transfers. It may form part of an FTAM File Access Data Unit, but is not applicable as a file content's name.
ISO 8571-3:1988 Information processing systems - Open Systems Interconnection - File Transfer, Access and Management - Part 3 : File Service definition.
ISO/IEC 8831:1991 Information technology - Open Systems Interconnection - Job Transfer and Manipulation Concepts and Services
No additional definitions are used in this register entry.
FTAM File Transfer, Access, and Management
See clause 3.5.1 of ISO/IEC 8831.
The document consists of a single instance of the ASN.1 datatype
Report-display-doc
defined in clause 2.7 of this International Standard.
Datatype ::= Report-display-doc
asname ::=
{iso standard 8832 abstract-syntax (2)}
The ObjectDescriptor value shall be "ISO JTM abstract syntax".
The single presentation data value used for transfer shall consist of a single instance of "Datatype" and shall be transferred in any presentation context established for "asname".
A single presentation data value is used.
tsname ::= {joint-iso-ccitt asn1(1) basic-encoding(1)}
The ObjectDescriptor value shall be "Basic encoding of a single ASN.1 type".
12.2.1 The transfer syntax to be used with "tsname" is specified in ISO/IEC 8825.
12.2.2 The transfer syntax "tsname" shall be supported. Other transfer syntaxes may optionally be supported, but any additional support shall be declared in the Protocol Implementation Conformance Statement.
Concatenation of this type with itself is possible, and produces a document of the same type consisting of the combined list of <JTM-report-display> components.
NOTE -- The boundary of the original lists of <JTM-report-display> components is no longer visible.
See 4.1.16 of this International Standard.
| JTM-6 |
| {iso standard 8832 document (4) tcr-display (5)} |
| "ISO JTM TCR-display document" |
Parameters shall not be used.
This document type is defined for use in JTM and FTAM transfers. It may form part of an FTAM File Access Data Unit, but is not applicable as a file content's name.
ISO 8571-3:1988 Information processing systems - Open Systems Interconnection - File Transfer, Access and Management - Part 3 : File Service definition.
ISO/IEC 8831:1991 Information technology - Open Systems Interconnection - Job Transfer and Manipulation Concepts and Services.
No additional definitions are used in this register entry.
FTAM File Transfer, Access, and Management
See clause 3.5.3 of ISO/IEC 8831.
The document consists of a single instance of the ASN.1 datatype
Tcr-display-doc
defined in clause 2.7 of this International Standard.
Datatype ::= Tcr-display-doc
asname ::=
{iso standard 8832 abstract-syntax (2)}
The ObjectDescriptor value shall be "ISO JTM abstract syntax".
The single presentation data value used for transfer shall consist of a single instance of "Datatype" and shall be transferred in any presentation context established for "asname".
A single presentation data value is used.
tsname ::= {joint-iso-ccitt asn1(1) basic-encoding(1)}
The ObjectDescriptor value shall be "Basic encoding of a single ASN.1 type".
12.2.1 The transfer syntax to be used with "tsname" is specified in ISO/IEC 8825.
12.2.2 The transfer syntax "tsname" shall be supported. Other transfer syntaxes may optionally be supported, but any additional support shall be declared in the Protocol Implementation Conformance Statement.
Concatenation of this type with itself is possible, and produces a document of the same type consisting of the combined list of <transfer-display> components.
NOTE -- The boundary of the original lists of <transfer-display> components is no longer visible.
See 4.1.16 of this International Standard.