This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

• While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.
• Press the "Save" button at any time to save work in progress. Once the work has been saved, there is the option to continue editing if required.
• Many questions have instructions to assist in development of answers. They are marked with the indicator. Please look at the instructions carefully.
• Although HTML markup can be included in answers, this is not recommended apart from basic tags such as <p> and <br>, since incorrect markup could effect the format of other items in the document.
• Questions on this system should be addressed to the Conformance Statement manager at The Open Group.

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

1. LMX Server

Product Information

Environment Specification

Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.

	Testing Environment	Binary-compatible Family	Portability Environment	Indicator of Compliance	Compliance Details
			Select from this list XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended Internationalised System Calls and Libraries Extended V2	None.	None.
			Select from this list XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended Internationalised System Calls and Libraries Extended V2	None.	None.
			Select from this list XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended Internationalised System Calls and Libraries Extended V2	None.	None.
			Select from this list XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended Internationalised System Calls and Libraries Extended V2	None.	None.
			Select from this list XPG3 Internationalised System Calls and Libraries Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended Internationalised System Calls and Libraries Extended V2	None.	None.

Temporary Waivers

1.1 General SMB Issues

Question 1: Which SMB dialects do you support?

Response

Dialect	Supported
PC NETWORK PROGRAM 1.0	Yes   No
MICROSOFT NETWORKS 1.03	Yes   No
MICROSOFT NETWORKS 3.0	Yes   No
LANMAN 1.0	Yes   No
LM1.2X002	Yes   No

Rationale

An LMX server must support at least one of these dialects.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.9, Negotiated Dialect.

Question 2: Which security levels do you support?

Response

Security	Supported
share-level	Yes   No
user-level	Yes   No

If necessary, please elaborate in the area below.

Rationale

This defines the security environment (see Section 2.2, Security Overview) in which the LMX server works.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.8, Security Policy.

Question 3: Which password encryption policy does your LMX server support?

Response

Policy	Supported
SMB encryption	Yes   No
SMBsecpkgX X/Open security package	Yes   No
Other SMBsecpkgX security package	Yes   No
None	Yes   No

If necessary, please elaborate in the area below.

Rationale

Support of password encryption in the extended protocols is possible (see Section 11.2, SMBsecpkgX Specification, Section 11.3, SMBsesssetupX Specification, Appendix C, The X/Open Security Package and Appendix D, SMB Encryption Techniques), but optional.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.8, Security Policy.

Question 4: Do you support the interoperation of SMB and (PC)NFS with respect to the additional features beyond those provided by XSI on the same CAE system?

Response

Yes   No If necessary, please elaborate in the area below.

Rationale

Interoperation beyond XSI semantics for PC file and print-sharing implementations on a single CAE system is not necessarily provided.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.10, Network Issues.

1.2 Networking Issues

Question 5: Is the SMB server capable of running over other remotely mounted XNFS file systems?

Response

Yes   No

Rationale

It is possible for this to occur.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.10, Network Issues.

Question 6: Which binding of NetBIOS to a transport protocol do you support?

Response

Binding	Supported
TOP/NetBIOS	Yes   No
RFC 1001/1002	Yes   No

Where:

TOP/NetBIOS refers to the document "MAP/TOP Users Group Technical Report, Specification of NetBIOS Interface and Name Service Support by Lower Layer OSI Protocols, Version 1.0, September 27, 1989", as reproduced in the specification as Appendix E.

RFC 1001/1002 refers to the "Protocol Standard for a NetBIOS Service on a TCP/UDP Transport: Concepts and Methods" (RFC 1001) and "Protocol Standard for a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications" (RFC 1002), both dated April 1987 and reproduced in the specification as Appendix F and Appendix G.

Rationale

At least one of the two bindings must be supported.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.10, Network Issues.

Question 7: Do you support additional mappings of LMX server names to NetBIOS names?

Response

Yes   No If necessary, please elaborate in the area below.

Rationale

It is possible that next to the specified mapping of LMX server names to NetBIOS names (see Section 3.5, Naming) other mechanisms exist.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.10, Network Issues.

Question 8: Do you support operation over more than a single subnetwork?

Response

Yes   No

Rationale

