forked from moshix/UnixNJE
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathnetdata.descript
1364 lines (747 loc) · 41.3 KB
/
netdata.descript
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
Netdata: A Transmission Format for Network Data. Netdata: A Transmission Format for Network Data. Netdata: A Transmission Format for Network Data. Netdata: A Transmission Format for Network Data.
7 May 1981
John D. Palmer
Robert P. O'Hara
TABLE OF CONTENTS TABLE OF CONTENTS TABLE OF CONTENTS TABLE OF CONTENTS _________________
Netdata Format . . . . . . . . . . . . . . . . . . . . . 3 Netdata Format . . . . . . . . . . . . . . . . . . . . . 3 Netdata Format . . . . . . . . . . . . . . . . . . . . . 3 Netdata Format . . . . . . . . . . . . . . . . . . . . . 3
Control Record Formats . . . . . . . . . . . . . . . . . 6 Control Record Formats . . . . . . . . . . . . . . . . . 6 Control Record Formats . . . . . . . . . . . . . . . . . 6 Control Record Formats . . . . . . . . . . . . . . . . . 6
INMR01 -- Header Record . . . . . . . . . . . . . . . . . 6
INMR02 -- File Utility Control Record . . . . . . . . . . 6
INMR03 -- Data Control Record . . . . . . . . . . . . . . 8
INMR04 -- User Control Record . . . . . . . . . . . . . . 8
INMR06 -- Trailer Control Record. . . . . . . . . . . . . 8
INMR07 -- Acknowledgement Control Record . . . . . . . . 8
Text Units . . . . . . . . . . . . . . . . . . . . . . 10 Text Units . . . . . . . . . . . . . . . . . . . . . . 10 Text Units . . . . . . . . . . . . . . . . . . . . . . 10 Text Units . . . . . . . . . . . . . . . . . . . . . . 10
Text Unit Keys . . . . . . . . . . . . . . . . . . . . 11
Table of Contents 2
NETDATA FORMAT NETDATA FORMAT NETDATA FORMAT NETDATA FORMAT ______________
Netdata is a format in which files can be transmitted from
one computer user or system to another. The data transmit-
ted are the original file, plus enough descriptive informa-
tion to enable the file to be reconstituted at the receiving
end. The transmitted data are defined as a continuous
stream of bytes. While our current network imposes on us
the nostalgic notion of "card images", the "records" de-
scribed herein are logical records (of varying length), and _______
card boundaries are ignored.
The format of the transmitted file is shown in Figure 1 on
page 4. Several control records begin the file, followed by
the data records. A trailer record brings up the rear. An
acknowledgement file is composed of only control records.
If the transmission contains more than one file, the data
records of the multiple files will be separated by a con-
trol record.
Netdata Format 3
------------------------------------------------------------
A Transmission of One File:
+----------------------------------------------------------+
| CONTROL RECORDS |
+----------------------------------------------------------+ | |
| |
| DATA RECORDS |
| |
+----------------------------------------------------------+ | |
| TRAILER RECORD |
+----------------------------------------------------------+
A Transmission of Two Files:
+----------------------------------------------------------+
| CONTROL RECORDS |
+----------------------------------------------------------+ | |
| |
| DATA RECORDS - FILE 1 |
| |
+----------------------------------------------------------+ | |
| CONTROL RECORD |
+----------------------------------------------------------+ | |
| |
| DATA RECORDS - FILE 2 |
| |
+----------------------------------------------------------+ | |
| TRAILER RECORD |
+----------------------------------------------------------+
Figure 1. File format
------------------------------------------------------------
The control records and data records have the same format,
which is shown in Figure 2 on page 5. The data portion of a
control record begins with a 6 byte identifier. Following
the identifier are 0 or more "text units", which are de-
scribed below. An exception to this is the INMR02 control
record, in which the data portion begins with a 4 byte file
count field. This field is then followed by the text units.
Each record (both control and data) begins in the byte imme-
diately following the end of the previous record. The re-
cords of the file to be transmitted are broken up into
segments, whose format is shown in Figure 2 on page 5. A
segment has a maximum length of 255 bytes, including the 2
byte header. If the length of a record in the file is
greater than 253 bytes, it is sent as multiple segments.
Netdata Format 4
------------------------------------------------------------
+----------------------------------------------------------+ + +
| LEN | FLAGS | DATA... |
| 1 | 2 | 3-len |
+----------------------------------------------------------+ + +
Byte Length Contents
1 1 Length of segment including 2-byte header (2<=len<=255).
2 1 Segment descriptor flags:
x'80' - First segment of original record.
x'40' - Last segment of original record.
x'20' - (part of a) Control record.
x'10' - Record number of next record.
x'0F' - Reserved for future use.
3 n User data segment (0<=n<=253).
Figure 2. Data Record Format
------------------------------------------------------------
Netdata Format 5
CONTROL RECORD FORMATS CONTROL RECORD FORMATS CONTROL RECORD FORMATS CONTROL RECORD FORMATS ______________________
A control record will contain a length field in byte 1, a
flag field in byte 2, and the control record name in bytes
3-8 of the record. The data begin in byte 9. These data
are composed of a varying number of text units, except for
the INMR02 control unit, in which the text units are pre-
ceded by a 4 byte file number field.
INMR01 -- HEADER RECORD INMR01 -- HEADER RECORD INMR01 -- HEADER RECORD INMR01 -- HEADER RECORD _______________________
The INMR01 record is always the first record of a trans-
mission. The identifier of the record is "INMR01" in bytes
3-8. The remainder of the record (beginning with byte 9) is
composed of text units.
Required text units are:
INMFNODE Origin node name.
INMFTIME Origin time stamp.
INMFUID Origin userid.
INMLRECL Length of physical control record segments.
INMTNODE Target node name.
INMTUID Target userid.
Optional text units are:
INMFACK Receipt notification requested. If not present,
no receipt notification is requested.
INMFVERS Origin version number. If not present, version
"1" is assumed.
INMNUMF Number of files in this transmission. If not
present, there can only be 1 file in the trans-
mission.
INMUSERP user parameter string.
INMR02 -- FILE UTILITY CONTROL RECORD INMR02 -- FILE UTILITY CONTROL RECORD INMR02 -- FILE UTILITY CONTROL RECORD INMR02 -- FILE UTILITY CONTROL RECORD _____________________________________
Each INMR02 record controls a data transformation step. In
a given transmission, one or more processes represented by a
corresponding number of INMR02 records are required. Util-
ity operations currently supported are:
INMCOPY which converts sequential files to and from the INMCOPY INMCOPY INMCOPY
netdata format.
Control Record Formats 6
IEBCOPY which converts partitioned files to and from se- IEBCOPY IEBCOPY IEBCOPY
quential files (called "unloaded" files).
AMSCIPHR which invokes the Access Method Services REPRO AMSCIPHR AMSCIPHR AMSCIPHR
command to encrypt and decrypt files.
If more than one INMR02 record is present, they will appear
in inverse order. The first record in the data stream will
represent the last utility operation performed by RECEIVE.
Note that the INMCOPY utility is always the last (or only)
utility invoked during a SEND (TRANSMIT) operation, and thus
appears first in the file. The text units of the INMR02 re-
cord describe the result of the transformation operation.
The input with which it must work is described by the previ-
ous INMR02-directed operation or by the INMR03 data de-
scription record.
If the transmission contains more than one file, one or more
INMR02 records are required for each file in the trans-
mission. The groups of INMR02 records are in the same order
as the files in the transmission. The file number field
(which precedes the text units in the INMR02 record) identi-
fies to which of the multiple files in the transmission the
particular INMR02 record applies.
The identifier for this record is "INMR02" in bytes 3-8.
Bytes 9-12 contain the number of the file in this trans-
mission to which the control record applies. Multiple files
in a single transmission are numbered sequentially starting
at 1. The text units begin in byte 13.
Required text units are:
INMDSORG File organization.
INMLRECL Logical record length.
INMRECFM Record format.
INMSIZE Approximate size of file in bytes.
INMUTILN Utility program name.
Also required are either of the following:
INMDSNAM File name.
INMTERM Mail file.
Optional text units are:
INMBLKSZ File block size.
INMCREAT Creation date.
INMDIR Number of directory blocks.
INMEXPDT Expiration date.
INMFM Filemode number.
INMLCHG Last change date.
INMLREF Last reference date.
INMMEMBR Member name list.
INMUSERP User parameter string.
Control Record Formats 7
INMR03 -- DATA CONTROL RECORD INMR03 -- DATA CONTROL RECORD INMR03 -- DATA CONTROL RECORD INMR03 -- DATA CONTROL RECORD _____________________________
The INMR03 record immediately precedes the transmitted data
and identifies their format.
The identifier for this record is "INMR03" in bytes 3-8.
The text units begin in byte 9.
Required text units are:
INMDSORG File organization.
INMLRECL Logical record length.
INMRECFM Record format.
INMSIZE Approximate size of file in bytes.
INMR04 -- USER CONTROL RECORD INMR04 -- USER CONTROL RECORD INMR04 -- USER CONTROL RECORD INMR04 -- USER CONTROL RECORD _____________________________
The INMR04 record may appear anywhere among the control re-
cords. It contains user data to be passed to user exits
during the RECEIVE operation, if such exits are implemented.
The identifier for this record is "INMR04" in bytes 3-8.
The text units begin in byte 9.
Required text units are:
INMUSERP User parameter string.
INMR06 -- TRAILER CONTROL RECORD. INMR06 -- TRAILER CONTROL RECORD. INMR06 -- TRAILER CONTROL RECORD. INMR06 -- TRAILER CONTROL RECORD. _________________________________
The INMR06 record is always the last record in a trans-
mission. This record is used to verify that the trans-
mission is complete.
The identifier for this record is "INMR06" in bytes 3-8.
The text units begin in byte 9, however no text units are
presently defined for this record.
INMR07 -- ACKNOWLEDGEMENT CONTROL RECORD INMR07 -- ACKNOWLEDGEMENT CONTROL RECORD INMR07 -- ACKNOWLEDGEMENT CONTROL RECORD INMR07 -- ACKNOWLEDGEMENT CONTROL RECORD ________________________________________
The INMR07 record indicates acknowledgement of a previous
transmission. When it appears, the transmission will con-
sist of only the INMR01, INMR07, and INMR06 records (in that
order).
Control Record Formats 8
The identifier for this record is "INMR07" in bytes 3-8.
The text units begin in byte 9.
Required text units are:
INMFTIME Origin time stamp.
Also required are either of the following:
INMDSNAM File name.
INMTERM Mail file.
Optional text units are:
INMERRCD Error indication for the RECEIVE operation. If
not present, a sucessful RECEIVE operation is as-
sumed.
INMFACK Acknowledgement id.
INMFFM Filemode number.
INMUSERP User parameter string.
Control Record Formats 9
TEXT UNITS TEXT UNITS TEXT UNITS TEXT UNITS __________
Text units are used to describe the information contained in
the transmission control records. The format of a single
text unit is:
Offset Length Value
+0 2 Text unit key. The key identifies the in-
formation in the text unit. Possible values
for the key are given in the section "Text
Unit Keys".
+2 2 Count. The count field contains the number
of "length-value" fields which follow.
+4 2 Length field. The first of perhaps many
length fields. The length value includes
only the length of the following value field
and not its own 2-byte length.
+6 n Value field. The first of perhaps many
value fields. The format of the field is
specified for each text unit key. The
length of the field is specified by the pre-
ceding length field.
6+n Second length-value entry if the count
field indicated more than one entry present.
Each text unit immediately follows the previous text unit.
Dates and Times Dates and Times Dates and Times Dates and Times
All dates and times are expressed in GMT. For all text
units where a date or time is specified, the value field
will have a standard format: EBCDIC characters for the
year(4), month(2), day(2), hour(2), minute(2), second(2),
and fraction of seconds(n). Only as much as is known of
this time value need be specified. E.G. if only the year is
known the value would be 'YYYY'. If microseconds are known,
the value would be 'YYYYMMDDHHMMSSUUUUUU'.
Numeric Values Numeric Values Numeric Values Numeric Values
All numeric values may be specified with a length of 1 to 8
bytes. Current implementations use only the low-order 4
bytes if the field is longer than 8 bytes.
Text Units 10
TEXT UNIT KEYS TEXT UNIT KEYS TEXT UNIT KEYS TEXT UNIT KEYS ______________
The following text units are currently defined:
Text Unit Mnemonic Function
Key (hex)
0030 INMBLKSZ Block size
1022 INMCREAT Creation date
0001 INMDDNAM DDname for the file
000C INMDIR Number of directory blocks
0002 INMDSNAM Name of the file
003C INMDSORG File organization
1027 INMERRCD RECEIVE command error code
0022 INMEXPDT Expiration date
1026 INMFACK Originator requested notification
102D INMFFM Filemode number
1011 INMFNODE Origin node name
1024 INMFTIME Origin time stamp
1012 INMFUID Origin userid
1023 INMFVERS Origin version number
1021 INMLCHG Last change date
0042 INMLRECL Logical record length
1020 INMLREF Last reference date
0003 INMMEMBR Member name list
102F INMNUMF Number of files
102A INMRECCT Transmitted record count
0049 INMRECFM Record format
102C INMSIZE File size in bytes
0028 INMTERM Mail file
1001 INMTNODE Target node name
1025 INMTTIME Destination time stamp
1002 INMTUID Target userid
1029 INMUSERP User parameter string
1028 INMUTILN Name of utility function
Blocksize specification - Key = X'0030' Blocksize specification - Key = X'0030' Blocksize specification - Key = X'0030' Blocksize specification - Key = X'0030'
INMBLKSZ specifies the block size of the file. When this
key is specified, NUM is 1, LEN is 1 to 8, and PARM contains
the blocksize of the file.
Example: specification of blocksize 32768.
KEY NUM LEN PARM
0030 0001 0004 00008000
Text Units 11
Creation date specification - Key = X'1022' Creation date specification - Key = X'1022' Creation date specification - Key = X'1022' Creation date specification - Key = X'1022'
INMCREAT specifies the creation date of the file. When this
key is specified, NUM is 1, LEN is 4 or more, and PARM con-
tains the creation date in standard format.
Example: specification of August 28, 1969.
KEY NUM LEN PARM
1022 0001 0008 F1F9F6F9F0F8F2F8
Ddname specification - Key = X'0001' Ddname specification - Key = X'0001' Ddname specification - Key = X'0001' Ddname specification - Key = X'0001'
INMDDNAM specifies a ddname associated with the file. When
this key is specified, NUM is 1, LEN is the length of the
ddname field, and PARM contains the ddname.
Example: specification of the ddname DD1.
KEY NUM LEN PARM
0001 0001 0003 C4C4F1
Directory Block specification - Key = X'000C' Directory Block specification - Key = X'000C' Directory Block specification - Key = X'000C' Directory Block specification - Key = X'000C'
INMDIR specifies the number of blocks in the file. When
this is key is specified, NUM is 1, LEN is 1 to 8, and PARM
contains the number of directory blocks.
Example: specification of 15 directory blocks.
KEY NUM LEN PARM
000C 0001 0003 00000F
Dsname specification - Key = X'0002' Dsname specification - Key = X'0002' Dsname specification - Key = X'0002' Dsname specification - Key = X'0002'
INMDSNAM specifies the file name of the file. File names
are divided into "fields".
* In MVS a file is called a data set. In its name there ________
one or more "fields", and each field has a maximum
length of 8 characters. The fields are separated by pe-
riods; for example, AA.BB.CC.DD has 4 fields. The maxi-
mum length of the data set name, including all periods,
is 44 characters.
Text Units 12
* In CMS a file name is called a fileid. It always has ______
three fields that are separated by blanks (filename,
filetype and filemode, having a maximum of 8, 8 and 2
characters respectively).
When transmitting a CMS file, the filemode number is not
specified as part of the fileid. Instead, it is speci-
fied on the INMFFM text unit. The filemode letter is
considered to be the "highest qualifier" of the fileid,
so it is always transmitted as the first field.
When this key is specified, NUM is the number of fields in
the file name, and the LEN and PARM fields contain the
length and name of each field of the file name.
Example: specification of the file name "A.B".
KEY NUM LEN1 PARM1 LEN2 PARM2
0002 0002 0001 C1 0001 C2
Example: specification of the fileid "ABC EXEC A2".
KEY NUM LEN1 PARM1 LEN2 PARM2 LEN3 PARM3
0002 0003 0001 C1 0002 C1C2C3 0004 C5E7C5C3
File organization specification - Key = X'003C' File organization specification - Key = X'003C' File organization specification - Key = X'003C' File organization specification - Key = X'003C'
INMDSORG specifies the file organization. When this key is
specified, NUM is 1, LEN is 2, and PARM contains:
X'0008' for VSAM
X'0200' for partitioned organization
X'4000' for physical sequential
Example: specification of a physical sequential file.
KEY NUM LEN PARM
003C 0001 0002 4000
Error code specification - Key = X'1027' Error code specification - Key = X'1027' Error code specification - Key = X'1027' Error code specification - Key = X'1027'
INMERRCD indicates the result of the RECEIVE operation.
When this key is specified, NUM is 1, LEN is 1 or more, and
PARM will contain a string indicating the result of the re-
ceive operation.
Example: specification that the sent file was "RECEIVED".
Text Units 13
KEY NUM LEN PARM
1027 0001 0008 D9C5C3C5C9E5C5C4
Example: specification that the sent file was "DELETED".
KEY NUM LEN PARM
1027 0001 0007 C4C5D3C5E3C5C4
Expiration date specification - Key = X'0022' Expiration date specification - Key = X'0022' Expiration date specification - Key = X'0022' Expiration date specification - Key = X'0022'
INMEXPDT specifies the expiration date of the file. When
this key is specified, NUM is 1, LEN is 4 or more, and PARM
contains the expiration date value in standard format.
Example: specification of an expiration date of January 1,
1981.
KEY NUM LEN PARM
0022 0001 0008 F1F9F8F1F0F1F0F1
Acknowledge specification - Key = X'1026' Acknowledge specification - Key = X'1026' Acknowledge specification - Key = X'1026' Acknowledge specification - Key = X'1026'
INMFACK specifies that the origin has requested an acknowl-
edgement of receipt of the transmitted file. When this key
is specified, NUM is 0 or 1. If NUM is 1, LEN is 1 to 64
and PARM contains a transmission identifier to be returned
with the notification. The return is also made via this
text unit.
Example: specification notification request without id.
KEY NUM LEN PARM
1026 0000
Example: specification notification request with id FRED.
KEY NUM LEN PARM
1026 0001 0004 C6D9C5C4
Filemode number specification - Key = X'102D' Filemode number specification - Key = X'102D' Filemode number specification - Key = X'102D' Filemode number specification - Key = X'102D'
INMFFM specifies the filemode number of the file. When this
key is specified, NUM is 1, LEN is 1, and PARM contains the
filemode number of the file.
Text Units 14
Example: specification of filemode number of 0.
KEY NUM LEN PARM
102D 0001 0001 F0
Origin node name specification - Key = X'1011' Origin node name specification - Key = X'1011' Origin node name specification - Key = X'1011' Origin node name specification - Key = X'1011'
INMFNODE specifies the node name of the origin of this
transmission. When this key is specified, NUM is 1, LEN is
the length of the node name, and PARM is the name of the or-
igin node.
Example: specification of node VENICE.
KEY NUM LEN PARM
1011 0001 0006 E5C5D5C9C3C5
Origin time stamp specification - Key = X'1024' Origin time stamp specification - Key = X'1024' Origin time stamp specification - Key = X'1024' Origin time stamp specification - Key = X'1024'
INMFTIME specifies the time at which the transmission was
sent. When this key is specified NUM is 1, LEN is 4 or
more, and PARM is the time the transmission was created,
specified in standard format.
Example: Specification of July 19, 1951 at 3:20 PM.
KEY NUM LEN PARM
1024 0001 000C F1F9F5F1F0F7F1F9F1F5F2F0
Origin userid specification - Key = X'1012' Origin userid specification - Key = X'1012' Origin userid specification - Key = X'1012' Origin userid specification - Key = X'1012'
INMFUID specifies the userid of the origin of this trans-
mission. When this key is specified, NUM is 1, LEN is the
length of the userid, and PARM is the userid of the origin
of the transmission.
Example: specification of userid IBMUSER.
KEY NUM LEN PARM
1012 0001 0007 C9C2D4E4E2C5D9
Text Units 15
Origin version specification - Key = X'1023' Origin version specification - Key = X'1023' Origin version specification - Key = X'1023' Origin version specification - Key = X'1023'
INMFVERS specifies the version of the data format used for
this transmission. When this key is specified NUM is 1, LEN
is 1 to 8, and PARM is the version number of the data format
used.
Example: specification of version 1.
KEY NUM LEN PARM
1023 0001 0004 00000001
Last change date specification - Key = X'1021' Last change date specification - Key = X'1021' Last change date specification - Key = X'1021' Last change date specification - Key = X'1021'
INMLCHG specifies the last change date of the file. When
this key is specified, NUM is 1, LEN is 4 or more, and PARM
contains the last change date in standard format.
Example: specification of 04/01/81 8:12 PM.
KEY NUM LEN PARM
1021 0001 000E F1F9F8F1F0F4F0F1F2F0F1F2
Logical record length specification - Key = X'0042' Logical record length specification - Key = X'0042' Logical record length specification - Key = X'0042' Logical record length specification - Key = X'0042'
INMLRECL specifies the actual or maximum length, in bytes,
of a logical record in the file. When this key is speci-
fied, NUM is 1, LEN is1 to 8, and PARM contains either the
actual or maximum record length.
Example: specification of 80-byte records.
KEY NUM LEN PARM
0042 0001 0001 50
Last reference date specification - Key = X'1020' Last reference date specification - Key = X'1020' Last reference date specification - Key = X'1020' Last reference date specification - Key = X'1020'
INMLREF specifies the last reference date of the file. When
this key is specified, NUM is 1, LEN is 4 or more, and PARM
contains the last reference date in standard format.
Example: specification of February 14, 1981.
Text Units 16
KEY NUM LEN PARM
1020 0001 0008 F1F9F8F1F0F2F1F4
Member specification - Key = X'0003' Member specification - Key = X'0003' Member specification - Key = X'0003' Member specification - Key = X'0003'
INMMEMBR specifies a list of member names of the file. When
this key is specified, NUM is 1 or more and the LEN and PARM
fields will contain the length and name of each member.
Example: specification of the member IEASYS00.
KEY NUM LEN PARM
0003 0001 0008 C9C5C1E2E8E2F0F0
Example: specification of the members ABC and DEFG.
KEY NUM LEN1 PARM1 LEN2 PARM2
0003 0002 0003 C1C2C3 0004 C4C5C6C7
Number of Files - Key = X'102F' Number of Files - Key = X'102F' Number of Files - Key = X'102F' Number of Files - Key = X'102F'
INMNUMF specifies the number of files that make up this
transmission. It is required on the INMR01 control record
if there are more than zero files in the transmission. (If
this text unit is missing, number of files is assumed to be
zero. This makes sense only on an acknowledgement trans-
mission.) When this key is specified, NUM is 1, LEN is 1 to
8, and PARM contains the number of files that make up this
transmission.
Example: Specification of 2 files in this transmission.
KEY NUM LEN PARM
102F 0001 0004 00000002
Transmitted record count specification - Key = X'102A' Transmitted record count specification - Key = X'102A' Transmitted record count specification - Key = X'102A' Transmitted record count specification - Key = X'102A'
INMRECCT specifies a count of transmitted records. When
this key is specified, NUM is 1, LEN is 1 to 8, and PARM
contains the number of records transmitted.
Example: specification of 129 records.
KEY NUM LEN PARM
102A 0001 0001 81