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 appname1 [appname2] [appname3][[-] [appnamen ...]]

where:

appname1...appnamen

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

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: 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:

Filetype

Parms

FOCEXEC

RECFM VB TRKS LRECL 4096 BLKSIZE 27998 SPACE 50 50 DIR 50

MASTER

RECFM VB TRKS LRECL 80 BLKSIZE 22000 SPACE 50 50 DIR 50

ACCESS

RECFM VB 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 filetype creates libraries for GIF and JPG files.

FOCSTYLE

RECFM VB TRKS LRECL 1024 BLKSIZE 27648 SPACE 50 50 DIR 50

MAINTAIN

RECFM VB TRKS LRECL 4096 BLKSIZE 27998 SPACE 50 50 DIR 50

WINFORM

RECFM VB TRKS LRECL 4096 BLKSIZE 27998 SPACE 50 50 DIR 50

ETG

RECFM VB 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 appname1 appname2

where:

appname1

Is the application being copied.

appname2

Is the application to which the contents of the first application are being copied.
Top of page
x
APP COPYF

How to:

The APP COPYF command copies a single component from one application to another.

Note that if you copy the component manually, you can, optionally, rename it in the process.

x
Syntax: How to Copy an Application Component Manually
APP COPYF appname1 filename1 filetype1 appname2 filename2 filetype2

where:

appname1

Is the application that contains the component to be copied.

filename1

Is the component to be copied.

filetype1

Is the file type of the component to be copied.

appname2

Is application to which the named component is being copied.

filename2

Is the component in the second application, after the copy process.

filetype2

Is the component type in the second application, after the copy process.

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 MOVEF

How to:

The APP MOVEF command moves a single component from one application to another.

Note that if you move the component manually, you can, optionally, rename it in the process.

x
Syntax: How to Move an Application Component Manually
APP MOVEF appname1 filename1 filetype1 appname2 filename2 filetype2

where:

appname1

Is the application name of the component being moved.

filename1

Is the component name to be moved.

filetype1

Is the file type of component to be moved.

appname2

Is the application name to which the component of the first application is being moved.

filename2

Is the component name, in the second application, after the move process.

filetype2

Is the component type, in the second application, after the move process.

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 DELETE

How to:

The APP DELETE command deletes an application under approot.

x
Syntax: How to Delete an Application Manually
APP DELETE appname1 [appname2] [appname3][[-] [appnamen ...]]

where:

appname1...appnamen

Are application names. 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.
Top of page
x
APP DELETEF

How to:

The APP DELETEF command deletes a component in an application.

x
Syntax: How to Delete an Application Component Manually
APP DELETEF appname filename filetype

where:

appname

Is the application from which the component is being deleted.

filename1

Is the component to be deleted.

filetype

Is the component type of the file to be deleted.

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 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 appname1 appname2

where:

appname1

Is the application name to be renamed.

appname2

Is the new application name of up to 64 characters.

Example: Renaming an Application

The following shows APP1 being renamed to APP2.

APP RENAME APP1 APP2
Top of page
x
APP RENAMEF

How to:

The APP RENAMEF command renames a single component in an application.

x
Syntax: How to Rename an Application Component
APP RENAMEF appname filename1 filename2 filetype

where:

appname

Is the name of the application that contains the component being renamed.

filename1

Is the component to be renamed.

filename2

Is the new name for the component. The component name may be up to 64 characters and must not already exist since APP RENAME will not overwrite an existing name.

filetype

Is the component type of the file name to be renamed.

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
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 the requires it.

Note: This list reflects file types supported across all IBI 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

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

CSS

.ccc

MDB

.mdb
WebFOCUS