Standard or predefined types are one character long or they begin with $ or SYS:
Type | Meaning |
$... | Reserved |
C | Phases (load modules) |
D | Documents |
F | IFG format masks |
H | Compiler result information |
J | Procedures and ENTER jobs |
L | Link and load modules (LLMs) |
M | Macros |
P | Edited data |
R | Object modules |
S | Source programs |
SYS... | Reserved |
SYSJ.. | Compiled procedures |
U | IFG user profiles |
X | Data of any format |
The maximum record length of stored members is 32 Kbytes (including record header).
EDT processes text members with a maximum record length of 256 bytes.
Member type $... - reserved types
Types starting with $ are reserved.
Member type C - phases
A phase generated by the linkage editor TSOSLNK is normally stored in a file. LMS can be directed to write such a file as a C-type member to a library. Alternatively, the phases generated by the linkage editor can be stored directly in a library.
Member type D - documents
Type D members are intended for documents.
Member type F - IFG format masks
Members of this type are generated by IFG and stored in libraries.
Member type H - compiler result information
Members of this type are generated by the compilers and the assembler and stored in libraries.
Member type J - procedures and ENTER jobs
BS2000 procedures and ENTER jobs can be stored in this member type.
Member type L - link and load modules (LLM)
Both the linkage editor BINDER (see [5 (Related publications)]) and the compiler store the generated link and load modules (LLMs) in members of this type.
Member type M - macros
The assembler takes the macro members referenced in the program from the assigned library.
Member type P - list members
Edited data is referred to as a list member. The first character of the record must be a valid feed control character; this is checked on output to SYSLST.
Member type R - object modules
Object modules generated by the compilers or the assembler are normally stored in the temporary EAM area.
LMS can be directed to write such object modules as R-type members to the library. Alternatively, the object modules generated by the compilers or the assembler can be stored directly in a library.
These members serve as input to the linkage editors and the dynamic binder loader DBL.
Member type S - source programs
Source programs in libraries can be used as input to compilers and assembler for language processor runs.
Member type SYS... - reserved types
Types starting with SYS are reserved.
Member type SYSJ.. - compiled procedures
Compiled procedures are stored in this member type. Member types SYSJ and J are handled identically by LMS.
Member type U - IFG user profiles
Members of this type are generated by IFG and stored in libraries.
Member type X - data of any format
The type X member can accept any data. They are stored in text or PAM members, depending on the data format.
Textual member types - text members
Textual member types include the types S, M, J, P, D and X, as well as other types derived from them. Text members are members of these types, provided they contain no blockoriented records.
PAM members
In the following sections, members with block-oriented records are also referred to as PAM members (of type X or derivatives of type X) because as a rule they resulted from a file of type FILE-STRUCTURE=PAM being added as a member.