The BST05UPF utility will not normally be used as part of data center routine, therefore we recommend that you only run BST05UPF after consultation with Beta Systems support. BST05UPF is used to update file information in an existing database definition file. For example, you may want to run this program when:
Use command DEFINE UPDATE to specify the file information under DD BQLIN.
Whenever you run this program, please check the logs, even if the job ends with RC=0. Under certain circumstances, RC=0 may indicate that the definition database has not been found, and that the update process has not started for this reason.
Program BST05UPF only updates the information in the database definition file. Additional actions are required to change the corresponding physical dataset.
You must stop the started task before updating file information in the database definition file (DEFINE UPDATE FILE ...).
DEFINE UPDATE FILE -
filename | OLDDSN(dsname) -
[ DSNAME(dsname) ] -
[ MIRROR(NO) -
[ SPACE(cyl[,cyl]) ] -
[ VOLUME(volume|SMS) ] -
[ HWM(n) ] -
[ MAXSIZE(cyl) ] -
[ BUFFER(n) ] -
[ STORAGECLASS(name) ] -
[ MANAGEMENTCLASS(name) ] -
[ DATACLASS(name) ]
|
DEFINE UPDATE FILE |
Introduces the update command Use either filename or OLDDSN (dataset name) to specify which file to update. All other parameters are optional. |
|
filename |
filename is the short name (logical name) of the database component Note on spool files: When updating spool files, you must enter the name of the file that was generated using command DEFINE INSERT FILE. For example, if the number 20 was generated automatically, the file name will be SP000020. |
|
OLDDSN(dsname) |
dsname is the existing dataset name Note on SYSVAR support: If you code a dataset name instead of a short name, you must use exactly the same notation as in the database definition file. If the dataset name contains a static system symbol, you must specify the name of this symbol (&sysvar.). |
|
DSNAME(dsname) |
dsname is the new dataset name (for example, when renaming a database component) |
|
MIRROR(NO) |
Enter NO after the keyword if you do not want to create mirror databases. |
|
SPACE(cyl) |
Size of the VSAM dataset in cylinders; specify primary and secondary space when using dynamic databases: SPACE(cyl,cyl) |
|
VOLUME(volume | SMS) |
Volume to be used for the VSAM dataset. When SMS managed files are used, SMS must be entered rather than the volume name. |
|
HWM(nn) |
High water mark in percentage points (0..99) |
|
MAXSIZE(cyl) |
User-defined warning threshold value for file size (in cylinders); enables users to monitor database growth following automatic database extension (online under option D.1 or via the messages xxx9549I and xxx9549W) |
|
BUFFER(n) |
For database components of type DATA or KEY: Number of buffers, in 4K blocks, to be used by the BQL speedmaster function If A2G_SUPPORT=NO, the maximum value is limited to 30000. |
|
STORAGECLASS(name) |
Name of the storage class (when using SMS managed files) |
|
MANAGEMENTCLASS |
Name of the management class (when using SMS managed files) |
|
DATACLASS(name) |
Name of the data class (when using SMS managed files) |