Dataset Allocation

The Dataset Allocation screen (see the following figure) displays when you select option 2 from the User Parms menu. It enables you to enter information for the work file data set allocated to store Special Register Values, and for the temporary work file used to store SQL source.

Dataset Allocation screen

Specify Work File Dataset Info Area

High Level Qualifier

Optional. The High Level Qualifier (HLQ) applies to the following File-AID for Db2 work files:

• 
  
  • userid.FADB2.USERDATA
  • userid.FADB2.USERDATA
  • userid.FADB2.X.Dyymmdd.Thhmmss
  • userid.FADB2.X.Dyymmdd.Thhmmss.O

userid.FADB2.USERDATA stores the Special Register Values (see Special-Register-Values). This work file is automatically created.

userid.FADB2.USERDATA temporarily stores the SQL source whenever T (Temporary) Selection Criteria usage is specified (see for example, Selection Criteria Usage). This work file is automatically created. It will be deleted when exiting the session using the SQL temporary selection criteria.

userid.FADB2.X.Dyymmdd.Thhmmss is the XLOB work file when browsing or editing a LOB column with the XLOB command (see XLOB and XLOB Audit Trail Datasets). This work file is automatically created and the work file is deleted, unless your File-AID for Db2 edit session updated the LOB data and has the Audit Trail feature (Create Audit Trail) turned on.

userid.FADB2.X.Dyymmdd.Thhmmss.O is the before (Old) image of the XLOB work file when editing a LOB column with the XLOB command and “Create Audit Trail” is enabled (see XLOB and XLOB Audit Trail Datasets.) This work file is automatically created.

The high level qualifier (hlq) you specify here is used as the first qualifier of the work file data set name, the userid is used as the second qualifier (e.g. hlq.userid.FADB2.USERDATA. If a value was specified for the work file high level qualifier TEMPORARY_WORKFILE_HIGH_LEVEL_QUALIFIER at install time (for more information, see TEMPORARY_WORKFILE_HIGH_LEVEL_QUALIFIER in the File-AID for Db2 product configuration), that value will be prefilled here, but may be changed. The entered value is retained across sessions. If you do not specify an hlq, only the userid is used.