143:
the file's format, and one or more steps ("utility programs") which must be executed in order to rebuild this file. The text units identify the file's organization (INMDSORG: sequential, partitioned, etc.), its fixed of maximum record length (INMLRECL), its record format (INMRECFM: fixed, variable, etc) the approximate size of the file (IBMSIZE), and the utility program name(s) (INMUTILN). It may also contain the file's block size, creation date, number of directory blocks, name, expiration date, file mode number, last change date, last reference date, member name list (for partitioned datasets), a note file, and a user parameter string.
142:
This record describes how the file's data is to be reconstituted. Its identifier is "INMR02". Bytes 8-11 contain the big-endian binary number of the file to which this record applies. If there are multiple files in a transmission they are numbered starting with one. The rest of this record describes
150:
The Data
Control Record immediately precedes the data and describes its format, similar to the Utility Control Record. Its identifier is "INMR03". This record is ignored by CMS, but is used by TSO/E. It contains the file's organization (INMDSORG), its record length (INMLRECL), its record format
134:
The header record must be the first record of a NETDATA file. It has the identifier "INMR01". It contains information identifying the sender: node (host), timestamp, and user id, the length of the control record segments, and the target (receiving) node and user id. It may optionally contain a
189:
Data records (identified by their flag value), follow the Data
Control Record, if present, and precede the Trailer Control Record. Records can be any size up to INMLRECL. They are sent as multiple segments of up to 253 bytes, split into 80 byte records for transmission, and reassembled by the
126:
binary number of length-data pairs that follow for this key (usually one), a two byte length field identifying the length of the text unit data, and a text unit of the specified length. Implementations are expected to ignore any text unit information not relevant to the receiving system.
135:
request for acknowledgement of receipt, the version number of the data format, the number of files in the transmission, and a "user parameter string." CMS allows only one file per transmission, but TSO/E and other systems may allow more than one.
173:
This record has an id of "INMR07". It is used by the receiving system to acknowledge receipt of a transmission. It contains one of the text units File Name (INMDSNM) or Note File (INMTERM) plus, optionally, the Origin Time Stamp (INMFTIME).
158:
The User
Control record can appear at any point in the data stream. Its identifier is "INMR04". If present it is ignored by CMS, but may be used by other systems. It contains only a User Parameter String (INMUSERP).
190:
receiver. Settings of the flags byte in each record mark the beginning, end, or a complete record of the file. Bytes of a record can contain any bit pattern. No character values are reserved.
73:
of the file. A segment has a maximum length of 255 bytes. With the length and flags a segment can contain up to 253 bytes of data.
234:
208:
289:
279:
53:
to allow the original file to be reconstituted on the receiving system. A complete NETDATA file consists of a number of
86:
X'40' - this is the last segment of a record. If the record requires only one segment the flags will contain X'C0'
111:
166:
This record marks the end of the file. Its identifier is "INMR06". No other data is defined for this record.
284:
273:
110:
identifier in bytes 2-7 following the length and flags. They contain a number of
27:
123:
46:
34:
264:
50:
17:
181:
note") "is a short communication, the kind usually done by letter.".
107:
37:
systems, although implementations are available for other systems.
178:
92:
X'10' - this segment contains the record number of the next record
239:
31:
69:
A one-byte length field containing the length of a logical
89:X'20' - this segment is part of a control record
30:used primarily for data transfer and storage on
83:X'80' - this is the first segment of a record
8:
16:For the Netdata system monitoring tool, see
235:"z/VM:CMS Commands and Utilities Reference"
209:"x/VM: CMS Macros and Functions Reference"
151:(INMRECFM), and the file size (IBMSIZE).
49:files containing unloaded file data plus
118:. Each text unit consists of a two byte
199:
122:identifying this text unit, a two-byte
106:Control records have a six-character
7:
265:Netdatax - NETDATA command for Linux
65:. All records have the same format:
14:
177:A note file (sometimes called a "
80:field describing this segment:
170:Acknowledgement Control Record
1:
139:File Utility Control Record
306:
45:NETDATA files are 80-byte
15:
163:Trailer Control Record
290:VM (operating system)
280:Computer file formats
131:Header Control Record
213:IBM Knowledge Center
112:self-defining fields
61:and terminated by a
155:User Control Record
147:Data Control Record
233:IBM Corporation.
207:IBM Corporation.
297:
252:
251:
249:
247:
230:
224:
223:
221:
219:
204:
95:X'0F' - reserved
305:
304:
300:
299:
298:
296:
295:
294:
270:
269:
261:
256:
255:
245:
243:
232:
231:
227:
217:
215:
206:
205:
201:
196:
187:
172:
165:
157:
149:
141:
133:
104:
102:Control records
55:control records
43:
21:
12:
11:
5:
303:
301:
293:
292:
287:
282:
272:
271:
268:
267:
260:
259:External links
257:
254:
253:
225:
198:
197:
195:
192:
186:
183:
103:
100:
99:
98:
97:
96:
93:
90:
87:
84:
74:
63:trailer record
57:, followed by
42:
39:
13:
10:
9:
6:
4:
3:
2:
302:
291:
288:
286:
283:
281:
278:
277:
275:
266:
263:
262:
258:
242:
241:
236:
229:
226:
214:
210:
203:
200:
193:
191:
184:
182:
180:
175:
171:
167:
164:
160:
156:
152:
148:
144:
140:
136:
132:
128:
125:
121:
120:text unit key
117:
113:
109:
101:
94:
91:
88:
85:
82:
81:
79:
75:
72:
68:
67:
66:
64:
60:
56:
52:
48:
40:
38:
36:
33:
29:
25:
19:
285:IBM software
244:. Retrieved
238:
228:
216:. Retrieved
212:
202:
188:
185:Data records
176:
169:
168:
162:
161:
154:
153:
146:
145:
138:
137:
130:
129:
119:
115:
105:
77:
70:
62:
59:data records
58:
54:
44:
23:
22:
76:A one-byte
41:Description
28:file format
274:Categories
194:References
124:big-endian
116:text units
47:card image
114:, called
35:mainframe
51:metadata
71:segment
24:NETDATA
18:Netdata
246:Sep 6,
218:Sep 5,
108:EBCDIC
179:PROFS
78:flags
26:is a
248:2019
220:2019
240:IBM
32:IBM
276::
237:.
211:.
250:.
222:.
20:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.