Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

• Revised information about logging OSS File System EMS events to both $0 and $ZLOG in
“Event Management Service (EMS) Event Messages” (page 335).
• Added process information for the resource agent servers to “Summary of OSS Process
Information” (page 409).
• Added information in “OSS Environment Limits” (page 411):
OSS processes limits◦
◦ OSS File System resources, including new limits, EMS events, and how to view usages
and limits in SCF
• Added Open Source utilities and tools information to:
“Backing Up and Restoring OSS Files” (page 183)◦
◦ “Erasing and Removing OSS Files” (page 195)
◦ “Administrative Tools” (page 219)
◦ “Managing With the Shell” (page 235)
◦ “Compressing Files” (page 242)
• Revised information about the IOTIMEOUT attribute in:
“Currently Used TACL PARAMs for the OSS Monitor” (page 53)◦
◦ “ALTER SUBSYS, ALTER MON, and ALTER PROCESS Commands” (page 285)
◦ “INFO SUBSYS, INFO MON, and INFO PROCESS Commands” (page 307)
• Added new terms and definitions to “Glossary” (page 421).
Updated the inodes limits for a fileset to 100,000-2,200,000, which is modified with the
MAXINODES attribute in SCF. (See “Configuring the FILESET INODES Resource” (page 97).)
Added information throughout this guide about AF_INET sockets utilizing AF_INET socket data
buffers only when the process is configured on a Legacy TCP/IP address. If the process is configured
on a Parallel Library TCP/IP, TCP/IPv6, or CIP address, then AF_INET sockets do not utilize
AF_INET socket data buffers.
Corrected the limit of 99,999 for Device labels per node in “OSS Environment Limits” (page 411).
New and Changed Information in the 527191-014 Edition (February
2012)
• Revised the information about restricted-access filesets to indicate that the user ID you use
when creating or managing restricted-access filesets must not be a member of the Safeguard
SECURITY-OSS-ADMINISTRATOR (SOA) group in addition to not being the super ID (255,255).
• Updated the message text for messages OSS E00065 and OSS E00067.
• Added “Falling Back to a Previous Release Version Update or Upgrading to a New Release
Version Update” (page 393), which describes additional steps you must perform when falling
back to a previous RVU or upgrading to a new RVU if you are not using NonStop Software
Essentials or DSM/SCM to manage your OSS files.
• Updated references to DSM/SCM throughout this guide to include references to NonStop
Software Essentials.
New and Changed Information in the 527191-014 Edition (February 2012) 19