Application and File Management Commands

In this section:

The APP commands in this section provide management options for applications and their component files.


Top of page

x
APP CREATE

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.



x
Syntax: How to Create an Application Manually
APP CREATE app1[/app1a...] [app2[/app2a...] ...
   [appn[/appna...] ] [DROP]

where:

app1...appn

Are application names under approot. The application name can be up to 64 characters.

app1a...appna

Are nested application directories, allowed when nested applications are configured. In order to create a nested application, the parent application must already exist.

DROP

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.



x
Syntax: How to Change Default Characteristics of Component File Types (PDS Deployment Only)

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:

filetype

Are the component types that may be affected by this command, in uppercase: FOCEXEC, MASTER, ACCESS, HTML, GIF, FOCSTYLE, MAINTAIN, WINFORMS, ETG. You must issue a separate command for each component type you wish to affect.

SKIP

Indicates that the designated file type should not be created when the APP CREATE command is issued.

CREATE

Creates the designated file type when the APP CREATE command is issued. This is the default setting.

POSTFIX

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.

parms

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

WINFORMS

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


Example: Changing Default Characteristics of an Application (PDS Deployment)

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

Top of page

x
APP COPY

How to:

The APP COPY command copies the entire contents of one application to another. The target application must already exist.



x
Syntax: How to Copy an Application
APP COPY app1[/app1a...] app2[/app2a...]

where:

app1[/app1a...]

Is the application being copied. It can be a nested application name.

app2[/app2a...]

Is the application to which the contents of the first application are being copied. It can be a nested application name.


Top of page

x
APP COPYF[ILE]

How to:

The APP COPYF[ILE] command copies a single component or component type from one application to another.

Note that if you copy the 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.



x
Syntax: How to Copy an Application Component Manually
APP COPYF[ILE] app1[/app1a...]
  {filename1|*} filetype1   app2 [/app2a...]
  {filename2|*} {filetype2|*} [IFEXIST] DROP

where:

app1[/app1a...]

Is the application that contains the component to be copied. It can be a nested application name.

filename1

Is the component to be copied. Use an asterisk (*) to copy all components of file type filetype1.

filetype1

Is the file type, in uppercase, of the component to be copied.

app2[/app2a...]

Is the application to which the named component is being copied. It can be a nested application name.

filename2

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.

filetype2

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.

IFEXIST

Ignores any component in the source application that does not exist.

DROP

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 Designating File Types for APP Commands.


Top of page

x
APP MOVE

How to:

The APP MOVE command moves the entire contents of one application to another. The target application must already exist.



x
Syntax: How to Move an Application
APP MOVE app1[/app1a...] app2[/app2a...]

where:

app1[/app1a...]

Is the application being moved. It can be a nested application name.

app2[/app2a...]

Is the application to which the contents of the first application are being moved. It can be a nested application name.


Top of page

x
APP MOVEF[ILE]

How to:

The APP MOVEF[ILE] command moves a single component or component type from one application to another.

Note that if you move the 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.



x
Syntax: How to Move an Application Component Manually
APP MOVEF[ILE] app1[/app1a...]
  {filename1|*} filetype1  app2 [/app2a...]
  {filename2|*} {filetype2|*} [IFEXIST] [DROP]

where:

app1[/app1a...]

Is the application that contains the component to be moved. It can be a nested application name.

filename1

Is the name of the component to be moved. Use an asterisk (*) to move all components of file type filetype1.

filetype1

Is the file type, in uppercase, of the component to be moved.

app2[/app2a...]

Is the application to which the named component is being moved. It can be a nested application name.

filename2

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.

filetype2

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.

IFEXIST

Ignores any component in the source application that does not exist.

DROP

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 Designating File Types for APP Commands.


Top of page

x
APP DELETE

How to:

The APP DELETE command deletes applications under approot.



x
Syntax: How to Delete an Application Manually
APP DELETE app1[/app1a...] [app2[/app2a...] ...
  [appn[/appna...]]

where:

app1[/app1a...] ... [appn[/appna...]

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.


Top of page

x
APP DELETEF[ILE]

How to:

The APP DELETEF[ILE] command deletes a component or component type 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.



x
Syntax: How to Delete an Application Component Manually
APP DELETEF[ILE] app[/appna...] {filename|*} filetype

where:

appn[/appa...]

Is the application from which the component or component type is being deleted. Nested application names are supported.

filename

Is the name of the component to be deleted. Use an asterisk (*) to delete all files of type filetype.

filetype

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 Designating File Types for APP Commands.


Top of page

x
APP PROPERTY CODEPAGE

How to:

The APP PROPERTY appname CODEPAGE command identifies the codepage to be used for non-data files in the application directory.



x
Syntax: How to Specify a Code Page for an Application
APP PROPERTY app[/appa...] CODEPAGE number

where:

app[/appa...]

Is an application name. Nested application names are supported.

number

Is the code page number for non-data files in the application.


Top of page

x
APP RENAME

How to:

The APP RENAME command renames an existing application.

Note: You cannot rename an application if it is active in the search path.



x
Syntax: How to Rename an Application
APP RENAME app1[/app1a...] app2[/app2a...]

where:

app1[/app1a...]

Is the application name to be renamed. It can be a nested application name.

app2[/app2a...]

Is the new application name of up to 64 characters. It can be a nested application name.



Example: Renaming an Application

The following shows app1 being renamed to app2.

APP RENAME app1 app2

Top of page

x
APP RENAMEF[ILE]

How to:

The APP RENAMEF[ILE] command renames a single component 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.



x
Syntax: How to Rename an Application Component
APP RENAMEF[ILE] app[/appa... ] filename1
filename2 filetype [DROP]

where:

app[/appa...]

Is the name of the application that contains the component being renamed. It can be a nested application name

filename1

Is the file name of the component to be renamed.

filename2

Is the new name for the component. The component name may be up to 64 characters.

filetype

Is the file type, in uppercase, of the component to be renamed.

DROP

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 Designating File Types for APP Commands.


Top of page

x
Designating File Types for APP Commands

Reference:

The APP COPYF, APP MOVEF, APP DELETEF, and APP RENAMEF commands enable you to perform their actions on a wide variety of file types.



x
Reference: APP Commands and 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 Information Builders products and release levels. Particular file types may not be supported in particular releases or with every product.

File Type

File Extension

MASTER

.mas

FOCSQL

.acx

OMI

.omi

HLI

.hli

FOCEXEC

.fex

EDAPROF

.prf

MNTPAINT

.mpt

EDANLS

.nls

ERRORS

.err

MAINTAIN

.mnt

WINFORMS

.wfm

FOCCOMP

.fcm

FOCSTYLE

.sty

FOCFTMAP

.fmp

AFM

.afm

HTML

.htm

TXT

.txt

PS

.ps

GIF

.gif

TDL

.tdl

BMP

.bmp

EXCEL

.xls

XLSX

.xlsx

XLTX

.xltx

XLSM

.xlsm

XLTM

.xltm

ADR

.adr

BST

.bst

EPS

.eps

PDF

.pdf

XHT

.xht

XML

.xml

XSL

.xsl

TABS

.txt

SMARTLIB

.knb

FOCUS

.foc

IBICPG

.sl

TTEDIT

.tte

FOCTEMP

.ftm

DATA

.dat

TRF

.trf

FMU

.fmu

DDS

.DDS

FOCDEF

.def

PFA

.pfa

FOCPSB

.psb

PFB

.pfb

CONTROL

.ctl

LSN

.lsn

DTD

.dtd

ETL

.etl

EDAPRFU

.prf

ETG

.etg

XSD

.xsd

WSDL

.wsd

JPG

.jpg

SVG

.svg

PNG

.png

EDAPSB

.psb

MHT

.mht

SQL

.sql

JS

.js

Cascading Stylesheet

.css

Microsoft Access database

.mdb


iWay Software