IBM s/390 manual Disk layout AD system, Partition Mount Size Use, Device Volser Addr Use

The difficulty is that, if a file on the second hard disk (such as an emulated S/390 volume) is specified in a FLEX-ES resources definition, then that file must be available before resadm can be started. Linux mounting (through /etc/fstab) forgives missing file systems, but resadm does not. We handled the situation this way:

￿We defined a complete IPLable system on the primary hard disk drive. (For the OS/390 R10 AD system, this required four 3390-3 drives.)

￿We defined a FLEX-ES system and resource definition that referenced only these drives. These are the definitions (S10A and R10A) that we have described earlier. If only one hard disk drive is installed, we can start FLEX-ES using these definitions.

￿We placed optional OS/390 volumes (DLIBs, work volumes, and so forth) on the second hard disk drive.

￿We created another set of FLEX-ES definitions (S10B and R10B) that specified the additional S/390 volumes on the second hard disk drive. We created a second shell script (shosb) that uses this system name. If both hard disks are installed, we start FLEX-ES with these definitions.

There is a slight inconvenience in this method. We need to keep the common parts of both definitions synchronized, and this sometimes means double editing is required when changes are made. Both sets of definitions and the associated shell scripts are listed in Appendix A, “FLEX-ES definition listings” on page 69.

The remaining general discussion in this section assumes that both disk drives are mounted.

5.5.3 Disk layout (AD system)

Since we had two hard disks for our ThinkPad/EFS system, we decided to split the S/390 volumes between them. This might produce a small benefit in overlapped disk operation. We decided to place an IPLable system on the primary drive and optional volumes on the second drive. There was no special reason for this plan, but it seemed reasonable. We had ample space and could install many more 3390 volumes, if needed. We could have, for example, installed two AD releases as well as several user volumes.

We used the following layout for our OS/390 AD R10 system:

hda	Primary hard disk drive
	partition	mount	size		Use
	hda1	/boot	36	MB	Linux boot partition
	hda5	/	3 GB		Linux root, containing all of	Linux, FLEX-ES
	hda6	swap	150 MB		Linux swap
	hda7	/s390	26	GB	File system for S/390 volumes
hdc	Second hard disk drive
	hdc1	/holding	2 GB		Target area for tar/compress,	and other uses
	hdc2	/s391	27	GB	File system for S/390 volumes

We placed our S/390 volumes (for the OS/390 AD R10 system) as follows:

/S390 (on Primary hard disk)

Device	Volser	Addr	Use
3390-3	OS39RA	A80	IPL volume
3390-3	OS3RAA	A81	More OS/390 libraries
3390-3	OS39M1	A82	Parmlibs, spool, paging, VSAM, etc
3390-3	OS39HA	A87	HFS data sets

(14 GB still available)

/S391 (on Second hard disk) 3390-3 OS39DA A85 DLIBs 3390-3 OS3DAA A86 DLIBs 3390-2 OS3DAB A88 DLIBs

44S/390 PID: ThinkPad Enabled for S/390