Directory Limits Initialization Data Structure
This data structure is defined in the DASD.H header
file and is used with the NetDASDCtl API.
struct dasd_init_0 {
unsigned char i0_CtlFlag;
unsigned char i0_Drive;
};
where:
- i0_CtlFlag specifies the control function to
be performed on the 386-HPFS drive. Possible values for this control flag
are: ┌─────────────────────────┬───────┬────────────────────────────────────────────┐
│ SYMBOLIC CONSTANT │ VALUE │ MEANING │
├─────────────────────────┼───────┼────────────────────────────────────────────┤
│ DASD_CTL_INSTALL │ 1 │ Enables directory limits support on the
│
│ │ │ specified drive. │
├─────────────────────────┼───────┼────────────────────────────────────────────┤
│ DASD_CTL_REMOVE │ 2 │ Disables directory limits support on the │
│ │ │ specified drive. │
├─────────────────────────┼───────┼────────────────────────────────────────────┤
│ DASD_CTL_RECALC │ 3 │ Recalculates the space used in all of the
│
│ │ │ specified drive directories that have │
│ │ │ directory limits placed upon them. │
└─────────────────────────┴───────┴────────────────────────────────────────────┘
- i0_Drive specifies the letter of the drive
upon which the DASD control function is to operate. This drive must reside
on the server specified by the pszServername parameter for any API
using this data structure.
[Back: Directory Limits Information Data Structure]
[Next: 386-HPFS Information Data Structure]