Assessments - 0, GPA: 0
(
)
)
|
por este dispositivo também tem outras instruções :
Facilidade de uso
Operating System
Interoperability
• Interoperability for opens of Guardian C files:
As of G06.29, OSS can create Guardian files in the /G name space through
creat64() and open64(). The resulting files, regardless of size, are Guardian
Format 2 C files with file code 180. If a program running on any RVU attempts to
open this type of file through FILE_OPEN_ without 64-bit elections, the open
succeeds if the file is smaller than approximately 4 GB and fails if it is larger than 4
GB.
If the open call includes 64-bit elections and is issued on a G06.29 or later RVU,
the open succeeds regardless of file size.
If an application running on a pre-G06.29 system invokes FILE_OPEN_ with 64-bit
elections, the open succeeds. However, if the file size is smaller than 4 GB, the file
size limit for that open is 4 GB. If the file size is larger than 4 GB, the file size limit
for that open is the limit defined at file-creation time.
• Compatibility issue with Guardian files created by OSS APIs:
For G06.29, OSS adds support for files greater than 2 GB and adds related 64-bit
OSS APIs. Previously, OSS files were always Guardian Format 1, but now may be
Format 1 or Format 2. For applications using OSS APIs to access OSS files, the
format is not visible and there are no known compatibility issues. For applications
using Enscribe APIs to access Guardian files created by OSS APIs there is a
known compatibility issue.
Prior to G06.29, Guardian files created by OSS APIs were always format 1 with a
175 MB maximum size. As of G06.29, Guardian files created by the open() and
creat() APIs are Guardian Format 1 with an approximate 2 GB maximum size, and
Guardian files created by the open64() and creat64() APIs are Guardian Format 2
with an approximate 26 GB maximum size.
The standard OSS utilities, such as cp, pax and pinstall, now use open64() and
creat64() and thus create a Guardian Format 2 file when given a /G output file
name.
Example:
cp myfile /G/disk/subvol/myfile
Guardian applications that use file attributes such as file format and maximum size
are likely to be affected. These programs may fail when unexpected values are
returned (such as Format 2 if only Format 1 is expected).
Guardian applications that use file data and ignore file attributes are unaffected, if
running on G06.29 and the Format 2 file is unstructured, code 180 with an EOF
less than the Format 1 limit of approximately 4 GB. However, FILE_OPEN_ fails
with error 580, if the RVU is pre-G06.29, or if the file code is not 180, or if the EOF
is greater than the Format 1 limit.
Recovery choices include:
° Choice 1 - Change the application to accept Guardian Format 2 files.
G06.29 Release Version Update Compendium — 542946-001
2 -7
... Este manual também é adequado para os modelos :
Computadores - HP NonStop G-Series (118.64 kb)
Computadores - HP NonStop L-Series (118.64 kb)