G06.27 ReadMe
G06.27 README
Copyright (C) 2005 Hewlett-Packard Development Company, L.P.
Protected as an unpublished work.
All rights reserved.
The computer program listings, specifications, and documentation
herein are the property of Hewlett-Packard Development Company, L.P.
or a third-party supplier and shall not be reproduced, copied,
disclosed, or used in whole or in part for any reason without the
prior express written permission of Hewlett-Packard Development
Company, L.P.
This README (SUT) file contains information that was not available
at the time manuals, softdocs, and other release materials were
produced. This file contains only information pertinent to the
G06.27 Release Version Update (RVU).
See the online NonStop Technical Library (NTL) support collection for
the latest version of the README file.
----------------------------------------------------------------------
G06.27 README file
----------------------------------------------------------------------
o Enscribe Filesystem (T9055)
Solution 10-050722-0066
If a child process is created in a CPU that is different from
that of the parent, and if any of the opened files in the parent
process has as many I/Os pending as nowait depth for the file,
tdm_spawn() fails with error 28.
Recovery
None.
Workaround
Do not have any I/O outstanding on $RECEIVE when calling
tdm_spawn.
o EXPAND (T9057)
Solution 10-050427-7173
1. An application's write request on a EXPAND ATMSAP line may
return error 249 (Network error: operation aborted).
2. Copying of files using the FUP DUP command over an EXPAND ATMSAP
line may hang. FUP INFO output_file_name on a destination
system output will be as follows:
CODE EOF LAST MODIFIED OWNER RWEP PExt SExt
ZSTOSCF OC 100 2506752 18JUN2005 0:19 255,255 NNNN 542 16
This problem occurs only when the following conditions are met:
- The EXPAND LINE is configured with PROFILE modifier set to
PEXPSATM and CALLTYPE modifier set to ATMSAP.
Page
1
of
5