Object link information entries are output in the format described in the table below. The Entry type value in the entry header determines if the entry associated with the header is a object link information entry.
The system associates a coded character set identifier (CCSID) with all data including object link names.
This association is maintained across all save and restore operations.
For each field, an offset is specified in bytes. This offset is relative to the base address of the entry, or the beginning of the first field in the entry header.
Table 47. Object link information entry–Output from SAV and RST Commands Offset (bytes)
Type (in bytes) Set by1 Field Decimal Hex
0 0 BINARY(8) S/R See the table in Entry header information for more format details.
8 8 BINARY(4) S/R Object link identifier offset2
12 C BINARY(4) R Object link identifier after restore operation offset3
16 10 BINARY(4) S/R Starting volume identifier offset4
20 14 BINARY(4) S/R Object link error message replacement identifier offset5
24 18 BINARY(4) S/R Object link size
28 1C BINARY(4) S/R Object link size multiplier
32 20 BINARY(4) S/R ASP at time of save operation
36 24 BINARY(4) R ASP after restore operation
40 28 CHAR(10) S/R Object link type
50 32 CHAR(8) S/R Save active date/time
58 3A CHAR(10) S/R Object link owner at time of save
68 44 CHAR(10) R Object link owner after restore
78 4E CHAR(50) S/R Object link text
128 80 CHAR(1) R Object link security message
129 81 CHAR(1) S/R Object link status
130 82 CHAR(7) S/R Object link error message ID
137 89 CHAR(1) S/R Object link data
138 8A BIN(8) (blank) Reserved
146 92 CHAR(1) S/R Allow checkpoint write
147 93 CHAR(10) S/R ASP device name at time of save operation
157 9D CHAR(10) R ASP device name after restore operation
167 A7 CHAR(1) S In mounted UDFS
168 A8 CHAR(4) (blank) Reserved
172 AC BINARY(4) S/R Journal information required for recovery offset6
176 B0 BINARY(4) S/R Journal receiver information required for recovery offset7
Table 47. Object link information entry–Output from SAV and RST Commands (continued) Offset (bytes)
Type (in bytes) Set by1 Field Decimal Hex
180 B4 BINARY(4) S/R Mounted file system information offset8
184 B8 BINARY(4) S/R Number of private authorities saved
188 BC BINARY(4) R Number of private authorities restored
192 C0 BINARY(4) S Number of positions
196 C4 BINARY(4) S Position information offset9
Notes:
1. Set by column.Each value in this column is set when:
Value Condition
S Save operation set this field.
R Restore operation set this field.
S/R Either operation set this field.
(blank)
Not set by either operation. The associated field is set to zero for numeric fields, blank for character fields, or empty for variable-length character fields.
2. Format of object link identifier.You can find the start of the object link identifier using the Object link identifier offsetfield. An object link identifier will consist of a length followed by the object link name. The object link fields are not repeated.
The CCSID of the object link name can be found by using CCSID of data field from the Command information format.
Type (in bytes) Content Field
BINARY(4) S/R Object link identifier length
CHAR(*) S/R Object link identifier
3. Format of object link identifier after restore operation.You can find the start of the object link identifier after the restore operation by using the Object link identifier after restore operation offset field. An object link identifier will consist of a length followed by the object link name. The object link identifier fields are not repeated.
The CCSID of the object link name can be found by using CCSID of data field from the Command information format.
Type (in bytes) Content Field
BINARY(4) S/R Object link identifier after restore operation length CHAR(*) R Object link identifier after restore operation
4. Format of starting volume identifier.You can find the first entry by using the Starting volume identifier offsetfield. The volume identifier consists of a length followed by the volume name. The volume identifier fields are not repeated.
Type (in bytes) Content Field
BINARY(4) S/R Starting volume identifier length
CHAR(*) S/R Starting volume identifier
5. Format of object link error message replacement identifier. You can find the start of the object link error message replacement identifier using the Object link error message replacement identifier offsetfield. An object link error message will consist of a length followed by a name. The error message replacement identifier fields are not repeated.
Type (in bytes) Content Field
BINARY(4) S/R Object link error message replacement identifier length CHAR(*) S/R Object link error message replacement identifier
6. Format of journal information required for recovery. You can find the start of the entry by using the Journal information required for recovery offsetfield. Journal information required for recovery will consist of a length followed by the journal path name. The journal fields are not repeated.
The CCSID of the journal receiver path name can be found by using CCSID of data field from the Command information format. For information about converting this name, see the iconv API.
Type (in bytes) Content Field
BINARY(4) S/R Journal information required for recovery - path name length CHAR(*) S/R Journal information required for recovery - path name
7. Format of journal receiver information required for recovery. You can find the start of the entry using the Journal receiver information required for recovery offset field. Journal receiver information required for recovery will consist of an ASP device name, a length, and the journal receiver path name. The journal receiver fields are not repeated.
The CCSID of the journal receiver path name can be found by using CCSID of data field from the Command information format. For information about converting this name, see the iconv API.
Type (in bytes) Content Field
CHAR(10) S/R Journal receiver information required for recovery - ASP device name
CHAR(2) (blank) Reserved
BINARY(4) S/R Journal receiver information required for recovery - path name length CHAR(*) S/R Journal receiver information required for recovery - path name
8. Format of mounted file system information.You can find the start of the mounted file system information using the Mounted file system information offset field. The mounted file system information consists of a length followed by the name.
Type (in bytes) Content Field
BINARY(4) S/R Mounted file system name length
CHAR(*) S/R Mounted file system name
9. Format of position information.You can find the start of the Position information by using the Position information offsetfield. The Position information consists of a Media file identifier
followed by Starting position in file. The Position information field repeats for Number of positions times.
Type (in bytes) Content Field
BINARY(8) S Media file identifier
CHAR(32) S Starting position in file