DDM-related CL command considerations

 

This topic collection describes DDM-related specifics about iSeries™ CL commands when they are used with DDM files. These topics discuss running the commands on the source server and do not discuss them being submitted to run on the target server by the Submit Remote Command (SBMRMTCMD) command.

You see message CPF9810 if the following items are true about a DDM file:

• The file is created into library QTEMP.

• The file is used by a CL command (such as CPYF).

• A remote file and library was specified in the CL command and the library does not exist on the remote server.

Message CPF9810 indicates that the QTEMP library was not found. However, the library that was not found is the remote library that was specified in the DDM file.

• File management handling of DDM files
  Because of the way data management handles DDM files, be careful when specifying a member name on commands. If a member name is specified, data management first searches for a local database file containing the member specified before looking for a DDM file.

• ALCOBJ (Allocate Object) command
  When the name of a DDM file is specified on the Allocate Object (ALCOBJ) command on the source server, the command allocates the DDM file on the source server and its associated file or file member on a target server.

• CHGJOB (Change Job) command
  The Change Job (CHGJOB) command can be used to change the DDMCNV parameter, which controls whether Advanced Program-to-Program Communication (APPC) or iSeries Access Family conversations allocated for DDM use are to be kept active or automatically dropped when they are not in use by a job. The new value goes into effect immediately for the specified job.

• CHGLF (Change Logical File) command
  The Change Logical File (CHGLF) command can be used to change files on the source and target servers through the SYSTEM parameter.

• CHGPF (Change Physical File) command
  The Change Physical File (CHGPF) command can be used to change files on the source and target systems through the SYSTEM parameter.

• CHGSRCPF (Change Source Physical File) command
  The Change Source Physical File (CHGSRCPF) command can be used to change files on the source and target servers through the SYSTEM parameter.

• CLRPFM (Clear Physical File Member) command
  The Clear Physical File Member (CLRPFM) command can be used with DDM to clear all the records either from a physical file member on a target iSeries server or from a file on a non-iSeries target server. The command works the same way as it does for local files (clearing all data records and deleted records).

• Copy commands with DDM
  This topic describes the DDM implications of these CL commands.

• CRTDTAARA (Create Data Area) command
  The Create Data Area (CRTDTAARA) command creates a data area and stores it in a specified library. It also specifies the attributes of the data. The data area can be optionally initialized to a specific value.

• CRTDTAQ (Create Data Queue) command
  The Create Data Queue (CRTDTAQ) command creates a data queue and stores it in a specified library. Data queues are used to communicate and store data used by several programs either within a job or between jobs. Multiple jobs can send or receive data from a single queue.

• CRTLF (Create Logical File) command
  The Create Logical File (CRTLF) command can be used to create files on the source and target servers through the SYSTEM parameter.

• CRTPF (Create Physical File) command
  The Create Physical File (CRTPF) command can be used to create files on the source and target servers through the SYSTEM parameter.

• CRTSRCPF (Create Source Physical File) command
  The Create Source Physical File (CRTSRCPF) command can be used to create files on the iSeries source and target servers through the SYSTEM parameter.

• DLCOBJ (Deallocate Object) command
  When the name of a DDM file is specified on the Deallocate Object (DLCOBJ) command on the source server, the command deallocates the DDM file on the source server and its associated file or file member on a target server.

• DLTF (Delete File) command
  The Delete File (DLTF) command can be used to delete files on the source and target servers.

• DSPFD (Display File Description) command
  The Display File Description (DSPFD) command can be used to display (on the source server) the attributes of the DDM file on the source server, the remote file on the target server, or both the DDM file and the remote file. As with local files, the attributes of multiple DDM files, multiple remote files, or both can be displayed by the same command.

• DSPFFD (Display File Field Description) command
  The Display File Field Description (DSPFFD) command can be used to display the file, record format, and field attributes of a remote file. To display the remote file attributes, however, enter the name of the DDM file associated with the remote file, not the name of the remote file.

• OPNQRYF (Open Query File) command
  You can query remote files using the Open Query File (OPNQRYF) command, but only if the remote files are on a target iSeries server or a target System/38™.

• 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.

• RCLRSC (Reclaim Resources) command
  The Reclaim Resources (RCLRSC) command, like the Reclaim DDM Conversations (RCLDDMCNV) command, can be used to reclaim all DDM conversations that currently have no users in the job.

• RNMOBJ (Rename Object) command
  The Rename Object (RNMOBJ) command can be used to rename a remote file.

• WRKJOB (Work with Job) command
  The Work with Job (WRKJOB) command can be used to display two DDM-related items.

• WRKOBJLCK (Work with Object Lock) command
  The Work with Object Lock (WRKOBJLCK) command can be used to display the object lock requests (held locks and pending locks) for DDM files. This command displays only the locks held for the local DDM files, not locks held for the associated remote files.

 

Parent topic:

Use CL and DDS with DDM

 

Related concepts

Control language

 

Related reference

DDM-related CL command lists