INMBLKSZ |
0030 |
1 |
1 to 8 bytes |
Blocksize of the file Example:
Specification of blocksize 32768.
KEY NUM LEN DATA
0030 0001 0004 00008000
|
INMCREAT |
1022 |
1 |
4 or more bytes |
Creation date of the file, in
standard format. Example: Specification of September
25, 1987.
KEY NUM LEN DATA
1022 0001 0008 F1F9F8F7F0F9F2F5
|
INMDDNAM |
0001 |
1 |
Length of name |
DDNAME associated with the file. Example:
Specification of DDNAME DD1.
KEY NUM LEN DATA
0001 0001 0003 C4C4F1
|
INMDIR |
000C |
1 |
1 to 8 bytes |
Number of directory blocks in
the file. Example: Specification of 15 directory blocks.
KEY NUM LEN DATA
000C 0001 0003 00000F
|
INMDSNAM |
0002 |
Number of fields in file name |
Length of file name field |
Name of the file. File
names are divided into fields. In MVS™,
the name contains a maximum of 22 fields, each having at most 8 characters.
The fields are separated by periods: AA.BB.CC.DD is an example.
The total length, including the periods, must not exceed 44 characters.
In
CMS, file names have three fields: filename, filetype, and filemode,
with a maximum length of 8, 8, and 2 characters, respectively. The
fields are separated by blanks: REPORT SCRIPT A1 is an example.
When
transmitting a CMS file, the filemode character (but not the number)
is specified in this text unit. The filemode number is specified
in the INMFFM text unit. The filemode character is the first field
of the file name.
Note that TSO/E data set names are transmitted
differently in control records than in the text units available to
installation exits through text unit pointer lists (as shown in the
examples that follow). In the text units pointed to from text unit
pointer lists, the name is sent as a single length-data pair. In
control records, each part of the name and its length is a separate
length-data pair.
Example: Specification of TSO/E data
set A.B in text units available through pointer lists.
KEY NUM LEN DATA
0002 0001 0003 C14BC2
Example: Specification
of TSO/E data set A.B in INMR02 control records.
KEY NUM LEN1 DATA1 LEN2 DATA2
0002 0002 0001 C1 0001 C2
|
INMDSORG |
003C |
1 |
2 bytes |
The file organization, either: - X'0008'
- for VSAM
- X'0200'
- for partitioned organization
- X'4000'
- for physical sequential
Example: Specification of a physical sequential
file.
KEY NUM LEN DATA
003C 0001 0002 4000
|
INMEATTR |
8028 |
1 |
1 byte |
Extended attribute status.
It can be in any of the following formats:- X'00'
- Unspecified
- X'01'
- NO
- X'02'
- OPT
Example: Specification of EATTR as OPT.
KEY NUM LEN DATA
8028 0001 0001 02
|
INMERRCD |
1027 |
1 |
1 or more bytes |
A string indicating the result
of the RECEIVE operation. Example: Specification that
the transmitted file was "RECEIVED".
KEY NUM LEN DATA
1027 0001 0008 D9C5C3C5C9E5C5C4
|
INMEXPDT |
0022 |
1 |
4 or more bytes |
Expiration date of the file, in
standard format. Example: Specification of January
1, 1988.
KEY NUM LEN DATA
0022 0001 0008 F1F9F8F8F0F1F0F1
|
INMFACK |
1026 |
1 |
1 to 64 bytes |
Blanks or a notification string
that the issuer of TRANSMIT specified. This text unit exists
only if the sender (or installation exit) requested acknowledgment
that the transmitted file was received. If the sender also specified
a notification string to identify the transmission, that string is
in the text unit data field. If no string was specified, the length
and data fields are blank.
Example: Specification of
notification with string FRED.
KEY NUM LEN DATA
1026 0001 0004 C6D9C5C4
Example: Specification
of notification without a string.
KEY NUM LEN DATA
1026 0001
|
INMFFM |
102D |
1 |
1 byte |
Filemode number of a CMS file. Example:
Specification of filemode number 0.
KEY NUM LEN DATA
102D 0001 0001 F0
|
INMFNODE |
1011 |
1 |
Length of node name or number |
Name or number of the origin node. Example:
Specification of node VENICE.
KEY NUM LEN DATA
1011 0001 0006 E5C5D5C9C3C5
|
INMFTIME |
1024 |
1 |
4 or more bytes |
The time the transmission was
created, in standard format. Example: Specification
of July 19, 1987 at 3:20 PM.
KEY NUM LEN DATA
1024 0001 000C F1F9F8F7F0F7F1F9F5F2F0
|
INMFUID |
1012 |
1 |
Length of user ID |
User ID of the originator of the
transmission. If the transmission is a file, the originator
is the issuer of TRANSMIT. If the transmission is an acknowledgment,
the originator is the issuer of the acknowledgment.
Example:
Specification of user ID IMBUSER.
KEY NUM LEN DATA
1012 0001 0007 C9C2D4E4E2C5D9
|
INMFVERS |
1023 |
1 |
1 to 8 bytes |
The version number of the data
format used for the transmission. Example: Specification
of version 1.
KEY NUM LEN DATA
1023 0001 0004 00000001
|
INMLCHG |
1021 |
1 |
4 or more bytes |
Date the file was last changed,
in standard format. Example: Specification of April
1, 1987 at 8:12 PM.
KEY NUM LEN DATA
1021 0001 000E F1F9F8F7F0F4F0F1F2F0F1F2
|
INMLRECL |
0042 |
1 |
1 to 8 bytes |
The actual or maximum number of
bytes in the logical record in the file. Example: Specification
of 80-byte records.
KEY NUM LEN DATA
0042 0001 0001 50
|
INMLREF |
1020 |
1 |
4 or more bytes |
Date the file was last referenced,
in standard format. Example: Specification of February
14, 1988.
KEY NUM LEN DATA
1020 0001 0008 F1F9F8F7F0F2F1F4
|
INMLSIZE |
8018 |
1 |
4 bytes |
Size of the file in megabytes
(MB). Note: The value in this text unit for a partitioned data
set specifies the size of the PDS, not the size of a member.
Example:
Specification of a two gigabyte file.
KEY NUM LEN DATA
8018 0001 0004 00000800
|
INMMEMBR |
0003 |
1 or more |
Length of member name |
List of member names. If
more than one member is being transmitted, there are multiple length-data
field pairs, one for each member.
Example: Specification
of members IEASYS00 and A.
KEY NUM FLGS LEN1 DATA1
0003 0002 xxxx 0008 C9C5C1E8E2F0F0
LEN2 DATA2
0001 C1
|
INMNUMF |
102F |
1 |
1 to 8 bytes |
Number of files that make up the
transmission. If any files are being transmitted, this text
unit must be in the INMR01 control record. If the text unit is missing,
the number of files is assumed to be zero, which is true only when
the transmission is an acknowledgment.
Example: Specification
of two files in the transmission.
KEY NUM LEN DATA
102F 0001 0004 00000002
|
INMRECCT |
102A |
1 |
1 to 8 bytes |
Number of records transmitted. Example:
Specification of 129 records.
KEY NUM LEN DATA
102A 0001 0001 81
|
INMRECFM |
0049 |
1 |
2 bytes |
The record format of the file. The
value is the result of "logically ORing" one or more of the following
values together: - X'0001'
- Shortened VBS format used for transmission records
- X'xx02'
- Varying length records without the 4-byte header
- X'0200'
- Data includes machine code printer control characters
- X'0400'
- Data contains ASA printer control characters
- X'0800'
- Standard fixed records or spanned variable records
- X'1000'
- Blocked records
- X'2000'
- Track overflow or variable ASCII records
- X'4000'
- Variable-length records
- X'8000'
- Fixed-length records
- X'C000'
- Undefined records
Example: Specification of fixed block
records.
KEY NUM LEN DATA
0049 0001 0002 9000
|
INMSECND |
000B |
1 |
3 bytes |
Secondary space quantity.
Example: Specification of 10 blocks.
KEY NUM LEN DATA
000B 0001 0003 00000A
|
INMSIZE |
102C |
1 |
4 bytes |
Size of the file in bytes. Note
that the value in text units for partitioned data sets specifies the
size of the PDS, not the size of a member.
Example:
Specification of a 1,000,000 bytes file.
KEY NUM LEN DATA
102C 0001 0004 000F4240
|
INMTERM |
0028 |
0 |
Omitted |
Omitted. This text unit indicates
that the data was transmitted as a message. Example: Specification
of transmitted data.
KEY NUM LEN DATA
0028 0000
|
INMTNODE |
1001 |
1 |
Length of node name |
Node name to which the transmission
is being sent Example: Specification of node ROME.
KEY NUM LEN DATA
1001 0001 0004 D9D6D4C5
|
INMTTIME |
1025 |
1 |
4 or more bytes |
The time the transmission was
received, in standard format. Example: Specification
of March 14, 1987 at 8:30 AM.
KEY NUM LEN DATA
1025 0001 000E F1F9F8F7F0F3F1F4F0F8F3F0
|
INMTUID |
1002 |
1 |
Length of user ID |
User ID to which the transmission
is being sent. Example: Specification of user ID IBMUSER.
KEY NUM LEN DATA
1002 0001 0007 C9C2D4E4E2C5C9
|
INMTYPE |
8012 |
1 |
1 byte |
Data set type. - X'80'
- Data library
- X'40'
- Program library
- X'04'
- Extended format sequential data set
- X'01'
- Large format sequential data set
Example: Specification of data library.
KEY NUM LEN DATA
8012 0001 0001 80
|
INMUSERP |
1029 |
1 |
1 to 251 bytes |
The character string specified
on the PARM keyword of the TRANSMIT or RECEIVE command. Example:
Specification of user string ‘PARM1’.
KEY NUM LEN DATA
1029 0001 0005 D7C1D9D4F1
|
INMUTILN |
1028 |
1 |
Length of name |
Name of the utility program that
is used in restoring the transmitted data to its original format. Currently
defined names are: - INMCOPY
- Invokes an internal utility to convert from the transmission format
to a sequential file.
- IEBCOPY
- Invokes the IEBCOPY utility to reload a partitioned file.
- AMSCIPHR
- Invokes the Access Method Services REPRO command to decrypt a
file.
Example: Specification of utility program
INMCOPY.
KEY NUM LEN DATA
1028 0001 0007 C9D5D4C3D6D7E8
|