The member type indicates how the contents of the members are to be interpreted.
Standard types
Standard or predefined types are 1 character long, or start with $ or SYS
| Load modules |
| Text data |
| IFG format masks |
| Compiler result information |
| Procedures |
| Link and load modules (LLMs) |
| Macros |
| Data edited for printing |
| Object modules |
| Source programs |
| IFG user profiles |
| Data of any format |
| Compiled procedure |
| Reserved |
| Reserved |
The maximum record length of stored members is 32 Kbytes (including record header).
Member type C - phases
A phase generated by the linkage editor TSOSLNK is normally stored in a file. LMSCONV 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 - Text data
Any text may be written to D-type members. The same functions are possible as with S-type members.
Member type F - IFG format masks
Members of this type are created by IFG and stored in the libraries.
Members of this type are generated by the compilers and the assembler and stored in libraries.
Member type J - procedures
In this member type BS2000 procedures can be stored.
Member type L - link and load modules (LLM)
The BINDER (refer to the “BINDER” manual [12 (Related publications)]), and the compilers store the link and load modules (LLMs) created.
Member type M - Macros
The assembler takes the macro members addressed in the program from the assigned library.
Member type P - List members
Formatted data are referred to a list member. The first character of the record must be a valid line feed character; this is checked in the system file SYSLST.
Member type R - object modules
LMSCONV can store object modules created by compilers and the assembler and stored in a temporary EAM area in the library as members of type R. Optionally the object modules created by compilers and the assembler can also be stored directly in a library. The object modules and the dynamic link and load modules are used as inputs for these members.
Member type S - source programs
Source programs in libraries are used as inputs for the compilers and the assembler in compilation runs.
Member type U - IFG user profiles
Members of this type are created by IFG and stored in the libraries.
Member type X - data of any format
The member type X can accept any data.
Text-type member types - Text members
Types S, M, J, P, D, X are designated text-type member types. Text members are members of these types, provided that they do not contain and block-oriented records.
PAM members
Members with block-oriented records are referred to as PAM members below, since they are generally produced by adding a file as a member with FILE-
STRUCTURE=PAM.