OVRDBF (Override with Database File) command

 

The Override with Database File (OVRDBF) command can be used with DDM to override (replace) a local database file named in the program with a DDM file; the DDM file causes the associated remote file to be used by the program instead of the local database file.

If a DDM file is specified on the TOFILE parameter and if other parameters are specified that change a file's attributes, the result is that the remote file actually used by the program is used with its attributes changed by the parameter values specified on the OVRDBF command.

If the target server is an iSeries™ server or a System/38™, existing programs that use the OVRDBF command to access remote files work the same as when they access local files. All the OVRDBF parameters are processed the same on source and target iSeries servers.

If end-of-file delay (EOFDLY) is used, it is recommended to end a job with an end-of-file record because if the source job gets canceled, the target job does not get notified. The user must also end the target job.

If the target server is neither an iSeries server nor a System/38:

• The following parameters are still valid: TOFILE, POSITION, RCDFMTLCK, WAITFILE, WAITRCD, LVLCHK, EXPCHK, INHWRT, SECURE, SHARE, and SEQONLY.

  • The TOFILE parameter is always processed on the source server. When a DDM file name is specified on this parameter, the program uses the associated remote file instead of the local database file specified in the program.

  • The RCDFMTLCK parameter, if specified, is valid only if both of the following are true of the remote file used: only one type of lock condition can be requested for the remote file, and the record format name in the remote file must be the same as the name of the DDM file.

  • The WAITFILE and WAITRCD parameters have no effect on remote file processing.

• The MBR parameter causes an error if it is specified with a member name that is different than the name of the file containing the member.

• The FRCRATIO and NBRRCDS parameters, if specified, are ignored.

• The FMTSLR parameter, if specified, causes an error when the file being opened is a DDM file.

• The SEQONLY parameter causes records to be blocked on the source side. Records might be lost if the source job is canceled before a block is full.

 

Parent topic:

DDM-related CL command considerations

 

Related reference

Additional considerations: SBMRMTCMD command
Example: Access DDM remote members (iSeries server only)