gtps4m33System Generation

ONLFIL

The ONLFIL macro is used to specify the characteristics of the DASD devices that will be online and under direct control of the system. ONLFIL macro is required. Before coding this macro it is recommended that the user refer to TPF Concepts and Structures.

Up to four DASD devices may be coded using parameters DEVICEA= through DEVICED=. The parameter DEVICEA= must be coded for a DASD device. Any further DASD devices must use the next alphabetic parameter. For example, if you have two DASD devices then you must code parameters DEVICEA= and DEVICEB=. Combinations such as DEVICEA= and DEVICEC= or DEVICEB=, DEVICEC=, and DEVICED= are not allowed.

Format




Notes:

  1. The following parameters are only used by SIP Stage I processing

  2. The following parameters are required for online DASD devices A, B, C, and D (DEVA, DEVB, DEVC, DEVD). Substitute 'A', 'B', 'C', or 'D' for 'x' in the keyword parameters. All the following parameters are used by the offline FACE table generator as well as by SIP Stage I processing.

VSNCHAR=cc
Specifies the first two characters of the six-character volume serial numbers (see the VOLNOx parameter for the description of how the last four characters are coded). These two characters must be alphabetic and they will be used in the VSNs of all online modules, as well as the copy module and the loader general file. While the first two characters of a subsystem's VSN must be identical for all the DASD allocated to it, the first two characters must be unique across subsystems.

IPLABLE=n
Defines the number of primary and duplicate pairs of DEVA modules that are capable of being IPLed. n is an integer between 1 and 255 but not greater than the highest device A primary module.

The following convention is used in describing the remaining DASD parameters: the character identifying the DASD device (A, B, C, or D) is represented in the parameter names by a lowercase 'x'. For example, DEVICEx becomes DEVICEA for device A, DEVICEB for device B, and so on.

Devices must be coded in "sequential series." In other words, if you are coding parameters for only one device, you must specify this device as device 'A'. If you are coding two devices, you must specify devices 'A' and 'B'. Three devices must be A, B, and C, and four devices must be A, B, C, and D. (For example, if you have three devices, you cannot code them as devices A, C, and D.)

You can code the following parameters in any order, as long as you code all the required parameters (those without defaults) for each device. The parameters with defaults are ENTRx, DUPTYPx, and NAMDEVx.

DEVICEx=type[,# of cylinders]
Specifies one of the supported DASD device types as follows:
                                  Default #
Device Type                       Cylinders
 
3350 - 3350 Model 2 or Model 2F       555
3375 - 3375 Model 1 or Model 1F       959
3380 - 3380 all models                885
3390 - 3390 all models               1113
9345 - 9345                          1440

The number of cylinders indicates the maximum number of cylinders to be used by the specified device type. See Table 7 for more information.

Notes:

  1. 3390 devices are set at installation time to either native 3390 mode or 3380 emulation mode. A 3390 running in 3380 emulation mode must be coded as DEVICEx=3380 for both types of emulation. TPF supports 2 types of 3380 emulation.
    1. Track compatibility emulation, which is supported on 3990 control units that are not using CFLF. For sample JCL to set or change the mode of a 3390, see the description of the ICKDSF INSTALL command (SETMODE option) in the DSF User's Guide and Reference.
    2. Record format emulation, which is used with CFLF. 3380 emulation in this case is set by using Licensed Internal Code (LIC) that runs directly on the 3990.

  2. The volume table of contents (VTOC) dataset will be placed at one of the following locations:
    • The last track of the cylinder that was indicated.
    • The location that was specified by coding the RAMFIL macro statement with the VTOC parameter specified.
    • Cylinder 4369, head 0. This is the default location if the RAMFIL macro statement with the VTOC parameter specified is not coded and the number of cylinders is more than 4369.

PERMx=n
Specifies the number of device x online modules for fixed and pool records on both prime and dup mods.
Note:
The total number of online plus general file devices cannot exceed 3999 (or 999 if the system is in migration mode).

VOLNOx=nnnn
Specifies the numeric portion of the six-character starting volume serial number for DEVICEx. The parameter accepts a 1-to-4 digit decimal number (or a 1-to-3 digit decimal number if OLDVSN was coded).

Notes:

  1. The numeric characters cannot be all zeros, as VSN zero has been reserved for the copy module. Also the numeric portions of VSN range should not overlap the range of another device type, or the loader general file. SIP will assign sequential numbers starting with the specified number for the device type.

  2. The VSNs for the rest of a device type's DASD are calculated by adding one to the starting number for each DASD allocated. The last VSN created will be:
    VOLNOx + PERMx + EXTRx - 1
    

EXTRx=0|n
Specifies the number of extra device x file status table slots to be reserved for future expansion.

DUPTYPx
Specifies the duplication status for device x online modules.

N
Nonduplicated.

S
Selectively duplicated.

F
Fully duplicated.

NAMDEVx=name
This parameter is used to assign a symbolic four-character name to a DASD device type. This name is used as a device type identification in the DASD pool program messages. Each DASD device type must have a unique identification.

For example, if the user's system is to contain 3380 type DASDs as both device 'A' and device 'B' (e.g., pools formatted differently) then this parameter would have to assign unique names for device 'A' and 'B', such as NAMDEVA=DEVA and NAMDEVB=DEVB.

The default is whatever was coded for the DEVICEx parameter.

SPARVSNx=cccc
Specifies the first four alphameric characters of the volume serial numbers assigned to spare volumes to be used for copying from the online modules in the event of a DASD failure. VSNs starting with this character string will be ignored during disk roll call.

For example, specifying this parameter as 'SPAR' will allow you to attach any number of devices with the VSN 'SPAR00' without disrupting the IPL with unwanted duplicate VSN error messages. Since each logical device type of each MDBF subsystem may be formatted with its own unique record allocation, a different spare VSN may be coded for each device type of each MDBF subsystem. This will allow operations to more easily identify the appropriate spare to use for a given device, when multiple disk formats are used.

Examples

The following example specifies four DASD devices. Two 3390s are to be assigned as device A permanent modules and two 3380s are to be assigned as device B permanent modules. Both device A and B are to have four extra file status table slots reserved. Both device A and B are to be selectively duped. Device A has a starting VSN of SP0003 and device B has a starting VSN of SP2010. Device A is to be identified as DEVA and device B is identified as 3380 by the DASD pool program messages.

ONLFIL VSNCHAR=SP,                                        X
       DEVICEA=(3390,1440),PERMA=2,EXTRA=4,               X
       VOLNOA=3,DUPTYPA=S,                                X
       NAMDEVA=DEVA                                       X
       SPARVSNA=SPRA,                                     X
       DEVICEB=(3380,885),PERMB=2,EXTRB=4,                X
       VOLNOB=2010,DUPTYPB=S,                             X
       SPARVSNB=SPRB

References

None.