Create Physical Optical File (CRTPOFRDAR)

The Create Physical Optical File (CRTPOFRDAR) command creates a physical optical file. The description for this physical optical file comes from the model file

Parameters

Keyword	Description	Choices	Notes
FILE	Physical optical file	Qualified object name	Required, Positional 1
	Qualifier 1: Physical optical file	Name
	Qualifier 2: Library	Name, *CURLIB
STGGRP	Storage group	Name	Optional
COMPRESS	Compression	YES, NO	Optional
PRPAUT	Propagate authority	YES, NO	Optional
MEDIA	Media type	OPTICAL, DISK	Optional

Top

Physical optical file (FILE)

Specifies the name of the physical optical file to create.

Qualifier 1: Physical optical file

name: Specify the name of the physical optical file to be created.

This is a required parameter.

Qualifier 2: Library

*CURLIB: The current library for the job is used to locate the physical optical file. If no library is specified as the current library for the job, QGPL is used.
name: Specify the name of the library where the physical optical file is located.

Storage group (STGGRP)

Specify the name of the optical storage group to use to find the optical volumes on which to place the physical file.

Note: If you press the F4 key for this parameter while prompting the command, a list of all the valid entries is presented to you.

name: Specify the name of the storage group to use.

Compression (COMPRESS)

Specify if you want to compress your data before writing it to the optical media.

*YES: The data is compressed before it is written.
*NO: No compression is used. The data is written just as it is passed on the write API.
Note: This may be a good choice when working with a file that has a small record length. Depending on the data, compression can actually result in a record that is larger than the original uncompressed record. During testing, you can use the DSPOFDRDAR command to find the maximum record length for the file to help you determine if compression is of benefit.

Propagate authority (PRPAUT)

Specifies whether the authority from the model file should be propagated to the newly created physical optical file.

*YES: The authority associated with the model file is propagated to the physical optical file.
*NO: No authority is propagated to the physical optical file. Public authority is *EXCLUDE and the object is owned by the user profile or the group profile that issued this command.

Media type (MEDIA)

Specifies on which type of media this file should be placed.

*OPTICAL: The file should be placed on optical media.
*DISK: The file should be placed on disk media.
Note: You will probably want to use this option while you are developing and testing your application. The OnDemand Record Archive APIs have the same parameters regardless of the media type specified here.