The original specifications limited the operation to a single subnetwork, but interoperation to connected subnetworks is not precluded.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.10, Network Issues.

Question 9: With RFC1001/1002 functionality, does your implementation support B Type or M Type Node?

Response

Node	Provided
B Type Node	Yes   No
M Type Node	Yes   No

Rationale

With RFC 1001/1002 both types are possible. B-node functionality is the minimum functionality required for a compliant RFC 1001/1002 implementation. M-node functionality is a superset. (See Appendix F, RFC 1001 and Appendix G, RFC 1002.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.10, Network Issues.

Question 10: With Top/NetBIOS, does your NDSE implementation support NDUA?

Response

Yes   No

Rationale

With TOP/NetBIOS in simple network topologies the NDSE will resolve all NetBIOS name queries. For more complex network topologies NDUA support is useful, but optional. See Appendix E, TOP/NetBIOS.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.10, Network Issues.

1.3 Supported File and Print Options

Question 11: Do you support any file types other than file system subtrees and printers?

Response

Yes   No

Rationale

It is possible to share access to CAE special files.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.3, LMX File Mapping.

Question 12: How does the LMX server deal with print modes?

Response

Mode	Supported	Special LMX Server Action
Text	Yes   No
Graphics	Yes   No

Rationale

Special actions taken by the LMX server for text or graphics print files are optional.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.6, LMX Print Spooling.

Question 13: Do you use printer set-up data?

Response

Yes   No

Rationale

Allowing printer set-up data can have a profound effect in a shared environment.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.6, LMX Print Spooling.

Question 14: Do you support any mapping for CAE filenames to DOS filenames beyond the minimal requirements defined in the specification?

Response

Yes   No

Rationale

For all protocols, except the extended 2.0 protocol, DOS filenames need to be in upper-case 8.3 format (see Section 3.5.2, NetBIOS Names). It is possible to map longer or mixed-case CAE filenames into this format.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.2, LMX Filename Mapping.

Question 15: For the extended protocols, do you honour case-sensitivity (bit 3 of SMB header smb_flag not set) and non-canonical pathnames (bit 4 of SMB header smb_flag not set)?

Response

Yes   No

Rationale

Although case-sensitivity is present in CAE systems, DOS SMB redirectors will normally set the case-insensitivity bit.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.2, LMX Filename Mapping.

Question 16: Do you support the following SMB file attributes?

Response

Attribute	Provided
Read-only	Yes   No
Hidden	Yes   No
System	Yes   No
Volume	Yes   No
Directory	Yes   No
Archive	Yes   No

Rationale

SMB file attributes are not the same as CAE file attributes. The mapping of SMB file attributes that cannot be represented as CAE file attributes is optional.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.3.1, SMB File Attributes.

1.4 Interworking with CAE Applications and CAE-related Restrictions

Question 17: Do you support file interlocking between DOS and CAE applications with respect to deny-modes or byte-range locking?

Response

Yes   No

Rationale

The locking models used by SMB and CAE are different. If locking is provided it should support the features defined in Section 4.4, LMX File Locking.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.4.1, Interlocking Behaviour.

Question 18: If you support byte-range interlocking between CAE and PC applications, does this support 32-bit unsigned lock ranges

Response

Yes   No

Rationale

A CAE filsystem may not support such ranges in a native mode.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.4.1, Interlocking Behaviour.

Question 19: What are the maximum path lengths that you support from the root of the shared file system subtree?

Response

Rationale

LMX servers may have a maximum path restriction.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2.

Question 20: Does the server perform any internal caching?

Response

Yes   No

If necessary, please elaborate in the area below.

Rationale

A DOS user would expect a write of data to store to happen immediately.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.5, LMX Server Caching.

Question 21: For the extended protocols, do you support locking timeouts?

Response

Yes   No

Rationale

Locking timeouts are optional.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.4.2, Locking Timeouts.

Question 22: Does the CAE umask value have an effect on files created by the LMX Server?

Response

Yes   No

Rationale

Section 4.3.2, CAE File Access Permissions illustrates possible effects of umask.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.3.2, CAE File Access Permissions.

Question 23: Is the effect of umask configurable?

Response

Yes   No

Please elaborate in the area below.

Rationale

Section 4.3.2, CAE File Access Permissions illustrates possible effects of umask.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.3.2, CAE File Access Permissions.

Question 24: Does the CAE ulimit value have an effect on files created by the LMX Server?

Response

Yes   No

Rationale

Section 4.3.3, File System Issues illustrates possible effects of ulimit.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.3.3, File System Issues.

Question 25: Is the effect of ulimit configurable?

Response

Yes   No

Please elaborate in the area below.

Rationale

Section 4.3.3, File System Issues illustrates possible effects of ulimit.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.3.3, File System Issues.

1.5 Options with Extended 2.0 Protocols

Question 26: For the extended 2.0 protocols, what is the maximum length of the long filename component that you support?

Response

Rationale

LMX servers may have a maximum for the supported size of a particular filename (see Section 4.3.6, Long Filenames).

Limitation in filename component limits the type of client that may use the server.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.3.6, Long Filenames.

Question 27: For the extended 2.0 protocols, do you support extended attributes?

Response

Yes   No

Rationale

Support of this feature is optional.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 4.3.7, Extended Attributes.

2. IPC Mechanisms

2.1 Scope of the Implementation

Question 1: Which of the following items are supported?

Reference

CAE Specification, IPC Mechanisms for SMB.

2.2 Named Pipe APIs

Question 2: Which of the following optional interfaces are supported?

Response

LmForkNamedPip	Yes   No
DosOpen	Yes   No

Rationale

Support for these routines is optional.

Reference

CAE Specification, IPC Mechanisms for SMB.

Question 3: If DosOpen is supported, is there a way to specify the SMB account name and password for the named pipe usage?

Response

Yes   No

Please explain how the username and password are derived in the area below.

Rationale

The SMB security model requires a username and password. There must be some mapping between the CAE user and the SMB user.

Reference

CAE Specification, Protocols for X/Open PC Interworking: SMB, Version 2, Section 2.2, Security Overview.

Question 4: Are named pipes inherited from a process to a child process?

Response

Interface	Supported
LmForkNamedPipe	Yes   No
fork	Yes   No

Rationale

The method by which named pipes are inherited is a portability issue.

Reference

CAE Specification, IPC Mechanisms for SMB, Section 2.4.4, Pipe Instances and Inheritance.

Question 5: What is the default maximum number of instances for a named pipe applied when NP_ICOUNT is set to 0xFF?

Response

Rationale

If the API user calls DosMakeNmPipe() to create a new named pipe (rather than a new instance of an existing one), the NP_ICOUNT field of the pmode parameter may to be set to 0xFF to indicate that an implementation-defined maximum number of instances can be created.

Reference

CAE Specification, IPC Mechanisms for SMB, DosMakeNmPipe().

2.3 Mailslot APIs

Question 6: What is the maximum size of message accepted by a Class 2 mailslot?

Response

Rationale

Delivery of messages to Class 2 mailslots is not guaranteed, and there is an implementation-defined limit on the size of message that can be accepted by such a mailslot. This limit may not be less than 360 bytes.

Reference

CAE Specification, IPC Mechanisms for SMB, DosDeleteMailslot().

Question 7: What priorities of mailslots are supported?

Response

Level	Supported?
0	Yes   No
1	Yes   No
2	Yes   No
3	Yes   No
4	Yes   No
5	Yes   No
6	Yes   No
7	Yes   No
8	Yes   No
9	Yes   No

Please elaborate, if necessary, in the area below.

Rationale

It will always be true that priority 9 is delivered before other priority messages, but the behaviour of the lower priorities (0-8) is implementation-dependent and needs to be explained.

Reference

CAE Specification, IPC Mechanisms for SMB, Section 3.3, Mailslots.

---

3. Appendix

This appendix contains additional, explanatory material that was provided by the vendor.

---

Copyright © 
All rights reserved.

---

4. Change History

Date	Name	Comment
New

---

 Copyright © 1998-2002 The Open Group. All Rights Reserved.

 OSF/1, Motif, UNIX, and the "X" device are registered trademarks in the U.S. and other countries, and IT DialTone and The Open Group are trademarks of The Open Group.

---

[ Home ] [ Testing Home ] [ Conformance Statement Library Home ] [ Search Conformance Statements ] [ Send Feedback ]