DCE Application Programming Guide

NonStop DCE Application Development
Environment
HP NonStop DCE Application Programming Guide429551-003
1-7
Working in the Application Development
Environment
°
The chpass and su utilities are not implemented.
°
Integration of DCE login with the local operating system login into a single
operation is not supported.
The DCE registry and the local NonStop operating system user IDs are not
integrated. A user must log on to the NonStop system with an operating
system user ID and start an OSS shell before executing the dce_login utility.
Keytab and credential files are protected by local OSS security.
These principal registry attributes are not used by dce_login:
Home directory
Login shell
UID (referred to as UNIX ID in DCE documentation and sometimes as
user ID in OSS documentation)
Instead, the dce_login utility uses the OSS HOME and SHELL environment
variables. NonStop operating system user IDs are used in place of UIDs. No
mechanism exists for changing the user ID within the dce_login utility.
NonStop DCE internationalization has these limitations:
°
Only the default C/POSIX locale supported within the standard C run-time
library is provided. Any attempt to set the locale to another value fails; the
offending program continues to run, however, using the C/POSIX default
locale.
°
The only available automatic character code set conversion is between ASCII
and EBCDIC.
°
Only a single message catalog is supplied.
NonStop DCE does not include a distributor-agent extension.
Working in the Application Development
Environment
The information in this subsection can guide designers working in the NonStop DCE
application development environment. Topics covered include:
Environmental Dependencies on page 1-8
A Sample DCE Application on page 1-8
The Location of Files on page 1-9
Using DCE Documentation on page 1-9