|
In this section: |
The APP commands in this section provide management options for applications and their component files.
|
How to: |
In general, the APP CREATE command creates an application under the approot location. The exception is a PDS deployment on a Unified Server, where an application is a physical entity and each of its component file types is stored in a separate PDS.
The APP CREATE command can create any number of applications with one command.
APP CREATE app1[/app1a...] [app2[/app2a...] ... [appn[/appna...] ] [DROP]
where:
Are application names under approot. The application name can be up to 64 characters.
Are nested application directories, allowed when nested applications are configured. In order to create a nested application, the parent application must already exist.
Deletes an application if one already exists with the same name as the one to be created, and then creates a new application with that name. Note that any files in the pre-existing application are deleted. Without the DROP option, a message will be generated, and the pre-existing application will not be deleted or changed.
The application name may not contain spaces. If the name contains spaces, each section is understood to be a separate application. If you require a name with spaces, you must create it using another mechanism, such as the Windows Explorer. You can then use the APP MAP command to add it to APPROOT.
If you need to specify more application names than can fit on one line, add the continuation character (-) at the end of the first line, and code more application names on the next line.
The word HOLD cannot be used as an application name.
If you are working on a Unified Server in PDS deployment, you can change the default characteristics of individual component file types by issuing a DYNAM SET APP command. This command controls the types of component files that are generated for the application when an APP CREATE command is issued. By default, all component file types are generated.
The syntax is
DYNAM SET APP FOR filetype [SKIP|CREATE] [POSTFIX aaa.bbb] [parms]
where:
Are the component types that may be affected by this command, in uppercase: FOCEXEC, MASTER, ACCESS, HTML, GIF, FOCSTYLE, MAINTAIN, ETG. You must issue a separate command for each component type you wish to affect.
Indicates that the designated file type should not be created when the APP CREATE command is issued.
Creates the designated file type when the APP CREATE command is issued. This is the default setting.
Specifies the lower level qualifier of the DSN (data set name) for the component type. The APPROOT value is used to complete the full DSN, which is expressed as
approotvalue.appname.component_type
The default value for component_type is filetype.DATA.
Are the allocation parameters you can set. The default parameter values are:
|
File Type |
Parameter |
|---|---|
|
FOCEXEC |
RECFM VB TRKS LRECL 4096 BLKSIZE 27998 SPACE 50 50 DIR 50 |
|
MASTER |
RECFM FB TRKS LRECL 80 BLKSIZE 22000 SPACE 50 50 DIR 50 |
|
ACCESS |
RECFM FB TRKS LRECL 80 BLKSIZE 22000 SPACE 50 50 DIR 50 |
|
HTML |
RECFM VB TRKS LRECL 4096 BLKSIZE 27998 SPACE 50 50 DIR 50 |
|
GIF |
RECFM VB TRKS LRECL 4096 BLKSIZE 27998 SPACE 50 50 DIR 50 The GIF file type creates libraries for GIF and JPG files. |
|
FOCSTYLE |
RECFM FB TRKS LRECL 1024 BLKSIZE 27648 SPACE 50 50 DIR 50 |
|
MAINTAIN |
RECFM VB TRKS LRECL 4096 BLKSIZE 27998 SPACE 50 50 DIR 50 |
|
ETG |
RECFM FB TRKS LRECL 80 BLKSIZE 22000 SPACE 50 50 DIR 50 |
The following command indicates that GIF files should not be created when the APP CREATE command is issued.
DYNAM SET APP FOR GIF SKIP
The following command indicates that Procedures (FOCEXECs) should be created when APP CREATE is issued.
DYNAM SET APP FOR FOCEXEC TRKS SP 10 20 DIR 30
|
How to: |
The APP COPY command copies the entire contents of one application to another. The target application must already exist.
APP COPY app1[/app1a...] app2[/app2a...]
where:
Is the application being copied. It can be a nested application name.
Is the application to which the contents of the first application are being copied. It can be a nested application name.
|
How to: |
The APP COPYF[ILE] command copies one or more components or component types from one application to another.
Note that if you copy a component manually, you can, optionally, rename it in the process.
If you copy a Master File, the corresponding Access File is also copied. However, copying an Access File (file type FOCSQL) does not automatically copy the corresponding Master File.
APP COPYF[ILE] app1[/app1a...]
{filename1|*} filetype1 app2 [/app2a...]
{filename2|*} {filetype2|*} [IFEXIST] DROPwhere:
Is the application that contains the component to be copied. It can be a nested application name.
Are the components to be copied. Use an asterisk (*) to copy all components of file type filetype1.
You can use the following wildcard characters in the file name and file type references.
Note that an asterisk can also be used to replace the entire filename or filetype parameter.
Is the file type, in uppercase, of the component to be copied.
Is the application to which the named component is being copied. It can be a nested application name.
Is the component name in the target application, after the copy process. Use an asterisk (*) to propagate the file names from the source application to the target application.
Is the component type, in uppercase, in the target application after the copy process. Use an asterisk (*) to propagate the file types from the source application to the target application.
Ignores any component in the source application that does not exist.
Overwrites any component already in the target application with the same name and file type as a component being copied.
For a full list of the types of files you can copy with APP commands, see Application and File Management Commands.
|
How to: |
The APP MOVE command moves the entire contents of one application to another. The target application must already exist.
APP MOVE app1[/app1a...] app2[/app2a...]
where:
Is the application being moved. It can be a nested application name.
Is the application to which the contents of the first application are being moved. It can be a nested application name.
|
How to: |
The APP MOVEF[ILE] command moves one or more components or component types from one application to another.
Note that if you move a component manually, you can, optionally, rename it in the process.
If you move a Master File, the corresponding Access File is also moved. However, moving an Access File (file type FOCSQL) does not automatically move the corresponding Master File.
APP MOVEF[ILE] app1[/app1a...]
{filename1|*} filetype1 app2 [/app2a...]
{filename2|*} {filetype2|*} [IFEXIST] [DROP]where:
Is the application that contains the component to be moved. It can be a nested application name.
Is the name of the component to be moved. Use an asterisk (*) to move all components of file type filetype1.
You can use the following wildcard characters in the file name and file type references.
Note that an asterisk can also be used to replace the entire filename or filetype parameter.
Is the file type, in uppercase, of the component to be moved.
Is the application to which the named component is being moved. It can be a nested application name.
Is the component name in the target application, after the move process. Use an asterisk (*) to propagate the file names from the source application to the target application.
Is the component type, in uppercase, in the target application after the move process. Use an asterisk (*) to propagate the file types from the source application to the target application.
Ignores any component in the source application that does not exist.
Overwrites any component already in the target application with the same name and file type as a component being moved.
For a full list of the types of files you can move with APP commands, see Application and File Management Commands.
|
How to: |
The APP DELETE command deletes applications under approot.
APP DELETE app1[/app1a...] [app2[/app2a...] ... [appn[/appna...]]
where:
Are application names. Nested application names are supported. If you need to specify more application names than can fit on one line, add the continuation character (-) at the end of the first line, and enter additional application names on the next line.
|
How to: |
The APP DELETEF[ILE] command deletes one or more components or component types from an application.
If you delete a Master File, the corresponding Access File is also deleted. However, deleting an Access File (file type FOCSQL) does not automatically delete the corresponding Master File.
APP DELETEF[ILE] app[/appna...] {filename|*} filetypewhere:
Is the application from which the component or component type is being deleted. Nested application names are supported.
Is the name of the component to be deleted. Use an asterisk (*) to delete all files of type filetype.
You can use the following wildcard characters in the file name and file type references.
Note that an asterisk can also be used to replace the entire filename or filetype parameter.
Is the component type, in uppercase, of the component to be deleted.
For a full list of the types of files you can use with APP commands, see Application and File Management Commands.
|
How to: |
The APP PROPERTY appname CODEPAGE command identifies the codepage to be used for non-data files in the application directory.
APP PROPERTY app[/appa...] CODEPAGE number
where:
Is an application name. Nested application names are supported.
Is the code page number for non-data files in the application.
|
How to: |
The APP RENAME command renames an existing application.
Note: You cannot rename an application if it is active in the search path.
APP RENAME app1[/app1a...] app2[/app2a...]
where:
Is the application name to be renamed. It can be a nested application name.
Is the new application name of up to 64 characters. It can be a nested application name.
The following shows app1 being renamed to app2.
APP RENAME app1 app2
|
How to: |
The APP RENAMEF[ILE] command renames one or more components in an application.
If you rename a Master File, the corresponding Access File is also renamed. However, renaming an Access File (file type FOCSQL) does not automatically rename the corresponding Master File.
APP RENAMEF[ILE] app[/appa... ] filename1 filename2 filetype [DROP]
where:
Is the name of the application that contains the component being renamed. It can be a nested application name
Is the file name of the component to be renamed.
You can use the following wildcard characters in the file name and file type references.
Note that an asterisk can also be used to replace the entire filename or filetype parameter.
Is the new name for the component. The component name may be up to 64 characters.
Is the file type, in uppercase, of the component to be renamed.
Overwrites an existing component with the same file name and file type.
For a full list of the types of files you can use with APP commands, see Application and File Management Commands.
The APP COPYF, APP MOVEF, APP DELETEF, and APP RENAMEF commands enable you to perform their actions on a wide variety of file types.
The following is a comprehensive list of the file types you can use with APP commands and the file extensions associated with the on-disk names for hierarchical file systems.
Note that the file types must be coded in uppercase in any APP command that requires it.
Note: This list reflects file types supported across all products and release levels. Particular file types may not be supported in particular releases or with every product.
|
File Type |
File Extension |
|---|---|
|
ACX |
.acx |
|
ADR |
.adr |
|
AFM |
.afm |
|
BMP |
.bmp |
|
BST |
.bst |
|
cascading style sheet |
.css |
|
CONTROL |
.ctl |
|
DATA |
.dat |
|
DDS |
.DDS |
|
DEFAULT |
The APP filename value is used to derive the physical extension for the APP command, so that unknown user-defined extensions may be supported in an APP command (for example, APP COPYFILE BASEAPP MYFILE.FOO DEFAULT BASEAPP MYFILE FOCEXEC). |
|
DTD |
.dtd |
|
EDANLS |
.nls |
|
EDAPRFU |
.prf |
|
EDAPROF |
.prf |
|
EDAPSB |
.psb |
|
EPS |
.eps |
|
ERRORS |
.err |
|
ETG |
.etg |
|
ETL |
.etl |
|
EXCEL |
.xls |
|
FMU |
.fmu |
|
FOCCOMP |
.fcm |
|
FOCDEF |
.def |
|
FOCEXEC OR FEX |
.fex |
|
FOCFTMAP |
.fmp |
|
FOCPSB |
.psb |
|
FOCSQL |
.acx |
|
FOCSTYLE |
.sty |
|
FOCTEMP |
.ftm |
|
FOCUS |
.foc |
|
GIF |
.gif |
|
HLI |
.hli |
|
HTML |
.htm |
|
IBICPG |
.sl |
|
JPG |
.jpg |
|
JS |
.js |
|
LSN |
.lsn |
|
MAINTAIN |
.mnt |
|
MASTER OR MAS |
.mas MASTER has a special behavior that any matching Access File (.acx) is also operated upon by the APP command. This is so metadata is operated upon as a matched pair. Use MAS if it is strictly desired to only operate on the Master File and not the Access File. |
|
MHT |
.mht |
|
Microsoft Access database |
.mdb |
|
MNTPAINT |
.mpt |
|
OMI |
.omi |
|
|
|
|
PFA |
.pfa |
|
PFB |
.pfb |
|
PNG |
.png |
|
PS |
.ps |
|
SMARTLIB |
.knb |
|
SQL |
.sql |
|
SVG |
.svg |
|
TABS |
.txt |
|
TDL |
.tdl |
|
TRF |
.trf |
|
TTEDIT |
.tte |
|
TXT |
.txt |
|
WINFORMS |
.wfm |
|
WSDL |
.wsd |
|
XHT |
.xht |
|
XLSM |
.xlsm |
|
XLSX |
.xlsx |
|
XLTM |
.xltm |
|
XLTX |
.xltx |
|
XML |
.xml |
|
XSD |
.xsd |
|
XSL |
.xsl |