You can use this option to install a new POSIX subsystem.
The root and var file systems are installed as specified, directories are installed in the POSIX file system and the POSIX subsystem is started with the root file system just created.
Definition of BS2000 Container File
BS2000 filename: $SYSROOT.FS.ROOT
BS2000 filesize: 150000 PAM-Pages
POSIX filesystem? (y/n): Y
================================================================================
Definition of POSIX filesystem
Size of filesystem: PAM-Pages Journaling? (y/n): N
POSIX mountpoint: /
Automount? (y/n): Y Mountoptions:
Overwrite existing filesystem? (y/n): POSIX filesystem marker (y/n): Y
================================================================================
Save definitions: ENTER
Help : F1 terminate: F2
Indicate name of BS2000 container for the root filesystem
Figure 24: Follow-uo mask for “Install POSIX subsystem”
Definition of BS2000 container file:
BS2000 filename
Name of the PAM file to be used as a container file for the root or var file system.
The file name must contain the user ID SYSROOT. If the file does not yet exist, it is created with the specified size.
BS2000 filesize
Size of the container file in PAM pages (unit: 2Kb). The minimum size is 4096 PAM pages.The desired size must be entered for newly created container files.
If the container already exists, the actual size is incorporated into the field. You cannot modify the value in this case.
POSIX filesystem? (y/n)
Answer the query with y (yes) or n (no). The container file should normally contain a POSIX file system. However, you can bypass access via the POSIX file system in special cases and access the file directly (raw access).
The fields for the root and var file systems default to y (yes).
Definition of the POSIX file system
Size of filesystem
If a file system already exists in the BS2000 container file, its size is shown here in PAM pages (2 Kb). If no file system exists as yet, the field contains the size of the BS2000 container file.
You cannot overwrite the value in this field, because the size of a file system in a BS2000 container file is always the same as that of the BS2000 container file.
Journaling? (y/n)
In this field you can define whether the file system is to be defined with (y) or without (n) a journal. If you make no specification, the default value is = n.
The function "Journaling" is no longer supported, i.e. the parameter is ignored.
POSIX mountpoint
Directory in which the POSIX file system is to be mounted.
You must enter the absolute name of the directory and the name must begin with a slash (/). If the directory does not yet exist, the program creates it.
The fields for the root and var file systems default to /.
Automount? (y/n)
If the file system is to be mounted immediately and automatically for every subsystem start, you must enter y (yes). If you are only setting up the file system but do not yet wish to use it, you must enter n (no).
The fields for the root and var file systems default to y (yes).
Mountoptions
You can parameterize the mounting of the file system. You will find the appropriate options for the mount command in the "POSIX Commands" [1] manual. Multiple options must be separated by commas.
Overwrite existing filesystem? (y/n)
Answer the query with y (yes) or n (no).
This field is only activated if the container file already contains a POSIX file system. You must decide whether the file system is to be transferred unaltered or whether a new file system is to be created. When the root or var file system is created, this field is not activated, as these file systems are always overwritten.
POSIX filesystem marker (y/n)
Meaning: file system created in POSIX/BS2000.
The fields for the root and var file systems default to y (yes).
If the marker is not set, the file system is considered to be an ASCII file system under POSIX. This means that an ASCII-EBCDIC conversion takes place, depending on the IO_CONVERSION environment variable (see “Copying and converting files”).